design-update
Update specific design document with new content or metadata. Use when modifying design docs, updating status/completeness, or syncing after code changes.
Discover DevOps skills, compare source repositories and read the instructions for each workflow.
Update specific design document with new content or metadata. Use when modifying design docs, updating status/completeness, or syncing after code changes.
Full-text search across design documentation. Use when looking for specific topics, decisions, or patterns documented across design docs.
Generate cross-reference graph showing relationships between design documents. Use when visualizing doc dependencies, finding related docs, or understanding documentation structure.
Archive outdated design documentation. Use when design docs are no longer relevant, have been superseded, or document deprecated features.
Configure RSPress navigation bars and sidebars with _nav.json and _meta.json files. Use when setting up navigation, organizing sidebar sections, or configuring collapsible menu items.
Configure RSPress frontmatter for documentation pages. Use when setting up page metadata, controlling layout options, or configuring home page hero/features sections.
Explore implementation plans, status, and relationships. Provides comprehensive plan ecosystem navigation with filtering, health analysis, and actionable recommendations.
Sync user documentation with design doc changes. Use when design docs have been updated and user docs need to reflect the changes.
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.
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.
Review user doc quality. Use when checking documentation completeness, accuracy, readability, and ensuring examples work correctly.
List and filter plan documents. Use when exploring plans, checking status, finding plans by module, or reviewing plan health.
Export to PDF/HTML/markdown. Use when distributing documentation, creating presentations, or archiving design docs.
Generate API documentation from TypeScript source code for RSPress. Use when documenting package APIs, extracting types from source code, or creating function/class reference pages.
Sync site docs with API changes. Use when APIs have been updated and documentation needs to reflect the changes.
Remove historical cruft from design docs. Use when docs accumulate outdated content, after major refactorings, or when preparing for releases.
Comprehensive health audit for design documentation. Use when performing thorough quality checks, preparing for releases, or ensuring documentation compliance.
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 instructi...
Create new plan documents from templates. Use when starting new implementation work, documenting planned features, or organizing development tasks.
Comprehensive quality audit for CLAUDE.md context files. Use when performing thorough quality checks, preparing for releases, ensuring context efficiency, or verifying token optimization.
Review RSPress documentation for quality and Twoslash issues. Use when checking docs for completeness, accuracy, and code example quality.
Sync design docs with codebase state. Use when verifying documentation accuracy, after code changes, or when last-synced is stale.
Automatically selects appropriate review perspectives based on file type and characteristics. Use when initiating code review to determine which review-points files should be applied.
Defines project-wide code conventions for magic number elimination, constant usage, performance optimization, and type safety. Use when implementing, testing, or reviewing code to ensure consistency across the...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.