Source profileQuality 66/100
nexu-io/open-design/skills/impeccable-design-polish/SKILL.md
impeccable-design-polish
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.
- Source repository stars
- 82,073
- Declared platforms
- 0
- Static risk flags
- 0
- Last source update
- 2026-07-28
- Source checked
- 2026-07-28
Decision brief
What it does—and where it fits
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.
Not for
- Tasks that require unconfirmed production actions or broad system permissions.
- Environments where the pinned source and install steps cannot be inspected.
Compatibility matrix
Platform support, with evidence labels
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
Inspect first. Install second.
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
Source-detected install commandSource
npx skills add https://github.com/nexu-io/open-design --skill "skills/impeccable-design-polish"Safe inspection promptEditorial
Inspect the Agent Skill "impeccable-design-polish" from https://github.com/nexu-io/open-design/blob/89d6d4ef21baf80f871595abdf6f7de6e941dd44/skills/impeccable-design-polish/SKILL.md at commit 89d6d4ef21baf80f871595abdf6f7de6e941dd44. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
What the source asks the agent to do
- 01
Follow-Up Modes
Audit: identify the highest-impact issues in hierarchy, spacing, color, type, interaction states, responsiveness, and accessibility.
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. - 02
Operating Rules
1. Inspect the current HTML/page before editing. Do not guess from the prompt alone. 2. Keep the existing content, brand, and scenario unless the user explicitly asks to change them. 3. Prefer a few decisive fixes over broad cosmetic churn. 4. Remove common AI tells: - purple-bl…
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. - 03
Best Pairings
Pair with design-taste-frontend or gpt-taste for stronger anti-slop redesign work.
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.
Permission review
Static risk signals and limitations
No configured static risk pattern was detected
This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.
Evidence record
Why each signal appears
EvidenceSourceComputedTestedEditorial
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 66/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 82,073 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
Provenance and original SKILL.md
- Repository
- nexu-io/open-design
- Skill path
- skills/impeccable-design-polish/SKILL.md
- Commit
- 89d6d4ef21baf80f871595abdf6f7de6e941dd44
- License
- Apache-2.0
- Collected
- 2026-07-28
- Default branch
- main
View the original SKILL.md
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-frontendorgpt-tastefor stronger anti-slop redesign work. - Pair with
emilkowalski-motionor GSAP skills for motion-specific polish. - Pair with image/video skills when the artifact needs real visual assets rather than CSS-only decoration.
Alternatives
Compare before choosing
Computed 10042,015
coreyhaines31/marketingskills
ab-testing
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program
Computed 10042,015
coreyhaines31/marketingskills
churn-prevention
When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers o
Computed 1007
event4u-app/agent-config
design-intelligence
Grounded design brief from the adopted corpus — style, WCAG-checked color tokens, typography, layout pattern, anti-patterns. Use on ui-design-brief or any which-style/palette/font/chart decision.
Computed 1007
event4u-app/agent-config
design-system-capture
Write and maintain DESIGN.md + PRODUCT.md — captures visual decisions and interaction patterns so design tasks stay consistent across sessions without re-scanning past work.