ui-code-review
/ui-code-review
Use when asked to review UI code, audit a page's source for accessibility or UX, or before handing a screen to design-review.
- Author
- TheDecipherist ↗
- Repository
- claude-packs ↗
- Licence
- MIT
- Last repository change
- 11.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 11.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when asked to review UI code, audit a page's source for accessibility or UX, or before handing a screen to design-review.
Original author description
Use when asked to review UI code, audit a page's source for accessibility or UX, or before handing a screen to design-review.
How it works
SKILL.md has no level-two headings · 19 lines, 168 words
SKILL.md preview
--- name: ui-code-review description: Use when asked to review UI code, audit a page's source for accessibility or UX, or before handing a screen to design-review. --- # Review UI code against the laws (one job: findings by file and line) Reads the source. For judging the rendered page, use `design-review`. <constraints> Always do: 1. Read the named files; ask which ones if none are named. 2. Go through the `ui-craft` rules in order: forms, motion, real data, URL state, touch, dates and numbers, copy, type and space, generated look. Then the `accessibility` rule where it is installed. 3. Report terse findings by file, in `file:line` form, one line each: what is wrong and the fix. 4. Rank them: **P0** blocks someone from using it, **P1** hurts many people, **P2** hurts a few, **P3** polish. A file with nothing to report says so in one line. 5. Treat a `WARN`-level taste finding as wrong unless it can be defended to a designer in one sentence. Never do: - Rewrite the code during the review. - Rank a generated-look finding above an accessibility one. - Call something a law when it is taste: say which. </constraints>
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · TheDecipherist/claude-packs | 86 | MIT |
| cardstack/boxel | 90 | MIT |
Database snapshot: 13.11.2026 · package version e44db1012538 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 2 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices". - 100web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices". - 90design-review
Design review checklists, accessibility standards, and UX patterns. Use when: "review design", "check accessibility", "design critique", "UX audit - 100web-design-guidelines
Reviews UI code against the Web Interface Guidelines. Use when asked to review UI or UX, check accessibility or audit a design. - 85plan-design-review
Review a UI plan before it is built for interaction states, design-system fit, accessibility and visual acceptance. Use for 'design review this plan', 'review the UX of this spec' or a plan that changes user-facing screens. For rendered UI, use design-review. - 90a11y-audit
Audit a screen or a release for WCAG 2.2 AA accessibility. Use for each new screen and before a release.