agentleFS
odere-proodere-pro/claude-software-3-0-marketplace/docs/CLAUDE.md

claude-software-3-0-marketplace

CLAUDE.md2 starsChanged 5 months agoMITView on GitHub

Author-only documentation (not shipped; not loaded into end-user sessions). - adding-plugins.md — the canonical, agent-driven process for managing the registry: the /vet-plugin, /add-plugin, /update-plugin (refresh / --repo repoint / --name rename), and /remove-plugin skills, the listability contract, how to clear each blocker, and the manual fallback. Start here when growing or maintaining the marketplace. - teams.md — how the two dev-only agent teams relate: the ideation brainstorm team and the implementation registry-dev team, and the roadmap handoff between them. -…

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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:

    Keep docs link-clean — tests/gates/05-doc-links.sh fails CI on a dangling intra-repo .md link.

    line 18

≈ “Common” is an estimate: at least 1 in 5 of the 27,641 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

docs/ — human-readable references

Author-only documentation (not shipped; not loaded into end-user sessions).

  • adding-plugins.md — the canonical, agent-driven process for managing the registry: the /vet-plugin, /add-plugin, /update-plugin (refresh / --repo repoint / --name rename), and /remove-plugin skills, the listability contract, how to clear each blocker, and the manual fallback. Start here when growing or maintaining the marketplace.
  • teams.md — how the two dev-only agent teams relate: the ideation brainstorm team and the implementation registry-dev team, and the roadmap handoff between them.
  • brainstorm/ — the 12-persona, read-only brainstorm team apparatus (charter, roster, protocol) that ideates the agentic-engineering level-up.
  • plan/ — phased roadmaps (proposals) produced by the brainstorm team and consumed by registry-dev.
  • plugins/ — per-plugin install + quick-start guides for listed plugins (one file per plugin; mirrors each plugin's own README quick start so the registry is self-sufficient).

Keep docs link-clean — tests/gates/05-doc-links.sh fails CI on a dangling intra-repo .md link.

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.