agentleFS
johnqtcgjohnqtcg/awesome-skills/CLAUDE.md

awesome-skills

CLAUDE.md30 starsChanged 4 months agoMITView on GitHub

A documentation and asset repository — no application code. Five interconnected layers make up the repository: Important scope note: Regression-enabled skills under skills/<name>/ follow the layout visible via ls skills/<name>/ (SKILL.md, references/, scripts/run_regression.sh, scripts/tests/ with golden/ fixtures), plus these conventions: Per-skill regression (from the skill's directory): All skills at once (from repo root): Dependencies: pytest>=8,<9 (see requirements.txt). Built with MkDocs Material. Source is docs/, output is site/. Deployed to GitHub Pages via CI on push to main. When adding or…

  • Installs packages

The file

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

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    All supporting reference files use relative paths from SKILL.md

    line 32
  2. Distinctive:

    All skills at once (from repo root):

    line 43
  3. Distinctive:

    When adding or editing a production-ready skill, update all five layers together:

    line 67

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

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

What This Repo Is

A documentation and asset repository — no application code. Five interconnected layers make up the repository:

bestpractice/  →  rationale/  →  skills/  →  evaluate/  →  outputexample/
(methodology)     (design docs)  (examples)  (reports)     (real outputs)
  • bestpractice/ — skill design methodology docs (Fundamentals.md, Advanced.md, Evaluation.md, Iteration.md, Integration.md, Architecture.md), bilingual (EN + ZH)
  • rationale/ — per-skill design rationale docs explaining the why behind each skill's structure and decisions; each skill has design.md + design.zh-CN.md
  • skills/ — 51 installable Claude Code skills in total: 24 carry paired rationale/ + evaluate/ docs (14 with complete five-layer coverage), plus 16 multi-agent components (a 9-part Go review system and a 7-part US-equity analysis system), each centered on a SKILL.md with optional scripts/, references/, and agents/ subdirs
  • evaluate/ — formal review reports paired EN/ZH (<skill-name>-skill-eval-report.md / .zh-CN.md)
  • outputexample/ — real task outputs (PDFs, test code, CI configs, screenshots)
  • docs/ — MkDocs Material site source; served at GitHub Pages

Important scope note:

  • 14 skills have full five-layer coverage (rationale/, skills/, evaluate/, outputexample/); 24 carry at least paired rationale/ + evaluate/.
  • 16 multi-agent components support the orchestration architectures: a 9-part Go review system (go-review-lead + 8 vertical review skills) and a 7-part US-equity analysis system (stock-analysis-lead + 6 vertical review skills). They are installable and regression-tested, but do not yet have standalone rationale/, evaluate/, or outputexample/ tracks.

Skill Structure Convention

Regression-enabled skills under skills/<name>/ follow the layout visible via ls skills/<name>/ (SKILL.md, references/, scripts/run_regression.sh, scripts/tests/ with golden/ fixtures), plus these conventions:

  • Skill names use kebab-case
  • SKILL.md frontmatter must have name and description fields
  • All supporting reference files use relative paths from SKILL.md

Running Regression Tests

Per-skill regression (from the skill's directory):

cd skills/<name>
bash scripts/run_regression.sh

All skills at once (from repo root):

python3 -m pytest skills/
# or with coverage:
python3 -m pytest --tb=short skills/

Dependencies: pytest>=8,<9 (see requirements.txt).

Documentation Site

Built with MkDocs Material. Source is docs/, output is site/.

pip install mkdocs-material
mkdocs serve      # local preview at http://127.0.0.1:8000
mkdocs build      # build static site into site/

Deployed to GitHub Pages via CI on push to main.

Contribution Rules

When adding or editing a production-ready skill, update all five layers together:

  1. skills/<name>/SKILL.md (and supporting files)
  2. rationale/<name>/design.md + design.zh-CN.md
  3. evaluate/<name>-skill-eval-report.md + .zh-CN.md
  4. outputexample/<name>/
  5. bestpractice/ docs if the skill introduces or validates a new design pattern

For the 16 multi-agent components (Go review + US-equity analysis), update the skill itself, its references/tests, and shared architecture docs as needed. Those components do not currently require standalone rationale/, evaluate/, or outputexample/ directories.

Bilingual consistency is required: any change to an English doc needs a matching update to its .zh-CN.md counterpart (and vice versa). This applies to README.md, CONTRIBUTING.md, bestpractice/*.md (all six chapters plus README.zh-CN.md), and evaluate/ reports.

Pre-PR Checks

find skills -maxdepth 2 -name SKILL.md | sort
find evaluate -maxdepth 1 -type f | sort
git diff --check

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.