adjective-rob

Prelude — Development skill for Claude Code

Development community

Prelude is the open standard for machine-readable project context — enabling LLMs, agents, and teams to understand codebases with clarity.

How to install Prelude

This entry records only its repository, not the path inside it, so there is no exact command to give. Open adjective-rob/prelude and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Prelude does

Prelude is the open standard for machine-readable project context — enabling LLMs, agents, and teams to understand codebases with clarity. Generate structured .context/ files for architecture, stack, decisions, and more. Local-first. Agent-ready.

Alternatives in Development

Lazycodex — The one and only agent harness for complex codebases 3.3k ★
Tutor Skills — Transform docs or codebases into Obsidian StudyVaults with interactive quizzes 503 ★
Agentcontrolplane — ACP is the Agent Control Plane - a distributed agent scheduler optimized for simplicity, clarity, and control 463 ★

README

Prelude

**The open standard for machine-readable codebase context.**

Prelude transforms your codebase into structured, AI-optimized context that makes working with LLMs 10x more effective.

[![npm version](https://badge.fury.io/js/prelude-context.svg)](https://www.npmjs.com/package/prelude-context) [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)

Multi-project workspace

Register each codebase once, register Prelude once in your agent harness, and every agent session on the machine can see all of your projects: what each one is, how they relate, and where to look inside any of them.

Once per repo:

cd ~/code/backend  && prelude init && prelude workspace add .
cd ~/code/frontend && prelude init && prelude workspace add .

Once per machine:

prelude mcp-config --workspace --client claude-code
# prints:  claude mcp add --scope user prelude -- prelude serve --workspace

Then, from any agent session:

Agent call	What it gets back
`prelude_projects`	One block per project: purpose, stack, entry points, API surface, hub files, related projects
`prelude_compact(project="backend")`	The ~800-token overview, including the `[map]` line
`prelude_locate(query="billing checkout", project="backend")`	The handful of files to read, with reasons. Omit `project` to search every project
`prelude_map(project="backend", module="app/routers")`	One module's purpose, dependencies, tests, and files with exports
`prelude_record_decision(project="backend", title=..., rationale=...)`	Appended to that project's `.context/decisions.json`
`prelude_link_projects(from="frontend", to="backend", relation="consumes", contract="REST /api/v1, JWT bearer")`	Written to frontend's `project.json`
`prelude_annotate_module(project=..., path=..., purpose=..., notes=...)`	Corrects the map; never overwritten by `prelude update`
`prelude_workspace_refresh`	Reb