Total 54,044 skills, Documentation & Writing has 1524 skills
Showing 12 of 1524 skills
Expert C4 Container-level documentation specialist. Synthesizes Component-level documentation into Container-level architecture, mapping components to deployment units, documenting container interfaces as APIs, and creating container diagrams. Use when synthesizing components into deployment containers and documenting system deployment architecture.
Web development guidelines covering Bootstrap, Django, HTMX, and general web best practices
Expert in creating clear, accurate, and user-friendly documentation. Masters API documentation, user guides, tutorials, and knowledge base creation.
Converts technical work into compelling narratives for demos, blog posts, or presentations. Use when preparing hackathon demos, writing technical blog posts, or creating marketing content. Transforms: PR descriptions, commit histories, feature implementations into structured stories. Formats: demo scripts, blog posts, presentation outlines, marketing copy.
Diagnose genre problems and generate genre-specific elements. Use when genre promise is unclear, when elements feel misplaced, when secondary genres compete with primary, or when you need genre-specific entropy. Covers all 11 elemental genres from the Writing Excuses framework.
Create and deliver effective technical presentations, demos, and talks. Provides frameworks for structuring content, designing slides, and handling live demos.
Expert C4 Context-level documentation specialist. Creates high-level system context diagrams, documents personas, user journeys, system features, and external dependencies. Synthesizes container and component documentation with system documentation to create comprehensive context-level architecture. Use when creating the highest-level C4 system context documentation.
This skill should be used when content teaches patterns (skills, subagents, ADRs, PHRs, specifications) that have canonical sources elsewhere. Prevents format drift by ensuring content references and follows the authoritative format from canonical sources. Use before implementing lessons that teach platform patterns, or when reviewing content for format consistency.
Workflow navigation assistant that recommends next steps and optimizes documentation sequence through the SDD workflow
Use this when the user wants to review, polish, or proofread articles. Triggers include requests such as "polish my article", "check this", "revise my writing", "proofread this", "look over my article"
Use this when users need help starting or continuing their writing (not diaries). Trigger scenarios include "don't know what to write", "help me brainstorm", "write a travelogue", "record TIL", "write something". For diary writing, please use the diary-assistant skill instead.
Systematically identify what's missing in non-fiction writing—both blind spots (inherent limitations) and blank spots (gaps that could be addressed). Use before finalizing non-fiction or when feedback feels incomplete.