← ClaudeAtlas

llm-doc-writerlisted

Write token-efficient documentation for LLM context. Use when creating CLAUDE.md, README, technical docs, agent instructions, or any documentation consumed by AI assistants.
aiskillstore/marketplace · ★ 329 · AI & Automation · score 79
Install: claude install-skill aiskillstore/marketplace
# LLM-Optimized Documentation ## Core Principles | Principle | Rule | |-----------|------| | **Density** | Max info, min tokens | | **Format** | Tables > prose, bullets > paragraphs | | **No fluff** | Ban filler words (see list below) | | **Show don't tell** | Code examples > explanations | | **Progressive disclosure** | TOC + separate files for details | ## Banned Patterns ``` # Filler words - NEVER use simplement, il suffit de, en fait, basically, just, simply, it's important to note, as mentioned, obviously, of course, please note that, keep in mind, remember that # Redundant structures - NEVER use "This file contains..." (obvious from filename) "In this section we will..." (just do it) "The following example shows..." (just show it) ``` ## Format Rules ### Tables over Prose ```markdown # BAD - 45 tokens The system supports three modes: development mode which enables hot reload, production mode which optimizes for performance, and test mode which mocks external services. # GOOD - 20 tokens | Mode | Behavior | |------|----------| | dev | Hot reload | | prod | Optimized | | test | Mocked services | ``` ### Bullets over Paragraphs ```markdown # BAD - Narrative To run the project, first ensure Node.js is installed, then install dependencies with npm install, and finally start the dev server with npm run dev. # GOOD - Scannable ## Run 1. Requires: Node.js 18+ 2. `npm install` 3. `npm run dev` ``` ### Code over Explanation ```markdown # BAD - Explaining To create a