メニュー
Trails writing voice and values. Use when drafting or reviewing Trails docs, ADRs, README content, release notes, agent guidance, or public explanations for stance, audience, and tone.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/outfitter-dev/trails --skill trails-writing-voiceコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Run a Trails Regrade migration loop with dry-run discovery, occurrence judgment, safe apply, verification, ledger capture, and per-cycle resume.
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.
Run a Trails Regrade migration loop with dry-run discovery, occurrence judgment, safe apply, verification, ledger capture, and per-cycle resume.
SKILL.md を表示中
SOC 職業分類に基づく
| name | trails-writing-voice |
| description | Trails writing voice and values. Use when drafting or reviewing Trails docs, ADRs, README content, release notes, agent guidance, or public explanations for stance, audience, and tone. |
| metadata | {"version":"0.1.0","author":"trails","category":"content","skillset":{"generator":"scripts/codex/skillset.ts","target":"codex","version":1,"source":".claude/skills/trails-writing-voice","source-file":".claude/skills/trails-writing-voice/SKILL.md"}} |
The v1 vocabulary families are live. Use derive for contract-owned fact production and render for surface presentation.
Trails writes like a framework with a spine.
We are opinionated because drift is expensive. We explain those opinions because agents and developers need to trust the path, not memorize it. The voice should feel calm, direct, practical, and awake to tradeoffs.
| Principle | In practice |
|---|---|
| Contract-first | Lead from authored contracts and what they make possible. |
| Agent-native | Structure for agents and humans at the same time. |
| Drift-resistant | Explain how the framework makes consistency easier than divergence. |
| Evidence-backed | Anchor claims in code, checks, examples, ADRs, or measured behavior. |
| Plain by default | Use ordinary words when they carry the concept. Use Trails terms only when they earn the slot. |
| Teachable | A good paragraph should make the next correct action easier. |
| Distribution-aware | Feature work is not done until docs, examples, guidance, governance, and release posture are handled or explicitly not applicable. |
Write for three readers at once:
This does not mean writing more. It means writing with structure:
Trails voice is:
Prefer:
Define the trail once. Derive what the framework already knows. Render each surface from that shared contract.
Avoid:
Trails aims to provide a flexible and potentially powerful way to create multiple integrations.
| Container | Tone |
|---|---|
| README quick start | Fast, concrete, copy-pasteable. |
| Guide | Practical and explanatory. Show patterns and failure modes. |
| Reference | Dense and exact. Personality gets out of the way. |
| ADR | Declarative and reasoned. Tell the tension, then the decision. |
| Release note | Operator-focused. What changed, why it matters, what to do. |
| Agent guidance | Direct. Give rules, stop conditions, and verification. |
| Blog or narrative | More room for voice, but claims still need evidence. |
Trails can use outdoor and wayfinding language when it clarifies the mental model. Theme is not a writing quota.
Use themed terms when they are official vocabulary or carry the concept better than a plain word: trail, topo, surface, warden, wayfinder, and detour.
Do not decorate ordinary prose with theme language when a plain word is clearer.
The test:
Does the word reduce translation effort for a new agent or developer?
If yes, keep it. If no, say it plainly.
Trails docs can be strongly worded when the claim is backed by proof.
Good sources of proof:
Weak sources:
Use "we" when speaking as the project. Use direct imperatives when giving instructions.
Prefer:
Add a changeset on the branch that changes the publishable package.
Avoid:
It is recommended that a changeset should be considered.
When reviewing a Trails document for voice:
