Total 50,341 skills, Documentation & Writing has 1451 skills
Showing 12 of 1451 skills
Construct well-structured arguments using the hypothesis-argument-example triad. Covers formulating falsifiable hypotheses, building logical arguments (deductive, inductive, analogical, evidential), providing concrete examples, and steelmanning counterarguments. Use when writing or reviewing PR descriptions that propose technical changes, justifying design decisions in ADRs, constructing substantive code review feedback, or building a research argument or technical proposal.
Draft a detailed Non-Disclosure Agreement between two parties covering information types, jurisdiction, and clauses needing legal review. Use when creating confidentiality agreements or preparing an NDA for a partnership.
Use when the user asks to document an implemented feature. Analyze the diff from the base branch, infer the feature boundary and name, and generate behavioral feature documentation under docs/features/.
Conventions for writing, organizing, and browsing documentation in a docs/ directory using docfront. Use when creating documents, restructuring documentation, or unsure about frontmatter format and file naming conventions.
Collaborate on document creation and refinement. Merges contributions, manages versions, and produces unified documents from multiple sources.
Draft publication-ready Results/Findings sections for quantitative sociology articles. Guides cluster selection, arc construction, paragraph-level moves, and writing techniques based on genre analysis of 83 Social Problems/Social Forces articles across secondary-survey, administrative-data, and content-analysis methods. Use when the user wants to write, draft, or revise a Results section for a quantitative or content-analysis paper. Also use when the user asks for help structuring findings, organizing results, or translating statistical output into publication-ready prose.
Write clear, engaging technical content from real experience. Use when writing blog posts, documentation, tutorials, or technical articles.
Remove signs of AI-generated writing from text. Use when editing or reviewing any content to make it sound more natural and human-written. Catches patterns like inflated language, rule of three, em dash overuse, vague attributions, copula avoidance, negative parallelisms, synonym cycling, filler phrases, excessive hedging, and soulless structure. Use when someone says "humanize this", "this sounds like AI", "make this sound human", "remove the AI", "clean this up", "de-AI this", "this reads like ChatGPT", or when reviewing any AI-assisted draft before publishing. Also use as a final pass on content from other skills like boring-remix or social-content. World Code integrated — applies voice.md rules when available.
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.
Creates Architecture Decision Records (ADRs) to document significant architectural choices and their rationale for future team members. Use when the user says "write an ADR", "document this decision", "record why we chose X", "add an architecture decision record", "create an ADR for", or wants to capture the reasoning behind a technical choice so the team understands it later. Do NOT use when the decision hasn't been made yet (use create-rfc instead), for implementation planning (use technical-design-doc-creator), or for general documentation.
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).
Technical documentation expert for creating clear, comprehensive documentation. Use when user asks to write docs, create README, or document code.