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

claude-software-3-0-marketplace

CLAUDE.md2 starsChanged 5 months agoMITView on GitHub

This directory holds marketplace.json, the single source of truth for the odere-pro marketplace. It is the only thing this repo ships. There is intentionally no plugin.json here — this is a registry, not a plugin. - name is exactly odere-pro. Claude Code keys marketplaces by name. If any other repo also declares a marketplace named odere-pro, only one registers and the other is silently shadowed — the install failure that motivated consolidating everything here. So the name is load-bearing and…

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:

    Prefer the agent-driven skills (see docs/adding-plugins.md) over hand edits: /add-plugin <repo> to list, /update-plugin <name> to refresh / …

    line 51

≈ “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-plugin/ — the registry manifest (deepest detail)

This directory holds marketplace.json, the single source of truth for the odere-pro marketplace. It is the only thing this repo ships. There is intentionally no plugin.json here — this is a registry, not a plugin.

marketplace.json shape

{
  "$schema": "https://json.schemastore.org/claude-code-marketplace.json",
  "name": "odere-pro",
  "owner": { "name": "odere-pro", "email": "odere.pro@gmail.com" },
  "description": "…",
  "plugins": [
    {
      "name": "claude-oop-excellence",
      "source": { "source": "github", "repo": "odere-pro/claude-oop-excellence" },
      "description": "…",
      "homepage": "https://github.com/odere-pro/claude-oop-excellence",
      "license": "MIT",
      "keywords": ["…"]
    }
  ]
}

Invariants (every one is gated by tests/gates/02-marketplace-shape.sh)

  • name is exactly odere-pro. Claude Code keys marketplaces by name. If any other repo also declares a marketplace named odere-pro, only one registers and the other is silently shadowed — the install failure that motivated consolidating everything here. So the name is load-bearing and must never drift, and listed plugins' own repos must ship no marketplace.json.
  • Each entry is a github source whose repo is owned by odere-pro (matches ^odere-pro/[A-Za-z0-9._-]+$). The entry name may differ from the repo basename — e.g. plugin-cookbook lives in odere-pro/claude-plugin-cookbook. Entry names are unique.
  • Each entry carries name, description, license (plus homepage, keywords by convention).
  • Listing-quality floors (G2): description is non-empty, ≥ 20 chars, and not a verbatim repeat of name; keywords is non-empty; homepage (when set) matches ^https://. The top-level marketplace description is also non-empty and ≥ 40 chars (W2.1). Each entry must have at least one keyword NOT in the generic-keyword denylist (claude plugin tool utility helper code ai assistant cli) — this is a hard FAIL, not advisory (W2.1). The denylist is parity-gated between G2 and the Write-path hook (marketplace-guard.sh) via G0 §5.
  • $schema is pinned to https://json.schemastore.org/claude-code-marketplace.json (exact string-equality, checked by G2 with no network call).
  • No version on any entry — the plugin's own plugin.json is the version of record.
  • No sha/commit — installs track the plugin repo's default branch.

Editing

Prefer the agent-driven skills (see docs/adding-plugins.md) over hand edits: /add-plugin <repo> to list, /update-plugin <name> to refresh / repoint (--repo) / rename (--name), /remove-plugin <name> to drop, /vet-plugin <repo> to preflight. A PreToolUse hook (.claude/hooks/marketplace-guard.sh) blocks edits that break JSON, rename the marketplace, set a non-odere-pro repo, add a forbidden key, or embed a secret; a PostToolUse hook keeps it two-space indented. The path-scoped rule .claude/rules/marketplace-dev.md restates the contract. After editing, regenerate the README table (bash .claude/skills/add-plugin/scripts/sync-readme.sh), update CHANGELOG.md, and run bash tests/gates/run-all.sh.

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.