CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

60

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/impeccable-design-polish/SKILL.md
SKILL.md
Quality
Evals
Security

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

  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-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
  5. Preserve accessibility: focus states, contrast, semantic controls, readable text, and reduced-motion fallbacks.
  6. 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.
Repository
nexu-io/open-design
Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.