# Audit UI and Prepare Evidence-Based Design Plans

Interface reviews can mistake intentional differences for defects and recommend changes without evidence. This skill verifies design findings and prepares selected implementation plans while preserving product identity.

## Install

```bash
npx skillstore add ibelick/improve-ui
```

## Metadata

- Status: approved
- Slug: ibelick-improve-ui
- Skillstore revision: r1
- Version status: missing
- Tree hash: f5788d23dab7ec7c48b71c407a4c6bea3fbc14bce9dec7512f895e638d01c027
- Author: ibelick
- GitHub username: ibelick
- Repository: https://github.com/ibelick/ui-skills/tree/f511eae41c996e3953fbeabf95d38e4077d40711/skills/improve-ui
- Ref: ef0f8e34cfd360d6e95cf0c8e63f7d2be3df24c1
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 70
- Public page: https://skillstore.pages.dev/skills/ibelick-improve-ui
- Manifest: https://skillstore.pages.dev/api/skills/ibelick-improve-ui/manifest

## Capabilities

- Trace one product surface through routes, layouts, shared components, variants, tokens, and styles.
- Identify current design documentation and prove which sources govern the selected surface.
- Require a design contract, runtime connection, and one evidence-supported correction for every reported finding.
- Recheck cited sources, remove contradicted findings, and report at most three supported issues.
- Write self-contained plans for user-selected changes, covering reuse, affected consumers, validation, and stop conditions.
- Reconcile existing plans against current source, documented decisions, affected surfaces, and status.

## Use Cases

- Review a Product Surface: Check a settings interface against its governing components and design decisions before proposing targeted visual changes.
- Investigate Design-System Drift: Trace a dashboard through shared owners and resolved tokens to distinguish real inconsistencies from deliberate variants.
- Prepare an Implementation Handoff: Turn an approved design finding into a self-contained plan with exact scope, reusable elements, validation, and stop conditions.

## Prompt Templates

### Review One Interface

```
Use improve-ui to audit the account settings surface. Report supported UI findings and recommend one priority. Do not write plans or change product source.
```

### Trace a Design Inconsistency

```
Audit dashboard filter styling against current design guidance. Trace the governing variants and resolved tokens. Distinguish intentional exceptions from supported violations.
```

### Plan an Approved Correction

```
Prepare a plan for the approved settings-label inconsistency. Recheck evidence, name exact reusable elements, and specify validation. Write only under design-plans/.
```

### Reconcile Existing Plans

```
Reconcile existing design-plans/ files for the checkout surface against current source and accepted design decisions. Update stale evidence, scope, and status without implementing changes.
```

## Limitations

- Does not implement fixes or modify product source; file edits are limited to design-plans/.
- Does not install dependencies, run formatters, commit, or push changes.
- Uses rendered evidence only when supplied or visual inspection is explicitly requested; perceptual judgments require rendered or user evidence.
- Reports at most three findings and excludes accessibility, functional, and broader code-quality issues unless explicitly requested or otherwise in scope.

## Best Practices

- Specify one coherent surface and provide relevant design decisions or rendered evidence.
- Select supported findings before requesting plans, and keep implementation separate from the audit.
- Reconcile existing plans after source changes so implementation agents receive current evidence and scope.

## Anti Patterns

- Requesting repository-wide visual normalization without proving shared runtime ownership or a binding design rule.
- Treating repeated code, missing documentation, or personal preferences as sufficient evidence of a design defect.
- Expecting direct fixes, dependency installation, or product-source edits from this planning-only skill.

## Security Audit

- Audited at: 2026-11-11T15:47:35.449\+00:00
- Summary: All 20 static findings are false positives from Markdown formatting and ordinary design-review language, not executable commands or system reconnaissance. No evidence found of prompt injection, credential collection, or data exfiltration in the reviewed files. The skill restricts product-source changes and permits plan files only under design-plans/.

## Stats

- Views: 0
- Downloads: 4
- Favorites: 0
- Popularity score: 0
