Total 43,555 skills, Documentation & Writing has 1289 skills
Showing 12 of 1289 skills
Review and edit copy for grammar, style, and clarity. Works with project style guides or uses sensible defaults. Use when reviewing marketing copy, blog posts, documentation, emails, or any business writing that needs polish.
Review technical prose for accessibility, jargon density, and gatekeeping language. Ensures content passes the 'Grandma Test' and avoids 'obviously', 'simply' (Gatekeeping). Use this to refine technical explanations.
Comprehensive writing guide for Angular documentation (adev). Covers Google Technical Writing standards, Angular-specific markdown extensions, code blocks, and components. Use when authoring or reviewing content in adev/src/content.
Documentation guidelines for Mastra. This skill should be used when writing or editing documentation for Mastra. Triggers on tasks involving documentation creation or updates.
Writing and authoring Quarto documents (.qmd), including code cell options, figure and table captions, cross-references, callout blocks (notes, warnings, tips), citations and bibliography, page layout and columns, Mermaid diagrams, YAML metadata configuration, and Quarto extensions. Also covers converting and migrating R Markdown (.Rmd), bookdown, blogdown, xaringan, and distill projects to Quarto, and creating Quarto websites, books, presentations, and reports.
Generate high-quality, "All-Star" README files for open-source repositories. Use this skill when a user asks to create, update, or improve a README.md file for their project.
API documentation workflow for generating OpenAPI specs, creating developer guides, and maintaining comprehensive API documentation.
Technical writer specializing in the Diátaxis documentation framework
Generate academic research proposals for PhD applications. Use when user asks to "write a research proposal", "create PhD proposal", "generate research plan", "撰写研究计划", "写博士申请", "doctoral proposal", or mentions specific research topics for PhD application. Supports STEM, humanities, and social sciences with field-specific adaptations. Follows Nature Reviews-style academic writing conventions. Supports both English and Chinese output based on user preference.
Akademiskt skrivande med vetenskaplig stringens — svenska eller engelska. [VAD] Uppsatser, rapporter, avhandlingar, litteraturöversikter, papers enligt högskolestandarder. IMRAD-struktur, Harvard/APA-referenshantering. Tvåspråkig skill. [NÄR] Use when: akademisk, vetenskaplig, uppsats, rapport, avhandling, litteraturöversikt, forskningstext, Harvard-referens, APA-referens, kandidat, master, doktorand, paper, thesis [SPRÅK] Svenska eller engelska — matcha input eller fråga [EXPERTISE] Academic writing, methodology, source criticism, qualitative/quantitative (SV/EN)
Systematic documentation audit and maintenance. This skill should be used when documentation may be stale, missing, or misorganized — after feature work, refactors, dependency upgrades, or as a periodic health check. It prescribes folder structure for docs/ and manual/, dispatches haiku subagents for codebase/doc scanning, and routes doc creation to specialized agents (reference-builder, technical-writer, learning-guide) with docs-architect as quality gate.
Use when you need to produce a D2 decision document (RFC/Decision Doc) for a Spec Pack, and need to independently decide whether to execute D0 (bypass design via diversion) and D1 (optional research) even under pressure, avoiding guessing FEATURE_DIR, making up input details, writing design as implementation specifics, or leaving behind TODO/To-Confirm lists.