agentleFS
Sign inStart free
kais-aljammalkais-aljammal/web-dev-skills/templates/CLAUDE.md

web-dev-skills / templates

CLAUDE.md1 starsChanged 3 months agoMITView on GitHub

The file

We split this CLAUDE.md into the rules it gives an agent

9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    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. Distinctive:

    Keep protected authorization server-side and test cross-user/cross-tenant denial.

    line 29
  2. Distinctive:

    Never print, commit, or expose secret values.

    line 31
  3. Distinctive:

    Add tests for changed behavior, critical invariants, and negative authorization paths.

    line 32
  4. Distinctive:

    Keep migrations safe, reviewed, and reversible or explicitly compensated.

    line 34
  5. Distinctive:

    Keep logs structured and free of sensitive values.

    line 35
  6. Distinctive:

    Follow the repository threat model and OWASP ASVS requirements.

    line 38
  7. Distinctive:

    Treat uploaded files, model output, retrieved content, URLs, and webhook payloads as untrusted.

    line 40
  8. Distinctive:

    Verify webhook signatures, use idempotency, and handle replay/reordering.

    line 41
  9. Distinctive:

    Use least privilege for tools, cloud roles, tokens, CI jobs, and admin features.

    line 42

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

CLAUDE.md — Website Engineering Rules

Product and architecture

  • Product summary: [ONE PARAGRAPH]
  • Primary users and journeys: [LIST]
  • Architecture: [LINK/PATH]
  • Requirements: [LINK/PATH]
  • Threat model: [LINK/PATH]

Repository map

  • App/frontend: [PATH]
  • Server/API: [PATH]
  • Database/migrations: [PATH]
  • Shared UI/design system: [PATH]
  • Tests: [PATH]
  • Infrastructure/deployment: [PATH]

Commands

  • Install: [COMMAND]
  • Development: [COMMAND]
  • Lint: [COMMAND]
  • Typecheck: [COMMAND]
  • Unit/integration tests: [COMMAND]
  • E2E tests: [COMMAND]
  • Build: [COMMAND]

Engineering rules

  • Inspect existing patterns before introducing a new abstraction or dependency.
  • Keep protected authorization server-side and test cross-user/cross-tenant denial.
  • Validate all external input and provider responses at trust boundaries.
  • Never print, commit, or expose secret values. Use environment-variable names only.
  • Add tests for changed behavior, critical invariants, and negative authorization paths.
  • Preserve accessibility, responsive behavior, and error/loading/empty states.
  • Keep migrations safe, reviewed, and reversible or explicitly compensated.
  • Keep logs structured and free of sensitive values.

Security and abuse rules

  • Follow the repository threat model and OWASP ASVS requirements.
  • Apply layered rate limits/quotas to authentication, public forms, expensive APIs, uploads, payments, search, and AI actions.
  • Treat uploaded files, model output, retrieved content, URLs, and webhook payloads as untrusted.
  • Verify webhook signatures, use idempotency, and handle replay/reordering.
  • Use least privilege for tools, cloud roles, tokens, CI jobs, and admin features.

Done means

  • Acceptance criteria are satisfied.
  • Relevant lint, type, tests, and build pass.
  • Browser/mobile and accessibility checks are completed for UI work.
  • Security/authorization tests pass for protected work.
  • The diff is reviewed for regressions, secrets, debug code, and unnecessary dependencies.
  • Documentation and operational notes are updated.

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.

Check your setup, free