doc-condenser

> **DEPRECATED** — Modern Claude models condense and summarize technical documentation > natively with comparable quality. The output format preferences encoded here (40% length > cap, tables over prose, paths first) are too generic to justify skill overhead. Retained > for archival reference only. # Document Condenser Transform verbose technical documentation into concise, developer-focused specs. ## Core Principles 1. **Paths first** - Every file reference includes full/relative path 2. **Tables over prose** - Use tables for metrics, coverage, file lists 3. **Code samples stay** - Keep small, illustrative snippets; remove verbose examples 4. **Commentary, not explanation** - Brief context sentences, not paragraphs 5. **One-line history** - Reference legacy docs, don't preserve their content ## Output Structure ```markdown # [path/to/output.md] # [Title] - [Subtitle if needed] ## Purpose [2-3 sentences: what this is, why it exists, key design principle] ## Status [Table: metrics, rates, performance] ## Architecture Overview [Optional diagram or brief flow description] [Only if it aids understanding] ## Implementation Files [Grouped by category with paths and one-line descriptions] ## [Domain-Specific Sections] [Tables, code snippets, brief commentary as needed] ## Quick Reference [Box or code block with key stats for scanning] ``` See `assets/template.md` for a copy-ready scaffold of this structure. ## Transformation Rules ### KEEP - File paths (always...