| name | trails-writing-style |
| description | Trails prose craft and lexicon style. Use when writing or reviewing docs, ADRs, examples, release notes, agent prompts, comments, PR descriptions, or issue language for rhythm, clarity, and vocabulary precision. |
| metadata | {"version":"0.1.0","author":"trails","category":"content"} |
Trails Writing Style
The v1 vocabulary families are live. Use derive for contract-owned fact production and render for surface presentation.
This skill covers how Trails prose should read: sentence rhythm, structural patterns, examples, and vocabulary discipline.
For the larger stance, load trails-writing-voice. For document placement and required sections, load trails-writing-docs.
Start From The Contract
Trails writing should follow the same shape as Trails itself:
- Define the authored truth.
- Derive facts the framework already knows.
- Render the right surface, doc, example, check, or report.
This is both architecture and writing style. Avoid asking readers to reconcile three versions of the same idea.
Sentence Rhythm
Use a mix of:
- Claim: one sentence that can stand alone.
- Reason: why the claim matters.
- Consequence: what breaks or gets easier.
- Example: code, command, or concrete output.
Short sentences carry decisions. Longer sentences are allowed when they earn their room by explaining a real tradeoff.
