Total 52,119 skills, Documentation & Writing has 1490 skills
Showing 12 of 1490 skills
Advanced 47-marker voice analysis engine — analyzes your writing to build a comprehensive Voice Profile for AuthorClaw
Run /document `pr` | `changelog` | `release-note` | `postmortem` (or let it ask) to write the human facing prose about a change. Drafts from the real commits and diff, writing to the right place. Does not write code, tests, or specs.
Use when writing blog posts or documentation markdown files - provides writing style guide (active voice, present tense), content structure patterns, and MDC component usage. Overrides brevity rules for proper grammar. Use nuxt-content for MDC syntax, nuxt-ui for component props.
Generate architectural wikis with source code traceability. Creates comprehensive documentation including architecture overviews, module docs, data flow diagrams, and interactive static sites. Use when asked to document a codebase, generate architecture docs, create a wiki, or explain how a project is structured.
This skill should be used when the user needs to create a personalized, compelling cover letter from a resume and job description. Use when writing job application letters, addressing specific role requirements, handling career change narratives, or structuring persuasive arguments for candidacy.
Editorial review skill for Orbitant engineering blog posts. Activates when reviewing, editing, or providing feedback on blog articles. Produces structured reviews covering SEO, content quality, tone, and actionable improvements. Responds in the same language as the article being reviewed. Use this skill whenever someone asks to review a blog post, wants editorial feedback on a draft, needs SEO analysis for an article, or requests writing improvements for the Orbitant blog — even if they don't explicitly mention "review".
Create a standard PRD document package structure. Call it when starting a new project or initializing a PRD workspace.
Spatial organization of knowledge in navigable directories
Transform writing samples into a codified voice style that can be replicated consistently. This wizard guides you through analyzing samples, extracting patterns, and generating a custom voice skill.
New Zealand business English writing style for professional communications. Warm, inclusive, EN-NZ spelling. Use when writing emails, chat messages, proposals, client communications, or any business writing for New Zealand SME audiences. Applies to drafting, editing, and tone-checking any professional text.
ISD 연구계획서 통합 입력 템플릿 - Orchestrator용 입력 양식
Write or update external guide documents for the project —— dev-guide (for contributors / integrators / downstream developers) and user-guide (for end users). The output is stored in the project's docs/ directory, maintained alongside the code, and searchable by search tools. Difference from libdoc: guidedoc is task-oriented ("How to do Y with X"), while libdoc is reference-oriented ("What each part of X looks like"). Trigger scenarios: When the user says "write documentation", "developer guide", "user guide", or proactively push when feature-acceptance is completed.