design-docs-plugin

Generate cross-reference graph showing relationships between design documents. Use when visualizing doc dependencies, finding related docs, or understanding documentation structure.

Validate design doc structure and frontmatter. Use when checking design docs for compliance, ensuring proper formatting, or verifying metadata before commits.

Comprehensive quality audit for CLAUDE.md context files. Use when performing thorough quality checks, preparing for releases, ensuring context efficiency, or verifying token optimization.

Style rules for LLM context files (CLAUDE.md, AGENTS.md and their .local variants). Fires automatically when these files are opened. Enforces on-demand loading patterns, proper @-reference syntax and lean context structure.

Split large CLAUDE.md into child files. Use when context files exceed word limits, are too verbose, or cover multiple distinct topics that should be separate.

Validate CLAUDE.md structure, formatting, and quality. Use when checking context files for compliance, ensuring proper structure, or verifying before commits.

Archive outdated design documentation. Use when design docs are no longer relevant, have been superseded, or document deprecated features.

Comprehensive health audit for design documentation. Use when performing thorough quality checks, preparing for releases, or ensuring documentation compliance.

Compare doc versions across git history. Use when reviewing changes, tracking evolution, or understanding modifications.

Manage design documentation system configuration. Use when initializing the system, adding modules, or updating quality standards.

Export to PDF/HTML/markdown. Use when distributing documentation, creating presentations, or archiving design docs.

Generate table of contents for design documentation. Use when creating navigation, documentation overview, or module index pages.

Initialize new design documentation from templates. Use when creating new design docs, documenting new systems, starting architecture documentation, or setting up design docs for a new module.

Remove historical cruft from design docs. Use when docs accumulate outdated content, after major refactorings, or when preparing for releases.

Generate status reports for design documentation. Use when creating documentation summaries, tracking progress, or preparing documentation reviews.

Review and analyze design docs for health, quality, and improvement opportunities. Use when auditing design documentation, checking doc health, or identifying areas for improvement.

Full-text search across design documentation. Use when looking for specific topics, decisions, or patterns documented across design docs.

Split an oversized design doc into atomic, cross-referenced pieces. Use when a design doc covers more than one unrelated subsystem or has grown far larger than its peers in the same module.

Sync design docs with codebase state. Use when verifying documentation accuracy, after code changes, or when last-synced is stale.

Update specific design document with new content or metadata. Use when modifying design docs, updating status/completeness, or syncing after code changes.

Generate Level 2 (repository docs) from design docs. Use when creating comprehensive topic-based documentation for developers.

Generate Level 3 (documentation sites) from design docs. Use when creating feature-rich, interactive documentation for RSPress/Docusaurus sites.

Complete a plan by updating design docs and removing the transitory plan file. Use when implementation is finished and knowledge should be persisted to design documentation.

Create new plan documents from templates. Use when starting new implementation work, documenting planned features, or organizing development tasks.

Explore implementation plans, status, and relationships. Provides comprehensive plan ecosystem navigation with filtering, health analysis, and actionable recommendations.

List and filter plan documents. Use when exploring plans, checking status, finding plans by module, or reviewing plan health.

Validate plan document structure and frontmatter. Use when checking plans for compliance, ensuring proper formatting, or verifying metadata before commits.

Auto-loads design documentation style rules when .claude/design/**/*.md files are read. Enforces focused, boundary-level documentation over exhaustive code re-documentation.

Autonomous top-to-bottom overhaul of design docs — validate, restyle, resync against code, prune stale context, split oversized docs, reconcile cross-references, update CLAUDE.md references, then commit. Runs unattended with no confirmation gates. Use to groom design documentation before a review or release.

Generate CONTRIBUTING.md for developer onboarding. Use when creating or updating contribution guides with setup instructions and development workflows.

Generate SECURITY.md for vulnerability reporting. Use when creating or updating security policies with supported versions and reporting instructions.

Review package.json for completeness and best practices. Use when auditing metadata, checking dependency versions, or validating peerDependencies.

Sync user documentation with design doc changes. Use when design docs have been updated and user docs need to reflect the changes.

Comprehensive documentation review and update. Use before merging branches to ensure all docs are current, complete, and consistent.

End-of-branch workflow. Dispatches the design-doc, context-doc, and user-docs agents to update every documentation layer, then creates a changeset, squashes commits, pushes, and opens a PR. Use when finishing work on a branch before merge.

Capture the current task state into .claude/handoffs/HANDOFF.md so a fresh Claude Code session can resume the work, or read a pending handoff back into context. Bidirectional — writes a handoff when none is pending, resumes one when it exists.

Fetch and address PR review feedback. Filters resolved/outdated comments, triages by severity, makes fixes, runs lightweight doc check, commits and pushes. Use during PR review cycles.

Review CLAUDE.md files for quality, efficiency, and structure. Use when auditing LLM context files, checking documentation organization, preparing for context optimization, or ensuring lean imperative instructions.

Update CLAUDE.md files to improve efficiency and structure. Use when optimizing LLM context files, implementing review recommendations, splitting large files, or adding design doc pointers.

Final squash of all branch commits into one clean commit and force push for merge. Use after PR approval, before merging.