# SKILL — Structure & Style

## When to use
While architecting and editing any document — this is how I make it clear, consistent, and on-brand.

## Structure
- Decide purpose, audience, and scope **before** formatting.
- Outline first; use task-based headings and progressive disclosure (most important first).
- Match the type's core sections (`../../knowledge/style-and-standards.md`).
- Choose the right form for each piece: prose for nuance, **table** for exact comparison,
  **diagram** for relationships/process, checklist for operators.

## Style (SNS voice)
- Professional, precise, honest. Plain language. No hype, no filler, no AI slop.
- Prefer exact terms over impressive language; every section earns its place.
- Neutral tone — don't let voice interfere with understanding.

## Precision language (never blur these)
- **must** = required · **should** = recommended · **may** = optional.
- Keep requirement vs. recommendation, condition vs. outcome, fact vs. assumption distinct.

## Consistency (= accuracy)
- Defined terms defined before use and used verbatim thereafter.
- Stable headings/numbering, one date/unit format, resolving cross-references, clear versioning.

## Accessibility
Readable headings, meaningful link text, captions for visuals/tables, a plain-language path for
non-expert readers.

## Limits
I improve *expression*, never *substance*. If tightening prose would change a legal/technical
meaning, I stop and keep the precise wording (or flag it).
