From impeccable
Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability.
How this skill is triggered — by the user, by Claude, or both
Slash command
/impeccable:bolderThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Increase visual impact and personality in designs that are too safe, generic, or visually underwhelming, creating more engaging and memorable experiences.
Increase visual impact and personality in designs that are too safe, generic, or visually underwhelming, creating more engaging and memorable experiences.
Use the frontend-design skill — it contains design principles, anti-patterns, and the Context Gathering Protocol. Follow the protocol before proceeding — if no design context exists yet, you MUST run teach-impeccable first.
Analyze what makes the design feel too safe or boring:
Identify weakness sources:
Understand the context:
If any of these are unclear from the codebase, STOP and call the AskUserQuestion tool to clarify.
CRITICAL: "Bolder" doesn't mean chaotic or garish. It means distinctive, memorable, and confident. Think intentional drama, not random chaos.
WARNING - AI SLOP TRAP: When making things "bolder," AI defaults to the same tired tricks: cyan/purple gradients, glassmorphism, neon accents on dark backgrounds, gradient text on metrics. These are the OPPOSITE of bold—they're generic. Review ALL the DON'T guidelines in the frontend-design skill before proceeding. Bold means distinctive, not "more effects."
Create a strategy to increase impact while maintaining coherence:
IMPORTANT: Bold design must still be usable. Impact without function is just decoration.
Systematically increase impact across these dimensions:
NEVER:
Ensure amplification maintains usability and coherence:
The test: If you showed this to someone and said "AI made this bolder," would they believe you immediately? If yes, you've failed. Bold means distinctive, not "more AI effects."
Bold is not "more effects." Bold is one committed decision pushed further than the safe version dared. These pairs show the difference.
The "safe" version is indistinguishable from a thousand landing pages. The bold version makes a size decision and commits to it.
/* before — timid, no opinion, reads as a template */
.hero-title {
font-size: 2rem;
font-weight: 600;
line-height: 1.3;
letter-spacing: normal;
font-family: system-ui, sans-serif;
}
/* after — display scale, tight tracking, opinionated weight */
.hero-title {
font-size: clamp(3rem, 8vw, 6rem);
font-weight: 800;
line-height: 0.95;
letter-spacing: -0.04em;
font-family: "Fraunces", "Söhne Breit", serif;
text-wrap: balance;
}
A slate palette is safe because it refuses to take a position. Pick a hue and let it own the composition.
/* before — generic tech gray, indistinguishable from the next dashboard */
:root {
--bg: #f8fafc;
--surface: #ffffff;
--fg: #0f172a;
--accent: #64748b; /* slate, no personality */
}
/* after — committed hue, dominant across the UI */
:root {
--bg: oklch(97% 0.03 25); /* warm blush background */
--surface: oklch(99% 0.01 25);
--fg: oklch(22% 0.05 25);
--accent: oklch(65% 0.24 25); /* saturated terracotta owns 60% of the design */
--accent-ink: oklch(35% 0.18 25);
}
body {
background: var(--bg);
color: var(--fg);
}
Centered everything is the default. Break the grid on purpose and the page remembers you.
{/* before — safe, centered, perfectly balanced, forgettable */}
<section className="max-w-4xl mx-auto px-6 py-24 text-center">
<h1 className="text-5xl font-bold mb-6">Build faster</h1>
<p className="text-xl text-gray-600 mb-8 max-w-2xl mx-auto">
The platform for teams that ship.
</p>
<button className="px-6 py-3 bg-violet-600 text-white rounded-lg">
Get started
</button>
</section>
{/* after — asymmetric, overlapping, tilted, room to breathe */}
<section className="relative min-h-screen overflow-hidden">
<h1
className="absolute left-[4vw] top-[18vh] text-[clamp(5rem,14vw,14rem)] font-black leading-[0.85] tracking-[-0.05em]"
style={{ transform: "rotate(-2deg)" }}
>
Build
<br />
<span className="italic text-[--accent]">faster.</span>
</h1>
<p className="absolute right-[6vw] top-[55vh] max-w-xs text-lg leading-snug border-l-4 border-[--accent] pl-4">
The platform for teams that ship.
</p>
<a
href="/start"
className="absolute bottom-[12vh] right-[8vw] text-2xl font-bold underline decoration-4 underline-offset-8 decoration-[--accent]"
>
Start building →
</a>
<div
aria-hidden
className="absolute -left-20 bottom-0 w-[40vw] h-[40vw] rounded-full bg-[--accent] opacity-20 blur-3xl"
/>
</section>
BOLD: SLOP:
- One committed hue dominates 60%+ - Random cyan/purple gradient
- Display-scale type (clamp to 6rem+) - Four decorative effects stacked
- Tight tracking, heavy weight - Glassmorphism on every card
- Broken grid with intent (rotation, - Bounce easing on every animation
overlap, asymmetry) - Gradient text on every heading
- Generous negative space around - "More" as a substitute for
the one hero moment "stronger"
Test: remove every effect except the single strongest decision. If the design still feels bold, you chose right. If it collapses, you were stacking effects to hide a lack of commitment.
Remember: Bold design is confident design. It takes risks, makes statements, and creates memorable experiences. But bold without strategy is just loud. Be intentional, be dramatic, be unforgettable.
npx claudepluginhub firdausmntp/techneuma --plugin impeccableGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.