gagandeepgill/puzzle-game / .claude/skills/improve-ui
improve-ui
VerifiedAudit an existing product surface against its own design evidence, identify verified UI problems, and write self-contained implementation plans for another agent. Strictly read-only on product source. Use when asked to review, refine, improve, or clean up an interface without replacing its identity; investigate design-system drift; or prepare a design handoff.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.7 KB |
| agents/openai.yaml | config | 394 B |
| references/plan-template.md | markdown | 1.6 KB |
references/plan-template.md
View on GitHub# Design plan template
```markdown
# <Outcome>
Written against: <commit or unavailable>
## Evidence chain
- Surface: `<path, route, or rendered state>`
- Problem: <direct observation>
- Design evidence: `<documentation, style, token, component, pattern, or rendered surface>`
- Owner: `<path or surface>`
- Scope and affected surfaces: `<paths or surfaces>`
- Uncertainty: <none, or what requires validation>
## Design decision
<State the appropriately scoped change and why it resolves the root problem.>
## Reuse
- `<token, variable, component, variant, or composition>`
- Exemplar: `<path>`
If a new primitive is required, state why the existing system cannot express the decision, where the primitive belongs, and which consumers should share it.
## Changes
1. `<exact path or surface>`
- Change: <implementation-ready behavior or structure>
- Preserve: <valid behavior or identity>
- Verify: <observable result>
## Scope
- Inherit: <consumers that receive the change>
- Verify: <consumers that may be affected>
- Exclude: <valid exceptions and unrelated work>
## Validation
- Product: <task and expected outcome>
- Interface: <relevant routes, states, content extremes, interactions, and viewports>
- System: <confirm appropriate reuse and absence of an unintended parallel pattern>
- Repository: `<exact check command>` → <expected result>
## Stop conditions
- Stop if <a key assumption fails, ownership changes, or scope must widen>.
## Design documentation
- After acceptance and validation: <exact decision to record and its destination, or none>
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |