document-designerlisted

# Document Designer Design the editable document source and its presentation intent. Preserve facts, uncertainty, citations, code, and semantic meaning; do not fill content gaps with invented claims. ## Design 1. Identify audience, reading goal, document type, required sections, language, target medium, and provided brand constraints. Treat missing visual preferences as reversible design choices. 2. Read only the references needed for the document: - [typography.md](references/typography.md) for hierarchy, readable type roles, and multilingual fallback. - [page-layout.md](references/page-layout.md) for spacing, page flow, figures, and print intent. - [tables-and-callouts.md](references/tables-and-callouts.md) for dense data, warnings, notes, and code. - [design-tokens.md](references/design-tokens.md) when defining or selecting reusable tokens. 3. Establish the information hierarchy before styling. Keep one H1, use ordered heading levels, lead with the outcome, group related evidence, and remove decorative repetition. 4. Create or revise `source.md` as the semantic source of truth. Use Markdown structure rather than visual spacing characters, manual line wrapping, or embedded presentation hacks. 5. Create `document-design.yaml` beside the source when the publisher needs explicit choices. Include `document_type`, `audience`, `language`, `target`, `theme`, `density`, `toc`, `page_break_hints`, `font_fallback`, and `accessibility_notes`. Ma