Total 43,930 skills, Documentation & Writing has 1297 skills
Showing 12 of 1297 skills
Generates comprehensive blog post drafts with proper structure. Use when the user asks to write a full article, create blog content, draft long-form posts, or needs complete written content with SEO optimization.
Writing technical blog posts about tldraw features and implementation details. Use when creating blog content about how tldraw solves interesting problems.
ASCII architecture diagrams for ADRs via graph-easy. TRIGGERS - ADR diagram, architecture diagram, ASCII diagram.
Optimize CLAUDE.md and docs/ ecosystem following Boris Cherny's best practices
Web development guidelines covering Bootstrap, Django, HTMX, and general web best practices
Use when creating or formatting tables in markdown. Covers table syntax, alignment, escaping, and best practices.
This skill provides one-page synopsis writing techniques for screenplays. Covers the five requirements of a good synopsis, synopsis vs treatment comparison, and formatting for submission to producers and executives. Use when: preparing submission materials, creating one-page story summaries, pitching to producers or executives, or condensing screenplay for coverage.
Explains code with visual diagrams and analogies. Use when explaining how code works, teaching about a codebase, or when the user asks "how does this work?"
Expert in creating clear, accurate, and user-friendly documentation. Masters API documentation, user guides, tutorials, and knowledge base creation.
Synthesize evidence into a structured narrative (`output/SYNTHESIS.md`) grounded in `papers/extraction_table.csv`, including limitations and bias considerations. **Trigger**: synthesis, evidence synthesis, systematic review writing, 综合写作, SYNTHESIS.md. **Use when**: systematic review 完成 screening+extraction（含 bias 评估）后进入写作阶段（C4）。 **Skip if**: 还没有 `papers/extraction_table.csv`（或 protocol/screening 尚未完成）。 **Network**: none. **Guardrail**: 以 extraction table 为证据底座；明确局限性与偏倚；不要在无数据支撑时扩写结论。
Write comprehensive technical documentation including user guides, how-to articles, system architecture docs, onboarding materials, and knowledge base articles. Creates clear, structured documentation for technical and non-technical audiences. Use when users need technical writing, documentation, tutorials, or knowledge base content.
Coordinates project documentation creation. Gathers context once, detects project type, delegates to 5 L3 workers (ln-111-115). L2 Coordinator invoked by ln-100.