Loading...
Loading...
Found 63 Skills
Write, review, and restructure useful documentation with Diataxis, audience-specific README patterns, and AI-writing trope cleanup. Use when creating docs, improving READMEs, reorganizing documentation, or editing prose for clarity.
Generate clean, minimal technical SVG diagrams in a consistent Cloudflare-inspired style. Use when creating architecture diagrams, flow diagrams, or component diagrams for blog posts and documentation.
Transforms technical documents into rigorous learning journeys with collegiate-level mastery requirements. Uses Bloom's taxonomy progression, 80%+ mastery thresholds, and multi-level verification before advancing. Treats learning as a high school to college graduation progression. Use when user wants deep understanding, not surface familiarity.
Write detailed embodiment descriptions for patent specifications. Use when user says "撰写实施例", "write embodiment", "实施例描述", "detailed description", or wants to describe how to practice an invention.
Create an Architecture Decision Record (ADR) in canonical MADR v4 format capturing the why behind a significant technical choice. Use when user says 'document this decision', 'create an ADR', 'record architecture decision', 'why did we choose X', 'document the rationale', or when adding major dependencies, new frameworks, or changing fundamental patterns. Do NOT use for user-facing feature docs (use document-feature) or syncing existing docs (use update-doc).
README style guide for concise, direct documentation. Use when writing or editing README files.
Creates an Architecture Decision Record (ADR) documenting a significant technical decision, its context, alternatives considered, and consequences. Every major technical choice should have an ADR.
Readme Generator - Auto-activating skill for Technical Documentation. Triggers on: readme generator, readme generator Part of the Technical Documentation skill category.
Adopts the rigorous, witty, and data-dense persona of a Sub-millimetre (sub-mm) Astrophysicist. Ideal for technical documentation, academic summaries, or transforming mundane topics into high-stakes scientific discourse.
Prompt for creating detailed feature implementation plans, following Epoch monorepo structure.
After architecture is complete, produces a flat actionable rules sheet for programmers — what you must do, what you must never do, per system and per layer. Extracted from all Accepted ADRs, technical preferences, and engine reference docs. More immediately actionable than ADRs (which explain why).
Expert in creating clear, comprehensive technical documentation with Nextra (Next.js-based docs framework), MDX, and modern documentation patterns. Use for documentation sites that need Next.js integration.