# Design Review · jlcases

> How to review a change from product and design without reading the code — what to look at in a PR, which states are always forgotten, how to ask for a screenshot, and how to answer a UX notice. Use it when an interface notice arrives, when reviewing a PR from design, or when deciding whether something steps outside the design system.

## Facts
- Page: https://tashan.sh/capability/skill-jlcases-design-review
- tashan id: skill:jlcases/design-review
- Source: https://github.com/jlcases/agents-city
- Type: skill
- Category: design
- tashan score: 43.0 / 100
- Adoption: 17.0
- Upkeep: 63.0
- Freshness: 96.0
- Evidence coverage: 84% of the inputs this score can use
- Health: active
- Instruction depth: not yet graded
- License: Apache-2.0
- Official: no

## Install

```sh
cp -r design-review ~/.claude/skills/
```

## Security audit
Not scanned. We audit npm-published capabilities; this one has no npm package we can resolve, or has not reached the queue. This is not a clean bill of health.

---
Measured 2026-09-12 by tashan (https://tashan.sh) from public evidence. Scorer s5.
