agentleFS
Sign inStart free
hamzaMissewihamzaMissewi/agent-skills/CLAUDE.md

agent-skills

CLAUDE.md2 starsChanged 4 months agoMITView on GitHub

This is the agent-skills project — a collection of production-grade engineering skills for AI coding agents. Define: interview-me, idea-refine, spec-driven-development Plan: planning-and-task-breakdown Build: incremental-implementation, test-driven-development, context-engineering, source-driven-development, doubt-driven-development, frontend-ui-engineering, api-and-interface-design Verify: browser-testing-with-devtools, debugging-and-error-recovery Review: code-review-and-quality, code-simplification, security-and-hardening, performance-optimization Ship: git-workflow-and-versioning, ci-cd-and-automation, deprecation-and-migration, documentation-and-adrs, observability-and-instrumentation, shipping-and-launch Before adding a new skill or significantly reworking an existing one, run the pre-flight checks in CONTRIBUTING.md: search the catalog, check open PRs, confirm the idea fits docs/skill-anatomy.md, and justify the gap. Prefer extending an…

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Every skill lives in skills/<name>/SKILL.md

    line 28
  2. Distinctive:

    Every skill has: Overview, When to Use, Process, Common Rationalizations, Red Flags, Verification

    line 31
  3. Distinctive:

    Before opening a PR, search the upstream repository's open PRs and issues for work that touches the same files or rules.

    line 49
  4. Very specific:

    Prefer small, focused PRs over large refactors of widely shared files (for example, files under scripts/), which are more likely to collide …

    line 50
  5. Distinctive:

    Always: Run the CONTRIBUTING.md pre-flight checks before creating a new skill directory

    line 54
  6. Distinctive:

    Always: Follow the skill-anatomy.md format for new skills

    line 55
  7. Distinctive:

    Always: Check the upstream repo's open PRs and issues for overlap before opening a new PR

    line 56
  8. Distinctive:

    Never: Add skills that are vague advice instead of actionable processes

    line 57
  9. Distinctive:

    Never: Duplicate content between skills — reference other skills instead

    line 58

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

agent-skills

This is the agent-skills project — a collection of production-grade engineering skills for AI coding agents.

Project Structure

skills/       → Core skills (SKILL.md per directory)
agents/       → Reusable agent personas (code-reviewer, test-engineer, security-auditor, web-performance-auditor)
hooks/        → Session lifecycle hooks
.claude/commands/ → Slash commands (/spec, /plan, /build, /test, /review, /code-simplify, /ship; plus /webperf specialist audit)
references/   → Supplementary checklists (testing, performance, security, accessibility, observability)
evals/        → Skill eval cases + framework (see evals/README.md)
docs/         → Setup guides for different tools

Skills by Phase

Define: interview-me, idea-refine, spec-driven-development Plan: planning-and-task-breakdown Build: incremental-implementation, test-driven-development, context-engineering, source-driven-development, doubt-driven-development, frontend-ui-engineering, api-and-interface-design Verify: browser-testing-with-devtools, debugging-and-error-recovery Review: code-review-and-quality, code-simplification, security-and-hardening, performance-optimization Ship: git-workflow-and-versioning, ci-cd-and-automation, deprecation-and-migration, documentation-and-adrs, observability-and-instrumentation, shipping-and-launch

Conventions

  • Every skill lives in skills/<name>/SKILL.md
  • YAML frontmatter with name and description fields
  • Description starts with what the skill does (third person), followed by trigger conditions ("Use when...")
  • Every skill has: Overview, When to Use, Process, Common Rationalizations, Red Flags, Verification
  • References are in references/, not inside skill directories
  • Supporting files only created when content exceeds 100 lines

Contributing

Before adding a new skill or significantly reworking an existing one, run the pre-flight checks in CONTRIBUTING.md: search the catalog, check open PRs, confirm the idea fits docs/skill-anatomy.md, and justify the gap. Prefer extending an existing skill over adding a near-duplicate. CONTRIBUTING.md is the single source of truth for this workflow; do not restate its checklist here or elsewhere, link to it.

Commands

  • npm test — Not applicable (this is a documentation project)
  • Validate: Check that all SKILL.md files have valid YAML frontmatter with name and description
  • Evals: node scripts/run-evals.js — trigger/routing evals for every skill (CI); --behavioral <skill> for graded runs

Pull Requests

PRs target the upstream repository's default branch. In a typical fork setup the upstream remote is upstream and your fork is origin, but the exact remote names are not what matters here.

  • Before opening a PR, search the upstream repository's open PRs and issues for work that touches the same files or rules. If any overlaps, coordinate (build on it, align your rules with it, or rebase after it merges) instead of opening a conflicting PR.
  • Prefer small, focused PRs over large refactors of widely shared files (for example, files under scripts/), which are more likely to collide with in-flight work.

Boundaries

  • Always: Run the CONTRIBUTING.md pre-flight checks before creating a new skill directory
  • Always: Follow the skill-anatomy.md format for new skills
  • Always: Check the upstream repo's open PRs and issues for overlap before opening a new PR
  • Never: Add skills that are vague advice instead of actionable processes
  • Never: Duplicate content between skills — reference other skills instead

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