A community-facing marketplace of Claude Code plugins for building, maintaining, and evolving static content websites — initially Astro-based. Covers both infrastructure (site building, language servers) and content operations (writing, translation, linking, images).
content-stack/
├── .claude-plugin/
│ └── marketplace.json ← plugin registry (name, version, description, source)
├── content-ops/ ← content creation & management plugin
├── astro-builder/ ← Astro 6 site builder plugin
├── astro-lsp/ ← Astro language server plugin
└── README.md ← marketplace landing page (install commands, plugin list)
Each plugin directory follows this layout:
plugin-name/
├── README.md ← user-facing docs (required)
├── agents/ ← agent definition files (.md)
├── skills/ ← skill definition files (SKILL.md per skill)
├── hooks/ ← hooks.json + handler scripts
└── docs/ ← extended documentation
The single source of truth for registered plugins is .claude-plugin/marketplace.json.
Every plugin entry must have: name, version (semver), description, author.name, source, category.
- Create the plugin directory with
README.mdand its components - Run
/version-plugin— it will register the entry inmarketplace.jsonand update the rootREADME.md
- Plugin names are lowercase, hyphenated (e.g.
astro-builder,content-ops) - Skills use
SKILL.mdas the filename insideskills/<skill-name>/ - Agents use
<agent-name>.mdinsideagents/
The following plugins are enabled project-wide via .claude/settings.json — no global installation needed:
| Plugin | Why it's here |
|---|---|
plugin-dev |
End-to-end plugin authoring: skills, agents, hooks, commands, MCP, validation |
superpowers |
Structured planning, TDD, debugging, code review, and parallel agent dispatch |
feature-dev |
Feature exploration, architecture design, and implementation review for new plugins |
code-review |
Reviewing plugin PRs and contributions before merging |