Total 30,584 skills, Documentation & Writing has 1022 skills
Showing 12 of 1022 skills
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.
Diagnose world-level story problems. This skill should be used when settings feel thin, institutions feel designed rather than evolved, economies don't make sense, or non-human species feel like humans in costume. Keywords: worldbuilding, setting, world, institutions, economy, culture, species, consequences.
Write node content documents. Read download.txt, integrate local materials for each node and write detailed, accurate, and complete Markdown documents. Each sub-agent processes one node in parallel, outputting a complete node document including overview, directory/mind map, flow chart, online image URL, and reference materials. Suitable for scenarios requiring systematic and structured content creation.
Create excellent technical documentation with Mermaid diagrams. Use when documenting code architecture, API flows, database schemas, state machines, system design, or any technical concept that benefits from visual diagrams. Also use when asked to explain code, create documentation, write README files, or document how systems work.
Design and troubleshoot character transformation arcs. Use when characters feel static, when transformation feels unearned or abrupt, when you can't articulate what false belief needs to die, or when characters serve plot without having internal journeys. Covers positive, negative, and flat arcs.
Maintain a wiki-style world bible for collaborative fiction. Use for long-running story worlds, shared universes, membership sites, or any fiction requiring persistent canonical reference.
Act as an assistive writing coach who guides but never writes for the user. Use when helping someone develop their own writing through questions, diagnosis, and frameworks. Critical constraint - never generate story prose, dialogue, or narrative content. Instead ask questions, identify issues, suggest approaches, and let the writer write.
Documentation generation patterns for technical specs, API docs, user guides, and knowledge bases using real tools like Sphinx, MkDocs, TypeDoc, and Nextra. Use when creating docs from code, building doc sites, or automating documentation workflows.
Expert sales proposal and pricing presentation strategist. Use when writing proposals, executive summaries, ROI business cases, pricing presentations, SOWs (Statement of Work), RFP responses, or competitive positioning documents. Covers proposal structure, terms positioning, design formatting, follow-up strategy, and win-rate optimization.
Extract and document a writer's distinctive voice patterns for consistent reproduction. Use when you need to capture writing voice, analyze writing style, create a voice guide, or write in someone's established style. Keywords: voice, tone, style, writing analysis, fingerprint.
Remove AI-generated traces from text. Suitable for editing or reviewing text to make it sound more natural and human-written. A comprehensive guide based on Wikipedia's "Signs of AI Writing". Detect and fix the following patterns: exaggerated symbolism, promotional language, superficial analysis ending with -ing, vague attribution, overuse of dashes, rule of three, AI vocabulary, negative parallelism, excessive connective phrases.
Act as an active writing partner who contributes content alongside the human writer. Use when the writer wants a collaborator who generates prose, dialogue, alternatives, and builds on their ideas. Applies Story Sense frameworks while actively contributing to the creative work. Contrasts with story-coach which never writes.