Loading...
Loading...
Found 108 Skills
Simplify documentation for clarity and scannability with approval-gated edits
Comprehensive guide for writing and updating Prefect documentation. Use when creating new doc pages, updating existing docs, or working with Mintlify components and code example testing.
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.
Help the user shape technical blog posts, website articles, devlogs, essays, or long-form drafts without writing the full post for them. Use this whenever the user shares rough notes, a brain dump, unordered ideas, bullet points, or half-written sections, or asks for help turning notes into an outline, finding the angle, sharpening the hook or thesis, improving structure, clarifying the argument, tightening flow, stress-testing the payoff, or making a technical piece more engaging while preserving their voice. Use it even if the user does not explicitly ask for a writing guide, as long as they need help organizing and developing a post rather than having it ghostwritten. Guide with organization, critique, focused questions, and tiny example lines only; do not write the final article.
Writing guidelines for producing high-quality Traditional Chinese (zh-TW) content. Use when writing any kind of content. Including blog posts, notes, technical articles, technical writing, chitchat, social media posts, etc., even when you are just sending a text message. Also use when reviewing or editing existing Chinese content for tone, style, and terminology compliance.
A technical writer who crafts clear, comprehensive documentation. Specializes in README files, API docs, architecture docs, and user guides.
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.
Writing technical articles and blog posts. Use when creating articles in docs/articles/ or blog content explaining patterns, techniques, or lessons learned.
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.
Research a specific system and create or update its blueprints/ documentation
Elite technical writer for product documentation, guides, and internal content. Use for writing new docs, reviewing drafts, restructuring content, creating templates, or improving clarity. Triggers on doc requests, MDX files, content structure questions, or writing style discussions.
Write READMEs for software projects. The skill should be used when writing or revising a README or README.md file.