outfitter-dev/trails-dev
Build Trails itself with contributor workflows for architecture, governance, documentation, and review.
The working-on-Trails doctrine digest — what governs the framework, the decision tools for framework work, and where truth lives. Use at the start of any session that changes Trails itself (framework code, docs, vocabulary, governance), when orienting a new agent or persona, or when deciding which governing source answers a question. Not for building apps with Trails; the trails skill covers consuming the framework.
Run a Trails Regrade migration loop with dry-run discovery, occurrence judgment, safe apply, verification, ledger capture, and per-cycle resume.
Trails framework design tenets — the foundational beliefs, promises, primitives, and patterns that govern the framework. Use when evaluating architectural decisions, reviewing feature proposals, checking alignment with framework principles, or when tenets, principles, or design philosophy are mentioned.
Author, update, and manage Trails ADRs. Use when creating new ADRs, promoting drafts to accepted, updating the ADR index, renaming or renumbering ADRs, or when the user mentions ADR, architecture decision, or decision record.
Use when a Trails change derives framework facts, derived views, rule data, or surface metadata. Helps agents find authoritative owner exports and avoid shadow registries, duplicated maps, and canonical-source indirection.
Compatibility entry for older public-union review prompts. Use Trails Warden's public-output discriminant rule and the building-trails owner-first workflow.
Use when reviewing Trails-owned framework code for Result-shaped failures, resource and cwd boundaries, app loading, and documented host construction exceptions.
Draft or review Trails docs, ADRs, README content, release notes, examples, agent guidance, and prose-heavy changes with one contributor editorial workflow. Use for writing, restructuring, or editorial readiness checks.
Compatibility entry for the retired Trails language-styleguide name. Route all Trails drafting and editorial review through trails-editorial.
Compatibility entry for older primitive-parity prompts. Use building-trails to classify deliberate scope, user-facing gaps, and unsupported symmetry pressure.
Compatibility entry for older Warden-classification prompts. Use building-trails and the canonical Warden contributor guide to place enforceable and advisory findings.
Compatibility entry for older Trails documentation prompts. Route document placement, structure, maintenance, drafting, and review through the singular trails-editorial workflow.
Compatibility entry for older Trails prose prompts. Route prose craft, examples, and vocabulary work through the singular trails-editorial workflow.
Compatibility entry for older Trails writing prompts. Route drafting or review of voice, audience, tone, and stance through the singular trails-editorial workflow.