Total 54,113 skills, Documentation & Writing has 1536 skills
Showing 12 of 1536 skills
Crear o actualizar Architecture Decision Records (ADRs) en docs/adr/. Activar siempre que el usuario quiera documentar, registrar, actualizar o cambiar el estado de una decisión arquitectónica — incluso si no usa la palabra "ADR". Frases que activan este skill: "registrar decisión", "documentar por qué usamos X", "dejar constancia de esta elección técnica", "decision record", "cambiar ADR a Accepted", "marcar como Superseded", "crear ADR", "actualizar ADR", "nuevo ADR", "ADR-XXX". Usar también cuando el usuario describa una tensión arquitectónica que deba quedar documentada.
Review generated or changed documentation before it ships — READMEs, API references, docstrings, PHPDoc/JSDoc, changelogs, tutorials, and doc sites. Best used reactively after an agent writes or edits docs, after code changes documented behavior, or before publishing docs. Use when the user says 'review the docs', 'is this documentation accurate', 'update the docs', 'write a README', 'document this API', 'add a docstring', or 'add a changelog entry'. Core job: verify every referenced function, flag, endpoint, config key, and code sample against the source; catch docs-vs-code drift; strip filler and unverifiable claims. DO NOT USE for production code review (use clean-code-guard), test review (use test-guard), marketing copy or blog posts, prose style editing of non-technical writing, or documentation site theming.
Read and comprehend story texts, summarize characters, relationships, and plots, and organize them into a coherent outline. Suitable for quickly grasping the core of a story and providing an outline foundation for script creation
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.
General Chinese Creation and Revision Skill. Applicable to Zhihu answers, forum long posts, official account articles, blogs, comments, character stories, historical narratives, news and industry interpretations, popular science, tutorials, reviews, personal narratives, novels, stories, dialogues, oral broadcasts, and speeches. Defaults to writing in the voice of someone who has experienced things, checked materials, and is willing to explain the ins and outs clearly, focusing on retaining the authentic human touch and natural Chinese rhythm of long answers and posts on the Chinese internet, while avoiding empty institutional tones, slogan-style speech tones, marketing tones, and AI model tones. For non-fiction long articles, first check if the materials are sufficient; if not, conduct research, ask questions, or shorten the article, and never pad the word count with repetitive explanations. Verify facts, quotes, data, and user experiences for real-world content; for fictional content, characters, scenes, dialogues, psychology, and plots can be created. Colons, dashes, phrases like "not...but..." and similar counterargument structures are strictly prohibited in the final draft, and business jargon and AI model jargon should be removed. Do not create author profiles, personal rule libraries, or personal writing Skills.
Document frontend data needs for backend developers. Use when frontend needs to communicate API requirements to backend, or user says 'backend requirements', 'what data do I need', 'API requirements', or is describing data needs for a UI.
Document session work with explicit commands. Use /start to begin tracking, /end to finalize session, /clear to reset. Tracks decisions, file changes, and context for continuity.
Use when user mentions fantasy, magic system, or world-building for fantastical settings - provides fantasy genre conventions, magic system design patterns, and world-building frameworks
Write content that sounds natural, conversational, and authentically human - avoiding AI-generated patterns, corporate speak, and generic phrasing
Use when writing blog posts or documentation markdown files - provides writing style guide (active voice, present tense), content structure patterns, and SEO optimization. Overrides brevity rules for proper grammar.
Audit project documentation quality across 8 categories (Hierarchy, SSOT, Compactness, Requirements, Actuality, Legacy, Stack Adaptation, Semantic Content). Delegates to ln-601 for deep semantic verification of project documents. Use when documentation needs quality review, after major doc updates, or as part of ln-100-documents-pipeline. Outputs Compliance Score X/10 per category + Findings + Recommended Actions.
Maintains changelogs following Keep a Changelog format, categorizes changes by type. Use when updating CHANGELOG, preparing releases, or documenting version changes.