UX/UI guidelines citations wired into all audit and review skills

Status: Delivered
CAS: CAS-2784
Delivered: 2026-05-14
PRs: #742

What’s new

The four agent skills that produce UX findings — astrid-ux-advisor, casaconomy-ux-review, casaconomy-task-worktree, and casaconomy-review-protocol — now all reference docs/ux/ux-ui-guidelines-v0.md and instruct the agent to cite UX-* rule IDs in every finding. Before this change, the guidelines doc existed but only Eivind’s skill knew about it; Astrid and the UX Specialist would produce findings without a traceable standard. Now every audit surface is grounded in the same citable authority.

How to use it

Nothing changes for engineers in practice — the skills are updated behind the scenes. What you will see:

Astrid’s advisory comments on UI PRs now include UX-* citations in her findings (e.g., “UX-LAYOUT-01 — bottom anchor gap of 34 px detected”).
Eivind’s UX walk verdicts carry rule IDs (already wired in CAS-2737; this extends the pattern to Astrid).
Acceptance criteria review in casaconomy-review-protocol now has a fourth gate: for UI PRs, AC items must cite the applicable UX-* rule, and the reviewer must verify each cited rule is satisfied by the diff.
Task-worktree CAS body template for UI-touching issues now has a UI-specific AC paragraph instructing the engineer to cite UX-* IDs.

What changed under the hood

astrid-ux-advisor skill — step 4 updated to instruct Astrid to cite UX-* IDs per finding; new step 9 instructs her to read the guidelines doc before composing. New “UX/UI guidelines” section added to the skill.
casaconomy-ux-review skill — new “UX/UI guidelines” section; UX Specialist is instructed to cite rule IDs in findings and propose new rules for ungoverned gaps (UX-UNGOVERNED).
casaconomy-task-worktree skill — DoD item 10 (AC) gains a UI-specific paragraph requiring UX-* citation for UI-touching PRs.
casaconomy-review-protocol skill — AC validation prerequisite expanded from three checks to four; check 4 requires UX-* citation in UI PR AC items.
AGENTS.md — docs/ux bullet now lists all four skills carrying the citation expectation.

Why we built it

CAS-2772 wrote the guidelines and wired them into Eivind. But Astrid (advisory UX analysis via AI), the UX Specialist (human-directed deep review), and the review protocol all operated without referencing the standard. A finding without a rule ID is subjective and hard to act on. By wiring citations into every audit surface, every finding becomes traceable: the engineer knows exactly what rule to satisfy, the reviewer knows what to verify, and the guidelines doc gets exercised and improved as real cases surface.

Known limitations / follow-on work

Citations are enforced by skill instructions, not by tooling. A finding without a UX-* ID won’t fail CI.
Astrid’s citation quality depends on the completeness of the guidelines doc. The 7 stub sections in v0 will produce UX-UNGOVERNED findings until filled in.