Claude-Code-Plugins
CLAUDE.md8 starsChanged 2 months agoMITView on GitHub
Session startup: Agent Handoff injects state through the shared repo-local SessionStart hook. Branch workflow: Direct commit to main. No testing branch. Plugin releases are manual — bump plugins/<name>/.claude-plugin/plugin.json and its matching .claude-plugin/marketplace.json entry, then commit, tag <name>/vX.Y.Z, push, and gh release create. See BRANCH_PROTECTION.md for full rules. Document layout (read on demand): Use the repo-local agent-handoff skill at session startup and closeout. Do not reread state already injected by SessionStart. Keep project knowledge inside this repository and store credential references…
- Commits and pushes
In this repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agent-handoffSkill
- agent-handoffSkill
- refresh-plugin-cacheSkill
- test-pluginSkill
The file
We split this CLAUDE.md into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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
- Very specific: line 25
Use the repo-local agent-handoff skill at session startup and closeout.
- Distinctive: line 44
Check formatting over exactly that scope, with Git as the corpus authority:
- Very specific: line 56
Never check or write with a bare .: it reaches undeclared languages and Git-excluded scratch.
- Distinctive: line 64
Never lint a bare recursive glob: it descends into any independent Git repository checked out below this one.
- Distinctive: line 66
Run the enabled checks before claiming completion.
≈ “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
CLAUDE.md
Session startup: Agent Handoff injects state through the shared repo-local SessionStart hook.
Branch workflow: Direct commit to main. No testing branch. Plugin releases are manual — bump plugins/<name>/.claude-plugin/plugin.json and its matching .claude-plugin/marketplace.json entry, then commit, tag <name>/vX.Y.Z, push, and gh release create. See BRANCH_PROTECTION.md for full rules.
Document layout (read on demand):
docs/handoff/state.md— live state + active incidents (auto-injected, do not read directly)docs/handoff/deployed.md— deployment truth + what-remainsdocs/handoff/architecture.md— repo structure + plugin design principles + full CLAUDE.md detaildocs/handoff/credentials.md— credential surfacesdocs/handoff/conventions.md— pattern library (Phase 5 deferred)docs/handoff/sessions/— monthly session logs (grep by date)docs/handoff/bugs/— per-file bug KB (grep by service or tag)docs/handoff/specs-plans.md— pointer intodocs/plans/- per-plugin tests:
plugins/<plugin>/tests/(frameworks by language perdocs/handoff/conventions.mdTEST-001)
<!-- prettier-ignore-start --><!-- BEGIN project-standards:agent-handoff --><!-- markdownlint-disable MD025 -->Agent Handoff
Use the repo-local agent-handoff skill at session startup and closeout. Do not reread state already injected by SessionStart. Keep project knowledge inside this repository and store credential references only, never values.
<!-- markdownlint-enable MD025 --><!-- END project-standards:agent-handoff --><!-- prettier-ignore-end --><!-- prettier-ignore-start --><!-- BEGIN project-standards:markdown-tooling --><!-- markdownlint-disable MD025 -->Markdown and structured-text tooling
Prettier owns physical formatting and markdownlint owns Markdown structure. Do not add overlapping tools.
Enabled checks: format, lint.
Markdown scope: **/*.md.
Structured-config scope: **/*.json, **/*.jsonc, **/*.yml, **/*.yaml.
Lint additionally skips generated directories: .pytest_cache/**, .ruff_cache/**, .venv/**, node_modules/**.
Check formatting over exactly that scope, with Git as the corpus authority:
git ls-files -z -- ':(glob)**/*.md' ':(glob)**/*.json' ':(glob)**/*.jsonc' ':(glob)**/*.yml' ':(glob)**/*.yaml' | xargs -0 -r npx prettier --check --Without Git, bound the same scope by glob instead:
npx prettier --check --no-error-on-unmatched-pattern -- '**/*.md' '**/*.json' '**/*.jsonc' '**/*.yml' '**/*.yaml'Never check or write with a bare .: it reaches undeclared languages and Git-excluded scratch.
Lint Markdown structure over the same Git-tracked scope:
git ls-files -z -- ':(glob)**/*.md' ':(glob,exclude).pytest_cache/**' ':(glob,exclude).ruff_cache/**' ':(glob,exclude).venv/**' ':(glob,exclude)node_modules/**' | sed -z 's|^|:|' | xargs -0 -r npx markdownlint-cli2 --no-globsNever lint a bare recursive glob: it descends into any independent Git repository checked out below this one.
Run the enabled checks before claiming completion.
<!-- markdownlint-enable MD025 --><!-- END project-standards:markdown-tooling --><!-- prettier-ignore-end -->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.