Use when the user wants distinctive, production-grade frontend design, anti-generic AI aesthetics, UX critique, technical UI audits, or final polish through bundled Impeccable references and an optional upstream detector CLI.
Use when the user wants distinctive, production-grade frontend design, anti-generic AI aesthetics, UX critique, technical UI audits, or final polish through bundled Impeccable references and an optional upstream detector CLI.
Impeccable
Overview
Use this skill when the user wants stronger frontend design quality inside NextClaw.
This marketplace skill adapts the upstream pbakaus/impeccable project into a single installable NextClaw skill package with:
one top-level workflow router,
bundled local references for typography, color and contrast, layout, motion, interaction, responsive design, and UX writing,
bundled workflow guides for shaping, crafting, critique, audit, polish, and design-system extraction,
and an optional upstream impeccable detector CLI for deterministic anti-pattern scans.
Be explicit about the boundary:
This skill owns design-context gating, workflow selection, expectation-setting, and detector readiness guidance.
The bundled local references own the detailed design vocabulary.
The optional upstream impeccable CLI owns deterministic anti-pattern detection.
NextClaw, the current repository rules, and the active runtime own actual implementation and execution.
Do not present third-party detector output as built-in NextClaw capability.
Do not pretend the detector is ready when it is not.
What This Skill Covers
design context setup before UI work,
feature shaping before code is written,
distinctive frontend implementation guidance that avoids generic AI aesthetics,
focused passes on typography, color, layout, motion, interaction, responsive behavior, and microcopy,
design critique and technical UI audit,
final polish before shipping,
design-system extraction from repeated patterns,
optional detector-assisted anti-pattern scans when the upstream CLI is available.
What This Skill Does Not Cover
inferring the real audience or brand tone purely from code,
silently installing npm packages or downloading the detector runtime,
claiming detector-based evidence when Node/npm or the CLI are unavailable,
overriding a stricter local design system or project rulebook,
turning every design request into the same maximalist or marketing-style aesthetic,
pretending that an upstream multi-command ecosystem maps one-to-one onto NextClaw command surfaces.
Step 2: Gate on design context before real design work
Before doing meaningful design work, confirm these minimum inputs:
target audience,
primary use cases or jobs to be done,
brand personality or interface tone.
Do not infer these from code alone.
If the user already supplied them in the current conversation, proceed.
If not, ask the smallest number of targeted questions needed to unblock the work.
If the user wants this context persisted for future sessions, ask before writing a local .impeccable.md.
Step 3: Load only the matching local workflow
Prefer the smallest relevant asset instead of reading everything:
