agentleFS
xsovad06xsovad06/sova/templates/CLAUDE.md

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}}

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
  1. Very specific:

    Confirmed patterns: Add to .claude/rules/*.md (Tier 1)

    line 68
  2. Very specific:

    Deep domain knowledge: Create a command in .claude/commands/<topic>.md (Tier 1)

    line 69
  3. Very specific:

    New findings (not yet confirmed): Add to .claude/agent-memory/ (Tier 2)

    line 70
  4. Distinctive:

    Read AGENTS.md and this file before starting any task

    line 83
  5. Distinctive:

    Follow TDD: write failing test → implement → refactor

    line 85
  6. Distinctive:

    Run all tests and linting before considering work done

    line 86
  7. Distinctive:

    Create a PR with a clear description linking to the issue

    line 88
  8. Very specific:

    Do NOT include Co-Authored-By lines in commits

    line 94
  9. Very specific:

    Do NOT include "Generated with Claude Code" in PR descriptions {{/NO_AI_COAUTHOR}}

    line 95
  10. Distinctive:

    Always run linter/formatter before creating commits

    line 97
  11. Very specific:

    Never push without explicit user approval {{EXTRA_PREFERENCES}}

    line 98

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
CLAUDE.md

{{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

  1. Read AGENTS.md and this file before starting any task
  2. Understand the issue/task requirements fully before writing code
  3. Follow TDD: write failing test → implement → refactor
  4. Run all tests and linting before considering work done
  5. Self-review your changes before pushing
  6. Create a PR with a clear description linking to the issue
  7. Record learnings in .claude/agent-memory/

Claude Code Behavioral Preferences

{{#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}}

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.