Loading...
Loading...
Found 56 Skills
Normalize terminology across a draft (canonical terms + synonym policy) without changing citations or meaning. **Trigger**: terminology, glossary, consistent terms, 术语统一, 统一叫法, 术语表. **Use when**: the draft has concept drift (same thing called 2–3 names) or global-review flags terminology inconsistency. **Skip if**: you are still changing the outline/taxonomy heavily (do that first). **Network**: none. **Guardrail**: do not add/remove citation keys; do not introduce new claims; avoid moving citations across subsections.
Create comprehensive troubleshooting guides, FAQ documents, known issues lists, and debug guides. Use when documenting common problems, error messages, or debugging procedures.
AI-powered comprehensive codebase documentation generator. Analyzes project structure, identifies architecture patterns, creates C4 model diagrams, and generates professional technical documentation. Use when users need to document codebases, understand software architecture, create technical specs, or generate developer guides. Supports all programming languages. Alternative to Litho/deepwiki-rs that uses Claude Code subscription without external API costs.
Core technical documentation writing principles for voice, tone, structure, and LLM-friendly patterns. Use when writing or reviewing any documentation.
Write AI-scannable technical documentation.
Use after brainstorming completes - writes validated designs to docs/design-plans/ with structured format and discrete implementation phases required for creating detailed implementation plans
Documentation and content creation standards for Markdown files. Use when writing, reviewing, or formatting Markdown documentation, README files, or technical content.
Technical documentation writer specializing in creating clear, well-structured markdown documents for algorithms, system design, interview preparation, and code documentation. Use when writing README files, algorithm explanations, system design docs, or technical guides.
Check all READMEs for accuracy and consistency across the meta-repo
Use when creating, updating, or generating README and documentation files for projects and libraries
Use for PLANNING documentation with phased analysis (4 phases), gap identification, and structured knowledge modeling. Best for documentation audits, completeness analysis, and documentation strategy planning. NOT for writing actual docs (use tasks-documentation instead).
Write documentation, help articles, specs, and user-facing text in the authentic Grove voice. Use when writing any text that users will read, updating help center content, or drafting specs. Ensures warmth, clarity, and avoidance of AI patterns.