agentleFS
Sign inStart free
SashaMarchukSashaMarchuk/claude-plugins/CLAUDE.md

claude-plugins

CLAUDE.md0 starsChanged 11 days agoMITView on GitHub

This repository is in production — all four plugins (clickup, g-event, ultra, ultra-analyzer) are live for real users with a 170-test regression harness (bash tests/run-all.sh); every change must be made carefully, tested locally before commit, shipped via PR (no direct pushes to main), and accompanied by a migration note when registry-visible names or descriptions change so users can update via /plugin update rather than reinstall.

The file

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

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

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

    Every GSD agent: the full requirement text is in the linked spec, not in REQUIREMENTS.md.

    line 8

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

This repository is in production — all four plugins (clickup, g-event, ultra, ultra-analyzer) are live for real users with a 170-test regression harness (bash tests/run-all.sh); every change must be made carefully, tested locally before commit, shipped via PR (no direct pushes to main), and accompanied by a migration note when registry-visible names or descriptions change so users can update via /plugin update rather than reinstall.

Requirements (OpenSpec + GSD)

  • Requirement text lives only in openspec/: specs/ = current behaviour, changes/<id>/ = intended change. Never restate, reword or invent requirements elsewhere. GSD never edits openspec/.
  • /gsd-new-milestone: do not interview for requirements. Take every ### Requirement: ID Title from the active change's delta specs (openspec/changes/<id>/specs/) and write .planning/REQUIREMENTS.md entries as - [ ] **ID**: Title — openspec/changes/<id>/specs/<cap>/spec.md. Keep OpenSpec IDs as they are; do not continue GSD numbering; add no "table stakes".
  • Every GSD agent: the full requirement text is in the linked spec, not in REQUIREMENTS.md. Read it before planning, executing or verifying.
  • /gsd-discuss-phase / /gsd-plan-phase: list openspec/changes/<id>/proposal.md, design.md and the delta specs in <canonical_refs>.
  • Implement only through GSD; do not use OpenSpec apply. After the milestone's PR is merged: openspec archive <id> --yes.

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