skills
CLAUDE.md1 starsChanged 40 days agoMITView on GitHub
Follow the shared AI framework used by other coding agents. Read and follow: Use skills from: Follow the repository-intelligence rules defined in AGENTS.md. In particular: Prefer source code and extracted structural relationships over generated reports when verifying implementation details. Prefer native tool integrations when available. For AiIndex: - Prefer its MCP tools for agent-driven repository work. - Do not run AiIndex via dotnet run. - Do not invoke AiIndex from its source tree as the normal runtime. - Use the…
In this repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- advisorSkill
- code-reviewSkill
- debugSkill
- decisionSkill
- modernize-evalSkill
- modernize-planSkill
- new-featureSkill
- nf-avaloniaSkill
- nf-designSkill
- nf-specSkill
- nf-tasksSkill
- parallel-execSkill
- project-takeoverSkill
- repo-initSkill
- session-closeSkill
- tas-01-project-architecture-analyzerSkill
- tas-02-architecture-project-grouperSkill
- tas-03-architecture-normalizerSkill
- tas-04-generatorSkill
The file
Show its rules and text
We split this CLAUDE.md into the rules it gives an agent
14 rules. About 0 are common, 10 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 3
Follow the shared AI framework used by other coding agents.
- Distinctive: line 18
Follow the repository-intelligence rules defined in AGENTS.md.
- Distinctive: line 22
Use AiIndex for semantic or fuzzy code discovery, implementation details, behavioral logic, and questions such as "where is the code that …
- Distinctive: line 23
Use Graphify for callers/callees, dependency paths, imports, inheritance or implementation relationships, architectural connections, and …
- Distinctive: line 26
Prefer source code and extracted structural relationships over generated reports when verifying implementation details.
- Distinctive: line 30
Prefer native tool integrations when available.
- Distinctive: line 33
Prefer its MCP tools for agent-driven repository work.
- Very specific: line 34
Do not run AiIndex via dotnet run.
- Distinctive: line 35
Do not invoke AiIndex from its source tree as the normal runtime.
- Distinctive: line 36
Use the installed CLI only when explicitly requested, when MCP is unavailable, or when the required operation is CLI-only.
- Very specific: line 39
When graphify-out/graph.json exists, query the existing graph instead of rebuilding it unless a rebuild/update is explicitly needed.
- Very specific: line 40
Use graphify query, graphify path, or graphify explain according to the type of structural question.
- Very specific: line 44
Before ending meaningful coding work or switching projects, run the session-close skill.
- Distinctive: line 53
Do not run it for simple Q&A with no project changes.
≈ “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
Global Claude Instructions
Follow the shared AI framework used by other coding agents.
Read and follow:
AGENTS.mdrules/team-rules.mdrules/coding-standards.mdrules/security-rules.md
Use skills from:
skills/
Shared repository intelligence
Follow the repository-intelligence rules defined in AGENTS.md.
In particular:
- Use AiIndex for semantic or fuzzy code discovery, implementation details, behavioral logic, and questions such as "where is the code that does X?".
- Use Graphify for callers/callees, dependency paths, imports, inheritance or implementation relationships, architectural connections, and impact/blast-radius analysis.
- For mixed questions, use AiIndex first to discover likely files, symbols, or concepts, then use Graphify to verify or expand the structural relationships.
Prefer source code and extracted structural relationships over generated reports when verifying implementation details.
Tool usage
Prefer native tool integrations when available.
For AiIndex:
- Prefer its MCP tools for agent-driven repository work.
- Do not run AiIndex via
dotnet run. - Do not invoke AiIndex from its source tree as the normal runtime.
- Use the installed CLI only when explicitly requested, when MCP is unavailable, or when the required operation is CLI-only.
For Graphify:
- When
graphify-out/graph.jsonexists, query the existing graph instead of rebuilding it unless a rebuild/update is explicitly needed. - Use
graphify query,graphify path, orgraphify explainaccording to the type of structural question.
Session close
Before ending meaningful coding work or switching projects, run the session-close skill.
Run it when:
- files changed;
- decisions were made;
- blockers were found;
- task status changed;
- the user says they are done, closing, wrapping up, or switching projects.
Do not run it for simple Q&A with no project changes.
Provider-aware execution
Use the shared role-routing policy in providers/claude.yml (medium/default), providers/claude.low.yml, providers/claude.high.yml, and docs/model-routing.md. Shared skills request primary, executor, researcher, advisor, or fast; they must not hard-code Claude model names. Select profiles through --profile, AI_PROFILE, or the saved per-provider selection (default medium). Apply generic repository overrides from <repo>/.ai/providers/claude.yml and optional profile-specific overrides from <repo>/.ai/providers/claude.<profile>.yml.
When installed, delegate provider roles to the generated Claude subagents ai-executor, ai-researcher, ai-advisor, and ai-fast. Keep primary in the owning conversation; its active model remains the model selected for the current Claude session rather than being overwritten by the framework profile. The generated subagent frontmatter carries model, effort, and read/write tool boundaries; repository provider overrides require regenerating/re-syncing the native artifacts before they affect Claude's native agent files. If a preferred role model is unavailable, use the generated ai-<role>-fallback-N agent in order.
For substantial plan/stuck/completion checkpoints, use the reusable advisor skill. Prefer Claude Code's native advisor tool when it is enabled, compatible with the active model, and available; otherwise use an isolated advisor-role subagent/fallback. Follow the configured repeated-failure threshold rather than repeatedly retrying the same approach.
Parallel worker execution remains plan-controlled: use workers concurrently only where an approved plan explicitly marks parallel-safe work and parallel execution has been selected.
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.

