aicontext
CLAUDE.md2 starsChanged 7 months agoMITView on GitHub
Before starting any session, read and follow .aicontext/prompts/start.md. When subagents are available, delegate these tasks instead of performing them inline: Why: Subagents run with their own context window. Delegating keeps the main conversation focused and avoids consuming tokens on raw file contents, test output, and review details. Rules: - NEVER perform a review inline when the reviewer agent exists — delegate to the agent - NEVER read large amounts of code into main context for review — delegate to the…
In this repository40 other files it gives its agents.
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/aicontext.mdcCursor rule
- add-ideaSkill
- add-stepSkill
- aic-helpSkill
- aic-skillsSkill
- align-contextSkill
- brainstormSkill
- challengeSkill
- close-taskSkill
- commitSkill
- create-taskSkill
- deep-reviewSkill
- do-itSkill
- draft-issueSkill
- draft-prSkill
- finish-taskSkill
- generate-docsSkill
- gh-fix-testsSkill
- gh-resolve-prSkill
- gh-review-checkSkill
- gh-review-fix-loopSkill
- interviewSkill
- load-specSkill
- load-taskSkill
- make-prSkill
- next-stepSkill
- orchestrate-workersSkill
- plan-tasksSkill
- prepare-releaseSkill
- reviewSkill
- review-taskSkill
- run-stepSkill
- run-taskSkill
- start-featureSkill
- startSkill
- thoughtsSkill
- tidy-aicSkill
- web-inspectSkill
- worker-startSkill
The file
We split this CLAUDE.md into the rules it gives an agent
9 rules. About 0 are common, 3 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 3
Before starting any session, read and follow .aicontext/prompts/start.md.
- Distinctive: line 7
When subagents are available, delegate these tasks instead of performing them inline:
- Very specific: line 19
NEVER perform a review inline when the reviewer agent exists — delegate to the agent
- Distinctive: line 20
NEVER read large amounts of code into main context for review — delegate to the agent
- Very specific: line 21
Run multiple agents in parallel when tasks are independent (e.g., reviewer + test-runner after implementation)
- Very specific: line 22
NEVER use EnterPlanMode — all planning is done in .aicontext/tasks/ task files per process.md
- Very specific: line 23
NEVER launch a subagent without telling the user first — state which agent and what it will do (e.g., "Asking subagent test-runner to …
- Distinctive: line 24
When invoking an agent, provide only the context it needs (command, directory, files, task requirements).
- Very specific: line 25
When a skill is invoked via /command, its content is provided inline — NEVER read files from .claude/skills/ directories
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Project Rules
Before starting any session, read and follow .aicontext/prompts/start.md.
Agents
When subagents are available, delegate these tasks instead of performing them inline:
| Task | Agent | When |
| Code review | reviewer | After completing implementation, before presenting to user |
| Running tests | test-runner | After writing or modifying code |
| Drafting tests | test-writer | During TDD, to parallelize test writing with implementation |
| Codebase research | researcher | Before making changes, to understand existing code |
Why: Subagents run with their own context window. Delegating keeps the main conversation focused and avoids consuming tokens on raw file contents, test output, and review details.
Rules:
- NEVER perform a review inline when the
revieweragent exists — delegate to the agent - NEVER read large amounts of code into main context for review — delegate to the agent
- Run multiple agents in parallel when tasks are independent (e.g.,
reviewer+test-runnerafter implementation) - NEVER use
EnterPlanMode— all planning is done in.aicontext/tasks/task files perprocess.md - NEVER launch a subagent without telling the user first — state which agent and what it will do (e.g., "Asking subagent
test-runnerto execute the full test suite.") - When invoking an agent, provide only the context it needs (command, directory, files, task requirements). Never specify output format or reporting style — agents have built-in instructions and overriding them causes raw output dumps instead of structured summaries.
- When a skill is invoked via
/command, its content is provided inline — NEVER read files from.claude/skills/directories
Model defaults: Agents default to sonnet, except reviewer which defaults to opus for thorough analysis. Free plan users can downgrade all agents to haiku during aicontext init.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

