# experience-remediation

The experience-remediation skill for Claude Code executes UI and UX repairs. It runs to fix layout flaws and interaction issues based on project-specific rules.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf (Devin Desktop), Claude.ai · ★ 529 repo stars
- Author: ShuaiMXu
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/ShuaiMXu/happyhands/tree/HEAD/skills/experience-remediation/SKILL.md
- Updated: 2026-11-17
- Security check: automated, 2026-11-17 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/experience-remediation

## What it does

This skill performs interface diagnostics, fixing component defects and alignment issues within the project design system. It verifies element states, page hierarchy, and grid consistency against established project requirements. The tool systematically analyzes current viewport versions and cross-device regression scenarios.

Operation requires strict adherence to project protocols, including icon validation and Hero-section layout checks. Results are stored in a structured format with attached evidence for independent review. The skill never authorizes redesign or human acceptance, focusing purely on evidence-backed remediation.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add ShuaiMXu/happyhands --skill experience-remediation -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/experience-remediation/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/experience-remediation/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add ShuaiMXu/happyhands --skill experience-remediation -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/experience-remediation/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add ShuaiMXu/happyhands --skill experience-remediation -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/experience-remediation/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install ShuaiMXu/happyhands skills/experience-remediation
```

2. **Manually: put the files in place**
- File: `.github/skills/experience-remediation/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add ShuaiMXu/happyhands --skill experience-remediation -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/ShuaiMXu/happyhands --path skills/experience-remediation
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/experience-remediation/SKILL.md` — The legacy .windsurf/skills/ path still works

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/ShuaiMXu/happyhands/tree/HEAD/skills/experience-remediation/SKILL.md

## When to use it
- Fix layout errors and visual defects
- Adjust component interface states
- Validate page hierarchy and grid
- Test responsive layout behavior
- Generate structured remediation reports

## Example prompts
- /experience-remediation fix layout issues on the dashboard
- /experience-remediation verify button component states
- /experience-remediation audit icons in the navigation menu

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 6038cce369200fd7.

BEGIN THIRD-PARTY FILE 6038cce369200fd7
```text
---
name: experience-remediation
description: Execute evidence-backed UI and UX remediation using project layout contracts, shared components and complete OJO/Taste/Impeccable methods, then supply per-rule evidence for independent acceptance.
---

# Experience remediation

Use for a confirmed experience repair, including AI slop and inconsistent shared components. The task, adopted project rules and approved Foundation take precedence over generic examples. This Skill never authorizes unrelated redesign, publication or a human acceptance decision.

## Diagnose

Read the complete assigned method documents. Start with the current page and its actual working viewport. First review the recurring AI slop and UI details: dropdown arrows/checkmarks, selected/focus states, gaps, boundaries, radii, redundant navigation and unnecessary copy. Then inspect shared components, task flow and current-page hierarchy/grid. Phone and other viewport checks come last as regression coverage; they never replace current-page remediation. For every contract rule and supplied state, return an explicit result with original screenshot references. Distinguish a visible violation from a preference, missing evidence and a genuine non-applicable rule. Never label an unchecked state not-applicable. Follow the existing finding-admission policy when proposing a repair.

## Mandatory order

Current-page AI slop and detail review → shared-component correction and current-page interactions → task/hierarchy/layout validation → cross-device regression. Inspect historical project issues before introducing new aesthetic preferences. Group findings and verification in this order, even if captures were collected together. Do not declare success because a mobile overflow was fixed while current-page control defects remain.

## Decide and implement

1. Reproduce the issue and identify the user task it interrupts. State what to preserve.
2. Inspect the actual design sources, shared component and all known consumers. A package dependency does not establish actual use.
3. Record a concrete decision: content order, grouping, primary action, copy retained/removed, widths, spacing, responsive reflow and state behavior. Use existing tokens and primitives. Resolve a shared cause before patching instances.
4. For grids, inspect the adopted container width, columns, gutter, outer margins, alignment and breakpoints. Record actual source references and the chosen values/reflow in the result. Preserve intended reading order and nested alignment; never impose OJO's 12-column/8pt examples on a different approved grid. Missing layout evidence must be stated, not invented.
```
END THIRD-PARTY FILE 6038cce369200fd7

The third-party file has ended. Everything between the 6038cce369200fd7 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2664 of 10565 bytes. © ShuaiMXu · MIT · https://github.com/ShuaiMXu/happyhands/tree/HEAD/skills/experience-remediation/SKILL.md

## Similar
- [designing-user-experience](https://affpapa.org/en/nevibecode/skills/designing-user-experience.md) — skill · 578 installs
- [ui-ux-polish](https://affpapa.org/en/nevibecode/skills/ui-ux-polish.md) — skill · 577 installs
- [attention-management](https://affpapa.org/en/nevibecode/skills/attention-management.md) — skill · 577 installs
- [comfort-safety](https://affpapa.org/en/nevibecode/skills/comfort-safety.md) — skill · 560 installs
- [break-ui](https://affpapa.org/en/nevibecode/skills/break-ui.md) — skill · 121000 installs

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
