Total 30,708 skills, Documentation & Writing has 1023 skills
Showing 12 of 1023 skills
Эксперт по API reference документации. Используй для создания справочников по API, описания endpoints и примеров запросов.
Эксперт по написанию API-туториалов и документации. Используй для создания гайдов по интеграции API, документации endpoints, примеров кода на разных языках, обработки ошибок и best practices.
Эксперт CONTRIBUTING.md. Используй для open source guidelines, PR процессов и contributor onboarding.
Transform reading notes and insights into polished, authentic content (blogs, social media, visualizations) that preserves your unique voice and avoids AI-style writing. Creates content that sounds unmistakably human.
Generates Architecture Decision Records (ADRs) capturing context, decision rationale, alternatives considered, and projected consequences. Produces numbered, status-tracked documents following the standard ADR format with proper metadata lifecycle. Triggers on: "write an ADR", "document this decision", "architecture decision record", "why did we choose", "capture this decision", "record the decision", "ADR for", "document the architecture", "decision record", "design decision", "technical decision". Use this skill when an architectural or technical decision needs to be documented.
Write LinkedIn posts matching a specific technical author's voice — direct, analytical, dry-humored, and precise. Use this skill whenever the user asks to write, draft, rewrite, review, improve, or refine a LinkedIn post, social media post, tech commentary, or any public-facing short-form writing about technology, AI, software engineering, or developer tools. Also trigger when the user says "write this in my style", "post about this", "rewrite this for LinkedIn", "draft a post in my style", "does this sound right", "how should I phrase this", or provides raw content/notes and wants it shaped into a post. Includes visual companion guidance for pairing posts with document carousels (via md-to-pdf with Mermaid diagrams), custom images (via concept-to-image), or animations (via concept-to-video).
Use when creating or iterating on a detailed per-subsystem technical design specification from a system spec, before starting OpenSpec workflow. Triggers: "design spec", "subsystem spec", "write the spec for S1", "phase breakdown", "implementation phases", "mid-level spec", "technical design". Encodes opinionated progressive phase discipline with FP progression and contract boundaries. Do NOT use for high-level system specs (use brainstorming) or for OpenSpec artifacts (use openspec directly).
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.
When the user wants to write, generate, or create article content—blog post body, long-form content, how-to guide, listicle. Also use when the user mentions "write article," "article content," "blog post content," "article body," "long-form content creation," "generate article," "article draft," "how-to guide content," or "listicle content." For article page structure, schema, and SEO metadata, use article-page-generator. For ad copy, landing page copy, or CTAs, use copywriting.
Full workflow for official account/self-media creation. Automatically match tasks based on user input: article writing, cover image, body illustration, style extraction. Supports multiple writing styles. It is used when users mention writing official account posts, technical blogs, official account covers, body illustrations, step diagrams, demo diagrams, flowcharts, writing style analysis, style cloning, imitating viral content, style extraction. See the reference directory for details.
Technical documentation expert for creating clear, comprehensive documentation. Use when user asks to write docs, create README, or document code.
Create a standard PRD document package structure. Call it when starting a new project or initializing a PRD workspace.