Discover tools technical docs skills, compare source repositories and read the instructions for each workflow.
Use when writing or updating documentation - generates function docs, API specs, architecture diagrams (Mermaid), READMEs, code explanations. Activates when user says "document this", "write README", "explain t...
ドキュメント、README、コードコメントを書く際に使用。
Write TSDoc-compliant code comments in English for TypeScript/JavaScript. Trigger: When adding documentation comments, documenting functions/classes, or improving code clarity.
Write clear, structured documentation for any project. Trigger: When writing READMEs, API docs, user guides, or technical documentation.
Navigate and work with interconnected markdown documentation. Use when reading, writing, or validating markdown documents in mddocs/, or when following links between documents.
Autonomous documentation maintainer that ensures code changes are reflected in documentation
Provides Chinese technical documentation writing guidelines. Use when creating new technical guides, editing existing docs to follow standards, or reviewing document format and structure.
Guide users through structured co-authoring, improvement, and QA of documentation. Use when users want to write or improve docs such as proposals, technical specs, decision docs, READMEs, guides, API docs, or r...
Creates individual AI-ready documentation files with proper structure, frontmatter, and validation. Use when writing or improving documentation that AI tools must process effectively. Triggers on "write documen...
Analyze a specific topic and produce a comprehensive markdown report in docs/analysis/
Documentation best practices and templates. Use when writing READMEs, API documentation, changelogs, or code comments. Provides templates, style guides, and documentation-as-code patterns.
Java language best practices and idioms. Use when writing, reviewing, or debugging Java code. Provides modern Java patterns, Spring Boot, testing, and architecture guidance.
Read and summarize the current state of the documentation hub. Provides a quick overview of system architecture, module responsibilities, technology stack, and glossary terms.
Bootstrap a new project's documentation hub by creating the four core documentation files (systemArchitecture.md, keyPairResponsibility.md, glossary.md, techStack.md) with initial content based on codebase anal...
Review specification and developer documents for compliance with project guidelines. Use when checking docs-spec/ and docs-site/docs/ for ambiguous expressions or missing required sections.
Generate API documentation, component docs, schema docs, and changelogs. Use when documenting new endpoints, creating component documentation, updating READMEs, or writing release notes.
Generate comprehensive learning documents by combining information from tickets, memories, GitHub PRs, and proposals. Use after completing significant work to capture lessons learned.
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.
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.
Generate Twoslash code examples for RSPress documentation. Use when adding type-rich, interactive code examples to documentation pages.
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.
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.