Loading...
Loading...
Found 76 Skills
Create repo-grounded TeX specs and companion PDFs. Use for LaTeX technical specs, algorithm-heavy plans, and phased implementation docs.
Guides for writing and editing Remotion documentation. Use when adding docs pages, editing MDX files in packages/docs, or writing documentation content.
How-To guide patterns for documentation - task-oriented guides for users with specific goals
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).
Generate or sync a "Living Specification" (docs/spec.md) from source code to eliminate doc-code drift. Use when creating, updating, or reviewing architecture documentation for a directory or module. Triggers on requests like "generate spec", "create spec.md", "sync documentation", "update architecture docs", "/spec.doc", or when asked to document a codebase directory.
Apply OceanBase documentation formatting standards including meta tables, notice boxes, spacing, and markdown lint compliance. Use when formatting or reviewing OceanBase documentation.
Behavior Guidelines for Information Visualization Presentation. Automatically activated when the model's response contains structured information such as comparisons, steps, configurations, architectures, etc., ensuring priority use of visual formats like tables, code blocks, lists, tree structures, instead of pure text accumulation. Trigger words: "Use a table", "Draw a diagram", "Make a list", "Structure it", "Don't just use text", "Visualize", "Compare". Even without trigger words, the rules of this Skill should take effect as long as the response contains structured information suitable for visualization. It also applies to scenarios such as "Too much text to read", "Can it be more intuitive?", "Organize into a table".
Documentation standards, API docs, and technical writing guidelines
You are a documentation expert specializing in creating comprehensive, maintainable documentation from code. Generate API docs, architecture diagrams, user guides, and technical references using AI-powered analysis and industry best practices.
Explanation documentation patterns for understanding-oriented content - conceptual guides that explain why things work the way they do
Research a specific system and create or update its blueprints/ documentation
When the user wants to create, optimize, or structure a changelog or release notes page. Also use when the user mentions "changelog," "release notes," "what's new," "updates," "product updates," "version history," or "changelog.yourdomain.com."