ux-author SKILL.md skillA
ux-author from cahenesy/throughline is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add cahenesy/throughline/ux-author@git:20261007.ef85e7ePins git:20261007.ef85e7e in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- cahenesy/throughline
- Path
skills/ux-author/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261007.ef85e7e, committed Oct 7, 2026
- Size
- 16,686 bytes
- Repository stars
- 3
- License
- MIT
Mock the screens for UI-bearing requirements after a merged PRD update that adds or changes `[UI]` requirements, before /tdd-author. Writes the docs/ux/ record (self-contained HTML mocks, screenshots, index), delegates the visual design to whatever design skills the session has, runs an independent UX critique, and opens a UX PR. Never merges. Invoke with /ux-author. Run in its own session.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# UX authoring
Produce or update `docs/ux/`, the UX record of the merged PRD's `[UI]`
requirements. It sits between a merged PRD PR and `/tdd-author`.
throughline owns the **contract**: what gets mocked, the `docs/ux/` record,
traceability, the critique and the gate. **Making** the mocks is delegated
by **role** to the skills and tools this session has. When none fits a role,
you do that work yourself and say so (the honest degrade). The roles are
`design` (UI mocks), `design-system` (tokens), `critique` and
`accessibility`.
Every mechanical step is a `tl_ux_*` function from
`$(tl_plugin_root)/scripts/lib/ux.sh`. Never re-implement one in prose.
**Never edit `docs/PRD.md`.** A requirement gap is recorded in the mocks
and the PR, never "fixed" in the PRD.
## Block contract (every `<!-- tl:… -->` block)
The harness runs each shell call in a fresh shell. Run each marker-tagged
block as one shell command. Each block sources its own helpers (fail
closed) and reads its inputs only from env vars, as `${VAR:?…}`. Prefix it
with `export` lines that carry the real values, e.g.
`export TL_REPO='/abs/repo' TL_SCREENS='login settings'`.
…Read the whole file at its exact version.
How to install
mdr add cahenesy/throughline/ux-author@sha256:f5675b5b5d36cb88The line at the top of this page pins the label git:20261007.ef85e7e, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_m6722zlb3af3xq4q)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 7, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (16686 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
cahenesy/throughline · 3 stars · license MIT · pushed 2026-10-15 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_m6722zlb3af3xq4q GET https://markdownregistry.com/api/v1/resolve?ref=cahenesy/throughline/ux-author GET https://markdownregistry.com/api/v1/blob/f5675b5b5d36cb88dd2faef7c69e0b10086afd452af0e3f0c4142628f1164ab0
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.