auditing-uilisted

Runs a lens-based UI/UX audit of the client and turns its findings into tracked, fenced work items. Use when auditing the interface for quality gaps, running or scoping an audit (full, one lens, one surface, or a diff), driving the real-browser leg of an audit, synthesizing raw lens findings into batches, or deciding how audit findings enter the tracker.
dork-labs/dorkos · ★ 9 · Web & Frontend · score 76

Install: claude install-skill dork-labs/dorkos

# Auditing UI An audit reads the interface through several independent lenses at once, then merges what they saw into one ranked report and a set of PR-sized batches. It writes **zero code**. The rules live in the charter, not here: `audits/ui.md` (domain) inherits `audits/README.md` (cross-domain). **The charter is the authority on the lens set, the lens keys, and which lens is surface-local versus whole-tree.** This file is the **procedure**, and it is the single home for the procedure: the commands under `/ui-audit:*` point here rather than restating any of it. Read the charter before every run. If `audits/ui.md` is missing, run `/ui-audit:init` first. ## 1. Durable state Three things outlive any single run and live at the domain root, `audits/runs/ui/`: | Path | What | Written by | | ------------- | -------------------------------------------------------------------- | ----------------- | | `profile.md` | how work lands in **this** repo | `/ui-audit:init` | | `stamps.json` | per-lens last-audited commit + rotation cursor | `run` and `pulse` | | `<date>/` | one run's `report.md`, `raw/<key>.md`, and its ledger when untracked | `run` and `pulse` | `<date>` is ISO `YYYY-MM-DD`. ### The repo profile is consulted, not decorative Read `audits/runs/ui/profile.md` at the start of every `run`, `pulse`, and `execute`. It answers q