Total 52,846 skills, Documentation & Writing has 1498 skills
Showing 12 of 1498 skills
Creates comprehensive Technical Design Documents (TDD) with mandatory and optional sections through interactive discovery. Use when user asks to "write a design doc", "create a TDD", "technical spec", "architecture document", "RFC", "design proposal", or needs to document a technical decision before implementation. Do NOT use for README files, API docs, or general documentation (use docs-writer instead).
How to build scenes: entry, dialogue, pacing, transitions. Use when writing or evaluating how scenes work on the page.
Write, rewrite, or edit user-facing text in the repo's preferred plain human style. Use for any prose task: docs, README sections, comments, release notes, PRDs, posts, emails, explanations, and requests to humanize or tighten text. Default to general prose rules; read references/documentation.md only for README, technical docs, usage guides, CLI/API docs, or documentation audits.
Rewrite Rust documentation comments to ensure all documentation and comments are in English, following rustdoc guidelines. Use when the user wants to clean up Rust documentation, translate Chinese comments to English, fix missing documentation, or ensure rustdoc compliance in a Rust codebase.
Use when the user wants to write, structure, or revise academic paper sections, improve notation consistency, or refine figures and tables. Triggers on phrases like "write the abstract", "structure the methods", "improve this section", "notation consistency", "figure refinement", or "paper structure".
Use when upgrading a public GitHub repository README, repo metadata, docs map, or first-impression brand surface to match the Zonic/Evensong proof-first standard.
Write, structure, or review a PhD/Master's research proposal. Use when drafting a research proposal, preparing for committee review, writing a thesis outline, or aligning methodology with academic requirements.
Extract academic tone rules from the corpus provided by the user in this round or the current manuscript, and make minimal adjustments. Use when the user asks for "Extract my PhD tone", "Check if the paper sounds like me", "Preserve author fingerprint", or requests the rw-phd-tone workflow. Runs without a private local workspace or preset research-lab; use user-provided material and bundled public-source methods.
Designs and develops specs following the spec-driven method. Asks clarifying questions before proposing structure, and builds the spec section by section. Use it when starting a large feature, before writing code.
Text formatting conventions for markdown and prose files. Use when writing or editing any .md, .txt, .adoc, or .rst file, including AGENTS.md, SKILL.md files, and documentation in docs/.
Generate reference documentation entry by entry for the public surface of libraries (components, functions, commands, etc.), with manifest tracking, supporting both single-entry and batch modes. Fundamental differences from guidedoc: guidedoc teaches you how to use things, while libdoc tells you what each part looks like; guidedoc's information sources are solution docs + user knowledge, while libdoc's information source is the source code itself. Trigger scenarios: When users say "write API documentation", "component documentation", "libdoc", "write documentation for each component", or when new public library interfaces are found after feature-acceptance.
Complete coaching skills for Taiwanese nursing staff to write evidence-based nursing reports (evidence-based reading reports, evidence-based case analyses), designed specifically for the N1–N4 nursing advancement system and the review formats of the Taiwan Nurses Association and Taiwan Evidence-Based Nursing Association. This skill must be triggered when users mention terms such as "evidence-based nursing report", "evidence-based case analysis", "evidence-based reading report", "N2 report", "N3 report", "N4 report", "nursing advancement report", "nursing promotion", "PICO", "5A Steps", "CASP Appraisal", "nursing EBP", "EBN", "evidence-based nursing", "evidence-based care", "evidence level", "literature appraisal", or when any nursing staff asks about promotion writing, transforming clinical problems into evidence-based topics, evidence-based literature search strategies, CASP appraisal forms, Oxford evidence levels, APA 7th edition format, applying evidence-based interventions to cases, challenging nursing routines, dispelling nursing myths, etc. Even if users casually say "I need to write a report", "I want to advance to N3", "Help me find a topic", "Help me set up PICO", "How to appraise this literature", this skill should be actively activated to provide complete structures, sentence patterns, and writing strategies with the highest review pass rate.