impeccable-design-polish

nexu-io/open-design · skills/impeccable-design-polish/SKILL.md

Follow-up design polish skill inspired by Impeccable. Use after a web or HTML artifact exists to audit, critique, polish, animate, harden, and prepare the page for a live/share pass.

Design & CreativeNo license★ 91788⑂ 10564commit 9881cff

Install skillView source on GitHub

What this skill does

Impeccable Design Polish

Use this skill as the post-generation pass for an existing design. It should not restart the project from scratch; it should make the current artifact sharper, more usable, and closer to something a designer would ship.

Follow-Up Modes

Audit: identify the highest-impact issues in hierarchy, spacing, color, type, interaction states, responsiveness, and accessibility.
Critique: explain what feels generic, overdesigned, underdesigned, or inconsistent.
Polish: directly edit the artifact to improve the top issues while preserving the user's intent.
Animate: add restrained, useful motion only where it improves feedback or storytelling.
Harden: repair mobile overflow, text clipping, contrast problems, missing states, broken links, and fragile layout assumptions.
Live: prepare the artifact for presentation or sharing, including final visual QA and clear next actions.

Operating Rules

Inspect the current HTML/page before editing. Do not guess from the prompt alone.
Keep the existing content, brand, and scenario unless the user explicitly asks to change them.
Prefer a few decisive fixes over broad cosmetic churn.
Remove common AI tells:
- purple-blue glow gradients with no product reason
- generic 3-card feature rows
- oversized rounded cards everywhere
- empty marketing adjectives
- inconsistent spacing and type scale
- decorative effects that do not support comprehension
Preserve accessibility: focus states, contrast, semantic controls, readable text, and reduced-motion fallbacks.
Finish with the artifact in a better runnable state, not just a critique list.

Best Pairings

Pair with design-taste-frontend or gpt-taste for stronger anti-slop redesign work.
Pair with emilkowalski-motion or GSAP skills for motion-specific polish.
Pair with image/video skills when the artifact needs real visual assets rather than CSS-only decoration.

Installation

Copy a source-pinned command for your client. You run it yourself.

Destination: .claude/skills/impeccable-design-polish · pinned to the source commit

# Run from your project root
git clone https://github.com/nexu-io/open-design.git .skillboard-tmp
git -C .skillboard-tmp checkout 9881cff70e02be86c2a58130af512011ba23d4af
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/skills/impeccable-design-polish" ".claude/skills/"
rm -rf .skillboard-tmp

Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.

New here? Step-by-step setup – from installing the agent to using the skill

Operating systemAgentI already use Claude Code

1
Install Git
Install Git with your package manager (Debian/Ubuntu shown; use dnf/pacman on others). Official download.
```
sudo apt update && sudo apt install -y git
```
2
Install Claude Code
Requires Node.js 18+. Install the CLI globally: Official docs. (command-line tool)
```
npm install -g @anthropic-ai/claude-code
```

Get the skill, pinned to its exact version

Open a terminal and run these steps (they clone the source, check out the exact commit, and copy the skill into place):

# Run from your project root
git clone https://github.com/nexu-io/open-design.git .skillboard-tmp
git -C .skillboard-tmp checkout 9881cff70e02be86c2a58130af512011ba23d4af
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/skills/impeccable-design-polish" ".claude/skills/"
rm -rf .skillboard-tmp

Destination: .claude/skills/impeccable-design-polish

4
Use it in Claude Code
Open Claude Code in your project. It reads skills from the folder above, so impeccable-design-polish is now available. Always review the source before using it – static checks cannot prove runtime safety.

Security & Audits

Scanner static-checks@0.1.0 · commit 9881cff70e02. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.

No static rules matched. This is not a safety guarantee.

impeccable-design-polish

nexu-io/open-design · skills/impeccable-design-polish/SKILL.md

Follow-up design polish skill inspired by Impeccable. Use after a web or HTML artifact exists to audit, critique, polish, animate, harden, and prepare the page for a live/share pass.

Design & CreativeNo license★ 91788⑂ 10564commit 9881cff

What this skill does

Impeccable Design Polish

Follow-Up Modes

Audit: identify the highest-impact issues in hierarchy, spacing, color, type, interaction states, responsiveness, and accessibility.
Critique: explain what feels generic, overdesigned, underdesigned, or inconsistent.
Polish: directly edit the artifact to improve the top issues while preserving the user's intent.
Animate: add restrained, useful motion only where it improves feedback or storytelling.
Harden: repair mobile overflow, text clipping, contrast problems, missing states, broken links, and fragile layout assumptions.
Live: prepare the artifact for presentation or sharing, including final visual QA and clear next actions.

Operating Rules

Inspect the current HTML/page before editing. Do not guess from the prompt alone.
Keep the existing content, brand, and scenario unless the user explicitly asks to change them.
Prefer a few decisive fixes over broad cosmetic churn.
Remove common AI tells:
- purple-blue glow gradients with no product reason
- generic 3-card feature rows
- oversized rounded cards everywhere
- empty marketing adjectives
- inconsistent spacing and type scale
- decorative effects that do not support comprehension
Preserve accessibility: focus states, contrast, semantic controls, readable text, and reduced-motion fallbacks.
Finish with the artifact in a better runnable state, not just a critique list.

Best Pairings

Pair with design-taste-frontend or gpt-taste for stronger anti-slop redesign work.
Pair with emilkowalski-motion or GSAP skills for motion-specific polish.
Pair with image/video skills when the artifact needs real visual assets rather than CSS-only decoration.

Installation

Copy a source-pinned command for your client. You run it yourself.

Destination: .claude/skills/impeccable-design-polish · pinned to the source commit

# Run from your project root
git clone https://github.com/nexu-io/open-design.git .skillboard-tmp
git -C .skillboard-tmp checkout 9881cff70e02be86c2a58130af512011ba23d4af
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/skills/impeccable-design-polish" ".claude/skills/"
rm -rf .skillboard-tmp

Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.

New here? Step-by-step setup – from installing the agent to using the skill

Operating systemAgentI already use Claude Code

1
Install Git
Install Git with your package manager (Debian/Ubuntu shown; use dnf/pacman on others). Official download.
```
sudo apt update && sudo apt install -y git
```
2
Install Claude Code
Requires Node.js 18+. Install the CLI globally: Official docs. (command-line tool)
```
npm install -g @anthropic-ai/claude-code
```

Get the skill, pinned to its exact version

Open a terminal and run these steps (they clone the source, check out the exact commit, and copy the skill into place):

# Run from your project root
git clone https://github.com/nexu-io/open-design.git .skillboard-tmp
git -C .skillboard-tmp checkout 9881cff70e02be86c2a58130af512011ba23d4af
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/skills/impeccable-design-polish" ".claude/skills/"
rm -rf .skillboard-tmp

Destination: .claude/skills/impeccable-design-polish

4
Use it in Claude Code
Open Claude Code in your project. It reads skills from the folder above, so impeccable-design-polish is now available. Always review the source before using it – static checks cannot prove runtime safety.

Security & Audits

Scanner static-checks@0.1.0 · commit 9881cff70e02. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.

No static rules matched. This is not a safety guarantee.

impeccable-design-polish

What this skill does

Impeccable Design Polish

Follow-Up Modes

Operating Rules

Best Pairings

Installation

Install Git

Install Claude Code

Get the skill, pinned to its exact version

Use it in Claude Code

Security & Audits

impeccable-design-polish

What this skill does

Impeccable Design Polish

Follow-Up Modes

Operating Rules

Best Pairings

Installation

Install Git

Install Claude Code

Get the skill, pinned to its exact version

Use it in Claude Code

Security & Audits