Manifestdocs Claude Plugins
- Updated March 4, 2026
- manifestdocs/claude-plugins
manifestdocs-claude-plugins is a Claude Code plugin that adds Manifest documentation and semantic navigation plugins for feature-driven engineering context.
About
manifestdocs-claude-plugins is a Claude Code plugin source that ships two plugins from Manifest, aimed at developers who want documentation and codebase navigation to stay aligned with how features actually ship. 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.
- 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
Manifestdocs Claude Plugins by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
/plugin install manifestdocs-claude-plugins@manifestdocs/claude-pluginsAdd your badge
Show developers this plugin is listed on Skillselion. Paste this into your README.
| Last updated | March 4, 2026 |
|---|---|
| Repository | manifestdocs/claude-plugins ↗ |
What it does
Wire Manifest’s Claude Code plugins so agents navigate living, feature-driven documentation and semantic code relationships without leaving the editor.
Who is it for?
Best when you're already investing in Manifest-style living documentation and want Claude Code wired to that graph.
Skip if: Greenfield projects with no documentation discipline who only need a one-off code generator skill.
What you get
After registration, Claude Code can use Manifest’s plugins to traverse living docs and semantic relationships like callers, definitions, and dependencies.
- Two enabled Manifest Claude Code plugins from one catalog source
- Agent-accessible semantic navigation aligned with documentation
- Reduced friction moving between product docs and implementation
By the numbers
- Catalog lists 2 plugins under manifestdocs/claude-plugins
- Thirteen plugin keywords including manifest, rocketindex, semantic, navigation, featuredriven
- Repository: manifestdocs/claude-plugins
Recommended Plugins
0xbigboss Linear CliLinear CLI built with Zig1
15195999826 LomomarketplaceLomo's Claude Code Plugin Marketplace1
1broseidon MarketplaceCurated collection of Claude Code plugins for fullstack development teams1
4rgon4ut Cc Zig LspZig LSP plugin for Claude Code4
708u TwigSimplify git worktree and branch management with configurable symlinks, change carrying, and cleanup.22
8avalon8 AvalonclaudemarketAvalon 的 Claude Code 插件市场How it compares
Manifest documentation MCP plugin pack, not a generic markdown-writing skill.
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.