Manifestdocs Claude Plugins
manifestdocs-claude-plugins is a Claude Code plugin for the Build phase that adds Manifest documentation and semantic navigation plugins for feature-driven engineering context.
by manifestdocs · github.com/manifestdocs/claude-plugins
Wire Manifest’s Claude Code plugins so agents navigate living, feature-driven documentation and semantic code relationships without leaving the editor.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install manifestdocs-claude-plugins@manifestdocs/claude-pluginsBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:manifestdocs/claude-plugins") and the paste-ready config with skillselion.get_install_config("plugin:manifestdocs/claude-plugins").
What it does
manifestdocs-claude-plugins is a Claude Code plugin source that ships two plugins from Manifest, aimed at builders who want documentation and codebase navigation to stay aligned with how features actually ship. Solo developers and small teams install it when Claude Code sessions stall on stale READMEs or when finding callers, definitions, and dependencies requires too much manual search. The bundle emphasizes living, feature-driven documentation and semantic navigation so agents can reason about product and engineering context alongside code. That pairing supports validate-through-operate work—scoping features, implementing them, and updating docs—but the canonical catalog placement stays on Build docs because that is where most users first register documentation plugins. Keywords such as manifest, rocketindex, semantic, and navigation signal tight coupling with Manifest’s doc model rather than generic markdown skills. Treat this as an MCP-oriented plugin pack for doc-aware coding agents, not a single lint or test runner.
Highlights
- Two Claude Code plugins from manifestdocs/claude-plugins in one catalog entry
- Feature-driven and living documentation orientation for engineering and product context
- Semantic navigation keywords: callers, definitions, dependencies without brittle grep-only flows
- Manifest and rocketindex integration for codebase-aware agent sessions
- MCP-category listing for documentation-heavy agent workflows
Why builders use it
Agents and humans lose hours when documentation is static and code navigation depends on slow, incomplete text search.
After registration, Claude Code can use Manifest’s plugins to traverse living docs and semantic relationships like callers, definitions, and dependencies.
At a glance
- Type - Plugin in Development Tools.
- Adoption - 0 installs, 0 stars, 0 votes.
FAQ
Who is manifestdocs-claude-plugins for?
It is for developers using Claude Code who rely on Manifest for feature-driven, living documentation and want agent tooling aligned with that model.
When should I use manifestdocs-claude-plugins?
Use it when semantic navigation across callers, definitions, and dependencies should complement your docs during build, review, and iteration.
How do I add manifestdocs-claude-plugins to my agent?
Install the manifestdocs/claude-plugins Claude Code plugin bundle, enable both listed plugins, and connect them to your Manifest documentation setup per repository docs.
Comments
Share how you use manifestdocs-claude-plugins, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.