Total 44,044 skills, Documentation & Writing has 1302 skills
Showing 12 of 1302 skills
Design evolving language systems for fictional worlds. Use when creating language families, dialects, linguistic history, or when language should reflect cultural and historical development.
Structure multi-POV stories through catalyst environments. Use when building interconnected narratives, when perspectives need meaningful intersection, or when a shared setting needs to generate distinct storylines.
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.
Transform predictable story elements into fresh, original versions. Use when something feels generic, when feedback says "I've seen this before," when elements orbit the protagonist too conveniently, or when you want to make a familiar trope feel new. Applies the 8-step CTF process and Orthogonality Principle.
Design religious and belief systems for fictional worlds. Use when creating pantheons, religious institutions, spiritual practices, or any belief structures that shape society and drive character motivation.
Write winning proposals and quotes for a solopreneur business. Use when putting together a proposal for a potential client, structuring a sales document, pricing a project scope, or improving proposal win rates. Covers proposal structure, scoping, pricing presentation, objection pre-emption, and the psychology of persuasive proposals. Trigger on "write a proposal", "proposal template", "sales proposal", "quote for client", "how to structure a proposal", "proposal writing", "win more proposals", "client proposal".
Create comprehensive HTML architecture diagrams showing data flows, business objectives, features, technical architecture, and deployment. Use when users request system architecture, project documentation, high-level overviews, or technical specifications.
Final pass for rhythm, word choice, consistency, and a candid assessment of the finished piece
Generate MDX blog posts or recaps from session logs in `sessions/articles`. Use when the user asks to turn daily session notes into publishable blog posts, define writing style or linking rules for those posts, or produce MDX drafts that follow the project's standards and file location.
Voice and tone rules for all written content. Use when writing prose that should sound human and be suitable for reading aloud.
Generate or update PROJECT_MAP.md for user-specified folders. Applicable to scenarios where users request directory maps/project maps/repository overviews/folder-level descriptions/updating existing PROJECT_MAP.md. Must first ask for the folder scope to scan, default full-repository scanning is prohibited; supports single directory or multiple directories (combined or generated separately).
Creates 4 root documentation files (CLAUDE.md, docs/README.md, documentation_standards.md, principles.md). L3 Worker invoked by ln-110-project-docs-coordinator.