rspress-navigation
Generate progressive navigation structure for RSPress documentation. Use when setting up or reorganizing module documentation navigation.
Browse published AI skills maintained by savvy-web. Compare skill descriptions and follow each source repository for setup instructions.
Indexed skills
45Repository stars across indexed skills
0Repository forks
0Average repository stars per indexed skill
0Repository stars may repeat across skills from the same repository.
Generate progressive navigation structure for RSPress documentation. Use when setting up or reorganizing module documentation navigation.
Use RSPress built-in components and MDX features in documentation. Use when adding interactive elements like tabs, badges, steps, callouts, or code groups to documentation pages.
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.
Generate progressive learning guides for RSPress documentation. Use when creating concept docs, how-to guides, or example pages with Twoslash code blocks.
Validate design doc structure and frontmatter. Use when checking design docs for compliance, ensuring proper formatting, or verifying metadata before commits.
Compare doc versions across git history. Use when reviewing changes, tracking evolution, or understanding modifications.
Scaffold new RSPress documentation pages with proper structure and templates. Use when creating new docs pages, adding package documentation, writing guides, or setting up API reference pages.
Manage design documentation system configuration. Use when initializing the system, adding modules, or updating quality standards.
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.
Generate status reports for design documentation. Use when creating documentation summaries, tracking progress, or preparing documentation reviews.
Validate plan document structure and frontmatter. Use when checking plans for compliance, ensuring proper formatting, or verifying metadata before commits.
Generate Twoslash code examples for RSPress documentation. Use when adding type-rich, interactive code examples to documentation pages.
Validate CLAUDE.md structure, formatting, and quality. Use when checking context files for compliance, ensuring proper structure, or verifying before commits.
Split large CLAUDE.md into child files. Use when context files exceed line limits, are too verbose, or cover multiple distinct topics that should be separate.
Review and analyze design docs for health, quality, and improvement opportunities. Use when auditing design documentation, checking doc health, or identifying areas for improvement.
Generate Level 1 (README.md) user documentation from design docs. Use when creating or updating package README files for npm/GitHub.
Generate table of contents for design documentation. Use when creating navigation, documentation overview, or module index pages.
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.
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.