sova / templates
CLAUDE.md3 starsChanged 4 days agoApache-2.0View on GitHub
Claude Code-specific configuration. Project conventions live in @AGENTS.md. Generated by SOVA (sova setup) {{#DEV_CMD}} ### Building / Running {{/DEV_CMD}} {{#COMMON_COMMANDS}} ### Other Commands {{/COMMON_COMMANDS}} {{#NO_AI_COAUTHOR}} - Do NOT include Co-Authored-By lines in commits - Do NOT include "Generated with Claude Code" in PR descriptions {{/NO_AI_COAUTHOR}} - Always run linter/formatter before creating commits - Never push without explicit user approval {{EXTRA_PREFERENCES}}
In this repository44 other files it gives its agents.
- AGENTS.mdAGENTS.md
- templates/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- dashboard-designSkill
- database-patternsSkill
- design-systemSkill
- design-tasteSkill
- issue-templateSkill
- sova-address-prSkill
- sova-after-mergeSkill
- sova-agent-readinessSkill
- sova-audit-instructionsSkill
- sova-debugSkill
- sova-develop-explainSkill
- sova-develop-fullSkill
- sova-developSkill
- sova-extract-knowledgeSkill
- sova-find-taskSkill
- sova-health-auditSkill
- sova-ingest-reviewSkill
- sova-integrate-prSkill
- sova-issueSkill
- sova-new-featureSkill
- sova-optimize-knowledgeSkill
- sova-prSkill
- sova-rearrange-commitsSkill
- sova-researchSkill
- sova-review-fullSkill
- sova-review-prSkill
- sova-reviewSkill
- sova-simplifySkill
- sova-specSkill
- sova-standupSkill
- sova-statusSkill
- sova-testSkill
- sova-update-docsSkill
- testing-patternsSkill
- visual-auditSkill
- dashboard-designSkill
- database-patternsSkill
- design-tasteSkill
- issue-templateSkill
- testing-patternsSkill
- visual-auditSkill
The file
We split this CLAUDE.md into the rules it gives an agent
11 rules. About 0 are common, 5 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
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
- could be automatic: a setting could enforce it
- Very specific: line 68
Confirmed patterns: Add to .claude/rules/*.md (Tier 1)
- Very specific: line 69
Deep domain knowledge: Create a command in .claude/commands/<topic>.md (Tier 1)
- Very specific: line 70
New findings (not yet confirmed): Add to .claude/agent-memory/ (Tier 2)
- Distinctive: line 83
Read AGENTS.md and this file before starting any task
- Distinctive: line 85
Follow TDD: write failing test → implement → refactor
- Distinctive: line 86
Run all tests and linting before considering work done
- Distinctive: line 88
Create a PR with a clear description linking to the issue
- Very specific: line 94
Do NOT include Co-Authored-By lines in commits
- Very specific: line 95
Do NOT include "Generated with Claude Code" in PR descriptions {{/NO_AI_COAUTHOR}}
- Distinctive: line 97
Always run linter/formatter before creating commits
- Very specific: line 98
Never push without explicit user approval {{EXTRA_PREFERENCES}}
≈ “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_NAME}} — Claude Code Instructions
Claude Code-specific configuration. Project conventions live in
@AGENTS.md. Generated by SOVA (sova setup)
@AGENTS.md
Run Commands
Testing
# Run all tests
{{TEST_CMD}}
# Run a specific test
{{TEST_SPECIFIC_CMD}}Linting and Formatting
# Lint
{{LINT_CMD}}
# Format
{{FORMAT_CMD}}{{#DEV_CMD}}
Building / Running
# Start local environment
{{DEV_CMD}}
# Run migrations (if applicable)
{{MIGRATE_CMD}}{{/DEV_CMD}}
{{#COMMON_COMMANDS}}
Other Commands
{{COMMON_COMMANDS}}{{/COMMON_COMMANDS}}
Knowledge System (4-Tier)
Tier 1: Always-loaded context (no truncation)
CLAUDE.md— This file (Claude Code-specific)AGENTS.md— Cross-cutting conventions for all AI tools.claude/rules/*.md— Modular knowledge files, loaded every session
Tier 1b: On-demand knowledge (loaded via commands)
.claude/commands/*.md— Workflow commands and deep domain skills
Tier 2: Agent memory (persists across tasks, gitignored)
.claude/agent-memory/MEMORY.md— Index file.claude/agent-memory/cookbook.md— Topical knowledge by domain, common mistakes with occurrence counts
Tier 3: Session memory (auto-managed by Claude Code)
~/.claude/projects/.../memory/MEMORY.md— User preferences, project state
Adding new knowledge
- Confirmed patterns: Add to
.claude/rules/*.md(Tier 1) - Deep domain knowledge: Create a command in
.claude/commands/<topic>.md(Tier 1) - New findings (not yet confirmed): Add to
.claude/agent-memory/(Tier 2) - User preferences: Auto-memory handles this (Tier 3)
- Promote: Tier 2 → Tier 1 when confirmed in 2+ tasks
Agent Configuration
- Task source: {{TASK_SOURCE}}
- Model: {{AGENT_MODEL}}
- Max budget per task: ${{MAX_BUDGET}}
- Review rounds: {{REVIEW_MAX_ROUNDS}}
Agent Workflow
- Read
AGENTS.mdand this file before starting any task - Understand the issue/task requirements fully before writing code
- Follow TDD: write failing test → implement → refactor
- Run all tests and linting before considering work done
- Self-review your changes before pushing
- Create a PR with a clear description linking to the issue
- Record learnings in
.claude/agent-memory/
Claude Code Behavioral Preferences
{{#NO_AI_COAUTHOR}}
- Do NOT include
Co-Authored-Bylines in commits - Do NOT include "Generated with Claude Code" in PR descriptions {{/NO_AI_COAUTHOR}}
- Always run linter/formatter before creating commits
- Never push without explicit user approval {{EXTRA_PREFERENCES}}
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.

