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

claude-software-3-0-marketplace

CLAUDE.md2 starsChanged 5 months agoMITView on GitHub

Never shipped; this configures Claude Code for whoever develops the registry. The goal is a tight, high-signal harness for a repo whose only payload is one JSON file. - settings.json — the harness wiring: - includeCoAuthoredBy: false + empty attribution → human-authored commits/PRs (global policy). - permissions.allow → read-only/maintenance Bash (git read verbs, jq, find, grep, cat, the gate runner, claude plugin validate, bun lint/format) so routine work doesn't prompt. - skillOverrides → disable skill families irrelevant to a docs/JSON…

  • Reads credentials

The file

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

2 rules. About 0 are common, 1 is distinctive, and 1 is 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.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never shipped; this configures Claude Code for whoever develops the registry.

    line 3
  2. Very specific:

    All read the hook payload from stdin (JSON) via python3.

    line 21

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

.claude/ — the author-only harness

Never shipped; this configures Claude Code for whoever develops the registry. The goal is a tight, high-signal harness for a repo whose only payload is one JSON file.

Map

  • settings.json — the harness wiring:
    • includeCoAuthoredBy: false + empty attribution → human-authored commits/PRs (global policy).
    • permissions.allow → read-only/maintenance Bash (git read verbs, jq, find, grep, cat, the gate runner, claude plugin validate, bun lint/format) so routine work doesn't prompt.
    • skillOverrides → disable skill families irrelevant to a docs/JSON registry (frontend, backend, postgres/db, and the instinct-learning set).
    • hooks → see below.
  • hooks/
    • marketplace-guard.sh (PreToolUse Write|Edit|MultiEdit) — blocks bad marketplace.json edits (invalid JSON, renamed marketplace, forbidden version/sha/commit, secret tokens).
    • guard-commit-author.sh (PreToolUse Bash) — blocks a git commit with Claude/Anthropic author or an AI attribution trailer.
    • json-format.sh (PostToolUse Write|Edit) — pretty-prints edited valid *.json; no-op otherwise.
    • All read the hook payload from stdin (JSON) via python3; exit 2 blocks, 0 allows.
  • skills/ — the agent-driven manage-plugins workflow:
    • add-plugin/ — /add-plugin <repo>: vet → edit manifest + README + CHANGELOG → gates → PR. Its deterministic core lives in scripts/: {vet-candidate,add-entry,update-entry,remove-entry,sync-readme,lib}.sh (shared by all four skills).
    • vet-plugin/ — /vet-plugin <repo>: read-only preflight (go/no-go + blockers).
    • update-plugin/ — /update-plugin <name> [--repo …] [--name …]: refresh / repoint / rename an existing entry.
    • remove-plugin/ — /remove-plugin <name>: drop an entry. See docs/adding-plugins.md.
  • agents/ — the spawnable worker + team agents:
    • plugin-onboarder.md — read-only worker the skills delegate to: fetches + vets a candidate repo and curates its description/keywords; never edits the manifest.
    • registry-dev-*.md (9) — the registry-dev engineering team's roles (auto-discovered); see teams/ below.
  • teams/ — author-only spawnable agent teams (dev-only; never shipped):
    • registry-dev/ — the engineering team that implements the brainstorm roadmap (docs/plan/) behind the gate suite. TEAM-BRIEF.md + BACKLOG.md + README.md; entry point registry-dev-manager. Its ideation counterpart is docs/brainstorm/; the handoff is docs/teams.md.
  • rules/marketplace-dev.md — path-scoped (.claude-plugin/**) restatement of the manifest contract; loads only when the manifest is touched.
  • agentline.json — statusline (model · branch · PR · context% · tokens · cost) for the agentline statusline.

MCP

.mcp.json (repo root, committed) declares context7 (docs lookup) and github servers. Secrets are not in the file — they come from env (CONTEXT7_API_KEY, GITHUB_PERSONAL_ACCESS_TOKEN). Per-machine plugin/MCP enablement lives in the git-ignored .claude/settings.local.json.

Mirror to gates

What the hooks enforce interactively, tests/gates/ enforces in CI — edit them together so local and CI never disagree.

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.