astra-uilisted
Install: claude install-skill thientranhung/astragentic
# A UI pass
**Three intents, name one.** `audit` reports what is wrong and why; `polish` the smallest
changes that fix what the audit found; `upgrade` a direction the current design cannot reach by
polishing, put as a question with two or three options, the pick is the owner's. Unnamed = audit.
```
Skill(skill: "astra-ui", args: "audit <surface>") # a route, a component, a flow, or "the dashboard"
Skill(skill: "astra-ui", args: "polish <surface>")
Skill(skill: "astra-ui", args: "upgrade <surface>")
```
## What the pass reads first
**The design spine wins.** The project's design philosophy files (tokens, typography, spacing,
components, Do's and Don'ts) are the standard; their paths are the lines of
`.astraler/project/design-spine` (5.1.0; a project that has not declared it gets no UI brief, so
a pass without one is a pass the owner asked for by hand). A finding is a gap between the
surface and a section of a spine file, cited. No spine file: the first finding is that the
project has no written standard, and the pass judges against the UI system the code names
(shadcn, MUI, an internal kit) with that caveat on every finding. The anti-slop skill the
project lists in `.astraler/project/anti-slop-skills` was read by the Builder before the UI
code; its rules are house rules the pass may cite by name, the spine stays the standard.
**The ticket's Glance and States are the checklist.** Each Glance line: does the must-see win
in two seconds in that actor's seat, does the res