Modo
Agendar llamada

impeccable: pulir, criticar y auditar el diseño de tu web

Le da a tu agente un vocabulario de comandos para criticar, auditar y pulir una web que ya existe, y un detector que marca los rasgos de diseño hecho con IA.

impeccable: pulir, criticar y auditar el diseño de tu web

Respuesta rápida

Qué es
impeccable es una skill de Paul Bakaus (licencia Apache 2.0) que le da a Claude 24 comandos para criticar, auditar, pulir y rediseñar interfaces, más un detector de 62 reglas que encuentra la estética típica de la IA.
Qué le das
Tu proyecto web (el código o la URL) y la parte concreta que quieres mejorar
Qué te devuelve
Una crítica puntuada o una auditoría con prioridades, y los cambios aplicados en el código
Licencia
Apache 2.0
En GitHub
110,8 mil estrellas · actualizada el
Revisada por Claura

Instálala en una línea para todos tus proyectos, en Claude Code, Cursor, Codex y más:

npx skills add pbakaus/impeccable --skill impeccable -g

Funciona en

Claude CodeEn ~/.claude/skills/
CursorEn ~/.agents/skills/
CodexEn ~/.agents/skills/
Gemini CLIEn ~/.agents/skills/

Pedidos para probarla

Con la skill instalada, copia uno y pégaselo a tu agente tal cual, o cambia los datos por los tuyos.

  • Audita el diseño de mi web en http://localhost:3000 y dame los problemas ordenados por gravedad, con el archivo de cada uno.

  • Pule la página de precios: jerarquía, espaciado y contraste, sin cambiar los textos.

  • Critica la landing de mi inmobiliaria como lo haría un director de arte y dime las tres cosas que la hacen parecer hecha con IA.

#Qué hace

impeccable es una skill de Paul Bakaus que le da a Claude permiso y herramientas para hacer diseño con oficio: código de producción, un punto de vista claro y verificación mirando el resultado en los tamaños en que se publica. Al empezar cada sesión corre un comando propio (impeccable context) que carga el PRODUCT.md del proyecto, el DESIGN.md con la identidad visual y las pautas de la superficie que se trabaja. Antes de tocar cualquier pantalla lee un archivo de piso de calidad (reference/craft-floor.md) con las prohibiciones absolutas y los reflejos que ningún detector atrapa.

Clasifica cada página en uno de cuatro modos según qué significa el éxito para quien la visita: persuadir (landings, precios, campañas: el visitante decide y actúa), operar (paneles y herramientas), leer (guías, documentación) y experiencia (portafolios y galerías). En persuadir pide trabajo audaz y con identidad; en operar y leer, precisión y contención. Dos reglas de fondo: si el brief fija una estética, se respeta aunque choque con sus advertencias, y refinar conserva la identidad actual mientras que rediseñar la reemplaza, sin quedarse a mitad de camino.

El corazón es la tabla de 24 comandos, cada uno con su manual en la carpeta reference/ (46 archivos): shape planifica antes del código, init y document escriben el contexto, critique hace una revisión con puntaje heurístico, audit revisa accesibilidad, rendimiento y adaptación a pantallas, y polish, bolder, quieter, distill, typeset, layout, colorize, animate, clarify, harden, adapt y optimize hacen cada uno un solo movimiento. live y generate muestran variantes en el navegador para elegir. Fuera de la skill, npx impeccable detect revisa una carpeta o una URL con 62 reglas fijas.

#Cómo aplicarla a tu negocio

Caso de ejemplo: una inmobiliaria de Córdoba tiene su web hecha con IA hace seis meses. Funciona, pero se ve igual que la de la competencia: fondo crema, tarjetas redondeadas para cada propiedad y un botón violeta.

  1. Mide antes de tocar. Corres npx impeccable detect https://tu-inmobiliaria.com y sale la lista de hallazgos (por ejemplo, 14 marcas: fuente genérica, texto gris de bajo contraste sobre las fotos, saltos en los títulos). Es la foto del punto de partida.
  2. Dale contexto una vez. /impeccable init te pregunta para quién es la web (familias que buscan alquiler y propietarios que quieren vender) y qué tiene que lograr (que dejen sus datos para una tasación). Queda en PRODUCT.md.
  3. Critica una sola sección. /impeccable critique la ficha de propiedad te devuelve qué falla y en qué orden arreglarlo. Pide los cambios de a uno: /impeccable typeset, /impeccable layout.
  4. Cierra con auditoría y pulido. /impeccable audit revisa accesibilidad y velocidad en el móvil y ordena los problemas de P0 a P3; /impeccable polish hace la pasada final. Vuelves a correr el detector y comparas contra la primera foto.

Si el problema de fondo son los textos y no el diseño, empieza por improved-copywriting. Y si la página todavía no existe, arma la primera versión con frontend-design y trae a impeccable para iterar.

#Cómo instalarla

El autor recomienda su propio instalador, que detecta tus agentes y ofrece activar el aviso automático del detector.

  • Instalador del autor (recomendado): desde la raíz de tu proyecto, npx impeccable install. Te pregunta si instalar para el proyecto o para todos, y ofrece el aviso que corre el detector después de cada edición: acéptalo. Recarga tu agente y corre /impeccable init (en Codex, $impeccable init). Para actualizar: npx impeccable update.
  • Claude Code, como plugin: /plugin marketplace add pbakaus/impeccable y después instala Impeccable desde /plugin.
  • Con una línea, para cualquier agente: npx skills add pbakaus/impeccable --skill impeccable -g.
  • A mano: copia la carpeta skills/impeccable de la versión de tu herramienta (.claude/ para Claude Code, .agents/ para Codex) a ~/.claude/skills/ para Claude Code, o a ~/.agents/skills/ para Cursor, Codex y Gemini CLI. Hay ZIP por herramienta en impeccable.style.
  • App de Claude: comprime la carpeta impeccable en un ZIP y súbela desde Customize, Skills, «Upload a skill».

Necesitas Node para npx; la skill en sí usa un programa propio que se baja una vez a ~/.impeccable/bin/. Para el detector por URL hace falta Chrome o Edge. No pide claves de API.

El SKILL.md completo (con la licencia y la fuente) está más abajo.

El SKILL.md completo

Skill original de Paul Bakaus (Apache 2.0). Fuente: github.com/pbakaus/impeccable/tree/main/.claude/skills/impeccable.

El archivo original está en inglés y va tal cual, sin traducir. Lo de arriba de esta ficha es el resumen en español: qué hace, cómo aplicarla y cómo instalarla.

Leer el archivo (96 líneas)

This skill gives you the tools and permission to make design that earns the name out-of-distribution craft. Work as an award-winning design director would: production-grade code, a clear POV, a deep grasp of what the client and its users need, and exceptional craft.

Core principles:

  • Finish the job. No hedging, no shortcuts: the deliverable is complete, except assets the user must provide.
  • Scale ambition to the surface's mode (see Modes). Persuade and Experience get full commitment: bold, distinct work with a point of view. On Operate and Read, ambition shows as precision and restraint, and patterns the visitor already knows earn their place.
  • Verify by looking at the rendered result at the sizes it ships at, and batch the checks: fix what one look shows before looking again, rather than screenshotting after every tweak.

Setup

  1. Run <skill-base-dir>/scripts/impeccable context once per session, where <skill-base-dir> is the directory that contains this SKILL.md (the skill folder, not a plugin root two levels above it); keep cwd at the user's project. That base directory resolves every .claude/skills/impeccable/scripts/impeccable <verb> command in this skill and its references, and .claude/skills/impeccable/scripts is the fallback only when the runtime reports no base directory. On a Windows shell without sh, call .claude/skills/impeccable/scripts/impeccable.cmd instead. The launcher runs a self-contained binary that ships next to it or is downloaded once on first run; no Node or other runtime is required. Pass a named source file or route as --target <path>. It loads PRODUCT.md, DESIGN.md, the matching surface brief, and native-platform guidance when applicable; follow its directives and do not rerun it.
  2. Load the request's playbook: its Commands-table reference for an explicit/implied sub-command, or reference/new-work.md for a new surface, a replacement visual world, or a build from an approved comp. Some playbooks come in parts; read the part this request needs in the same step, not when the playbook later mentions it: reference/new-work-world.md when a visual world is created or replaced (a redesign, a new look, or no established world), reference/new-work-comp.md for a build from an approved comp or on a comp-led build path, and reference/critique-rubric.md for a critique whose Assessment A runs in this context (a native platform, or no sub-agent tool); a delegated Assessment A gets the rubric's path in its prompt instead. Inspect target and incumbent visual truth before editing. When the app cannot run, start with committed visual-regression goldens or screenshot fixtures; verify target and freshness against current tokens, CSS, components, or assets, resolve conflicts, and compare theme/variant captures.
  3. After resolving analysis and direction, read reference/craft-floor.md immediately before any UI edit, including small refinements. It carries the quality floor, the absolute bans, and the reflexes no detector catches. Do not load it for planning-only work.

Launcher unavailable: On refusal or failure, send a separate message before the next tool call: “Context loading did not run; I’ll read the existing project context directly.” Then read existing PRODUCT.md and DESIGN.md without inventing missing context, follow applicable steps 2–3, including reading reference/craft-floor.md immediately before any UI edit, and continue through permitted tools. This applies to planning and editing; launcher failure alone does not block either.

How to design

  • The brief wins. Honor pinned aesthetics, eras, materials, fonts, and palettes even when they conflict with a saturated-pattern warning. Redirecting a clear brief toward your taste is failure.
  • Refinement preserves; redesign replaces. Refinement keeps the incumbent identity, behavior, copy, and everything outside scope. Ask before replacing factual copy or adding claims. Redesign keeps product truth, content, function, native affordances, and constraints, but treats the old look as evidence and anti-reference; choose a replacement world in new-work and replace DESIGN.md. Never split the difference into polish on the discarded look.
  • Loaded symbols stay out of the decoration. A subject's world does not license emblems tied to militarism, supremacy, or hate movements as motifs, badges, or ornament, such as the Rising Sun flag's rays, the Confederate battle flag, or Nazi-era insignia and their stylised variants; reach for that world's neutral forms instead. Content that documents such a symbol as fact stays as it is.
  • Visual authority is evidence, not a filename. Missing DESIGN.md alone does not make a project greenfield; new-work decides whether to preserve, expand, or replace the incumbent world.

Modes

The mode names what the visitor's success looks like on this surface.

  • Persuade: the visitor decides and acts; design is the product. Landing pages, marketing, campaigns, pricing. Earn attention and action. Ship real imagery when the brief needs it; follow the committed world, not category habit.
  • Operate: the visitor completes a task. App UI, dashboards, editors, admin, settings, tools. Scanability, consistency, native expectations, and the real usage scene outrank expression. Brand lives in precise details.
  • Read: the visitor understands something. Docs, articles, guides, help, changelogs. Structure for comprehension, then make the reading experience worth staying in.
  • Experience: the visitor is inside the work itself. Portfolios, galleries, showcases. Let the artifact lead from the first viewport; the interface recedes.

Choose the mode from the requested surface, not the product, and persist it only in that surface brief. A tool's landing page is still Persuade; a fashion house's documentation is still Read; a docs index is Read, not Persuade. See new-work.md for new surfaces and operate.md for deeper Operate/Read guidance.

Commands

CommandCategoryDescriptionReference
craft [feature]BuildDeprecated alias for an ordinary new-work requestreference/craft.md
shape [feature]BuildPlan UX/UI before writing codereference/shape.md
initBuildCapture durable product context in PRODUCT.mdreference/init.md
documentBuildGenerate DESIGN.md from existing project codereference/document.md
extract [target]BuildPull reusable tokens and components into design systemreference/extract.md
critique [target]EvaluateUX design review with heuristic scoringreference/critique.md
audit [target]EvaluateTechnical quality checks (a11y, perf, responsive)reference/audit.md · native: reference/audit.native.md
polish [target]RefineFinal quality pass before shippingreference/polish.md
bolder [target]RefineAmplify safe or bland designsreference/bolder.md
quieter [target]RefineTone down aggressive or overstimulating designsreference/quieter.md
distill [target]RefineStrip to essence, remove complexityreference/distill.md
harden [target]RefineProduction-ready: errors, i18n, edge casesreference/harden.md
onboard [target]RefineDesign first-run flows, empty states, activationreference/onboard.md
animate [target]EnhanceAdd purposeful animations and motionreference/animate.md
colorize [target]EnhanceAdd strategic color to monochromatic UIsreference/colorize.md
typeset [target]EnhanceImprove typography hierarchy and fontsreference/typeset.md
layout [target]EnhanceFix spacing, rhythm, and visual hierarchyreference/layout.md
delight [target]EnhanceAdd personality and memorable touchesreference/delight.md
overdrive [target]EnhancePush past conventional limitsreference/overdrive.md
clarify [target]FixImprove UX copy, labels, and error messagesreference/clarify.md
adapt [target]FixAdapt for different devices and screen sizesreference/adapt.md · native: reference/adapt.native.md
optimize [target]FixDiagnose and fix UI performancereference/optimize.md
liveIterateVisual variant mode: pick elements in the browser, iterate on alternativesreference/live.md
generate [n] [action] [element]IterateVariants, versions, or alternatives of a named element to choose from in the live browser; no manual pickingreference/generate.md

Routing:

  • No argument: read routing.md and present its context-aware menu; never auto-run a command.
  • Explicit or clearly implied request to run a command: load its reference (native variant on native platforms) and follow it. Ask once if two commands fit.
  • Workflow or command-selection question: read Workflow questions.
  • Otherwise: treat the request as general design work. Missing PRODUCT.md routes a new surface or replacement world through init, then new-work; a narrow refinement of existing code proceeds on the incumbent implementation as impeccable context directs, offering init afterward rather than blocking on it.
  • teach aliases init. craft is a deprecated alias for ordinary new-work and adds nothing. shape owns task discovery, then enters new-work only for visual-world and surface-concept decisions.

After init writes PRODUCT.md, resume without rerunning impeccable context; init loads the native platform reference itself when the platform it recorded is ios, android, or adaptive.

Pin / Unpin: .claude/skills/impeccable/scripts/impeccable pin <pin|unpin> <command> creates or removes a standalone /<command> shortcut. Report the script's result concisely; relay stderr verbatim on error.

Hooks: /impeccable hooks <on|off|status|ignore-rule|ignore-file|ignore-value|reset> manages the design detector hook for this project (auto-runs the detector after UI file edits and surfaces findings). Load reference/hooks.md when the user invokes it with any argument.

Doctor: /impeccable doctor reports and repairs drift between this project's Impeccable artifacts (PRODUCT.md, DESIGN.md and its sidecar, config, surface briefs, the hook) and what this version reads. Load reference/doctor.md when the user invokes it, or when they ask what is out of date, stale, or needs refreshing. A CONTEXT_STALE directive in Setup's output is the cheap subset of the same report; act on it there per its own instructions rather than running doctor unasked.

Foundations: /impeccable foundations runs .claude/skills/impeccable/scripts/impeccable foundations and walks the user through the product-foundations roadmap (secrets, 404 page, icons, CI and more); /impeccable foundations <id> fixes that one item. Load reference/foundations.md when the user invokes it.

Never repair drift as a side effect of a design task. A CONTEXT_STALE finding is reported, not acted on, unless the user asks. The one exception is a finding marked auto, which the next write to that file performs anyway.

Copiar el archivo tal cual
---
name: impeccable
description: "Use to design, redesign, critique, audit, polish or animate a frontend: websites, landing pages, dashboards, app UI, components, native iOS/Android screens, or a design system (DESIGN.md)."
version: 4.9.2
user-invocable: true
argument-hint: "[shape · audit|critique · animate|bolder|colorize|delight|layout|overdrive|quieter|typeset · adapt|clarify|distill · harden|onboard|optimize|polish · init|document|extract|live|generate] [target]"
license: Apache 2.0
---

<!--
Skill original: impeccable, de Paul Bakaus (https://github.com/pbakaus/impeccable/tree/main/.claude/skills/impeccable)
Licencia: Apache 2.0. Reproducida con atribución según los términos de la licencia.
Copia publicada en claura-ai.com/skills.
-->

This skill gives you the tools and permission to make design that earns the name out-of-distribution craft. Work as an award-winning design director would: production-grade code, a clear POV, a deep grasp of what the client and its users need, and exceptional craft.

Core principles:
- Finish the job. No hedging, no shortcuts: the deliverable is complete, except assets the user must provide.
- Scale ambition to the surface's mode (see Modes). Persuade and Experience get full commitment: bold, distinct work with a point of view. On Operate and Read, ambition shows as precision and restraint, and patterns the visitor already knows earn their place.
- Verify by looking at the rendered result at the sizes it ships at, and batch the checks: fix what one look shows before looking again, rather than screenshotting after every tweak.

## Setup

1. Run `<skill-base-dir>/scripts/impeccable context` once per session, where `<skill-base-dir>` is the directory that contains this SKILL.md (the skill folder, not a plugin root two levels above it); keep cwd at the user's project. That base directory resolves every `.claude/skills/impeccable/scripts/impeccable <verb>` command in this skill and its references, and `.claude/skills/impeccable/scripts` is the fallback only when the runtime reports no base directory. On a Windows shell without `sh`, call `.claude/skills/impeccable/scripts/impeccable.cmd` instead. The launcher runs a self-contained binary that ships next to it or is downloaded once on first run; no Node or other runtime is required. Pass a named source file or route as `--target <path>`. It loads PRODUCT.md, DESIGN.md, the matching surface brief, and native-platform guidance when applicable; follow its directives and do not rerun it.
2. Load the request's playbook: its Commands-table reference for an explicit/implied sub-command, or [reference/new-work.md](reference/new-work.md) for a new surface, a replacement visual world, or a build from an approved comp. Some playbooks come in parts; read the part this request needs in the same step, not when the playbook later mentions it: [reference/new-work-world.md](reference/new-work-world.md) when a visual world is created or replaced (a redesign, a new look, or no established world), [reference/new-work-comp.md](reference/new-work-comp.md) for a build from an approved comp or on a comp-led build path, and [reference/critique-rubric.md](reference/critique-rubric.md) for a critique whose Assessment A runs in this context (a native platform, or no sub-agent tool); a delegated Assessment A gets the rubric's path in its prompt instead. Inspect target and incumbent visual truth before editing. When the app cannot run, start with committed visual-regression goldens or screenshot fixtures; verify target and freshness against current tokens, CSS, components, or assets, resolve conflicts, and compare theme/variant captures.
3. After resolving analysis and direction, read [reference/craft-floor.md](reference/craft-floor.md) immediately before any UI edit, including small refinements. It carries the quality floor, the absolute bans, and the reflexes no detector catches. Do not load it for planning-only work.

**Launcher unavailable:** On refusal or failure, send a separate message **before the next tool call**: “Context loading did not run; I’ll read the existing project context directly.” Then read existing PRODUCT.md and DESIGN.md without inventing missing context, follow applicable steps 2–3, including reading [reference/craft-floor.md](reference/craft-floor.md) immediately before any UI edit, and continue through permitted tools. This applies to planning and editing; launcher failure alone does not block either.

## How to design

- **The brief wins.** Honor pinned aesthetics, eras, materials, fonts, and palettes even when they conflict with a saturated-pattern warning. Redirecting a clear brief toward your taste is failure.
- **Refinement preserves; redesign replaces.** Refinement keeps the incumbent identity, behavior, copy, and everything outside scope. Ask before replacing factual copy or adding claims. Redesign keeps product truth, content, function, native affordances, and constraints, but treats the old look as evidence and anti-reference; choose a replacement world in new-work and replace DESIGN.md. Never split the difference into polish on the discarded look.
- **Loaded symbols stay out of the decoration.** A subject's world does not license emblems tied to militarism, supremacy, or hate movements as motifs, badges, or ornament, such as the Rising Sun flag's rays, the Confederate battle flag, or Nazi-era insignia and their stylised variants; reach for that world's neutral forms instead. Content that documents such a symbol as fact stays as it is.
- **Visual authority is evidence, not a filename.** Missing DESIGN.md alone does not make a project greenfield; new-work decides whether to preserve, expand, or replace the incumbent world.

## Modes

The mode names what the visitor's success looks like on this surface.

- **Persuade:** the visitor decides and acts; design is the product. Landing pages, marketing, campaigns, pricing. Earn attention and action. Ship real imagery when the brief needs it; follow the committed world, not category habit.
- **Operate:** the visitor completes a task. App UI, dashboards, editors, admin, settings, tools. Scanability, consistency, native expectations, and the real usage scene outrank expression. Brand lives in precise details.
- **Read:** the visitor understands something. Docs, articles, guides, help, changelogs. Structure for comprehension, then make the reading experience worth staying in.
- **Experience:** the visitor is inside the work itself. Portfolios, galleries, showcases. Let the artifact lead from the first viewport; the interface recedes.

Choose the mode from the requested surface, not the product, and persist it only in that surface brief. A tool's landing page is still Persuade; a fashion house's documentation is still Read; a docs index is Read, not Persuade. See [new-work.md](reference/new-work.md) for new surfaces and [operate.md](reference/operate.md) for deeper Operate/Read guidance.

## Commands

| Command | Category | Description | Reference |
|---|---|---|---|
| `craft [feature]` | Build | Deprecated alias for an ordinary new-work request | [reference/craft.md](reference/craft.md) |
| `shape [feature]` | Build | Plan UX/UI before writing code | [reference/shape.md](reference/shape.md) |
| `init` | Build | Capture durable product context in PRODUCT.md | [reference/init.md](reference/init.md) |
| `document` | Build | Generate DESIGN.md from existing project code | [reference/document.md](reference/document.md) |
| `extract [target]` | Build | Pull reusable tokens and components into design system | [reference/extract.md](reference/extract.md) |
| `critique [target]` | Evaluate | UX design review with heuristic scoring | [reference/critique.md](reference/critique.md) |
| `audit [target]` | Evaluate | Technical quality checks (a11y, perf, responsive) | [reference/audit.md](reference/audit.md) · native: [reference/audit.native.md](reference/audit.native.md) |
| `polish [target]` | Refine | Final quality pass before shipping | [reference/polish.md](reference/polish.md) |
| `bolder [target]` | Refine | Amplify safe or bland designs | [reference/bolder.md](reference/bolder.md) |
| `quieter [target]` | Refine | Tone down aggressive or overstimulating designs | [reference/quieter.md](reference/quieter.md) |
| `distill [target]` | Refine | Strip to essence, remove complexity | [reference/distill.md](reference/distill.md) |
| `harden [target]` | Refine | Production-ready: errors, i18n, edge cases | [reference/harden.md](reference/harden.md) |
| `onboard [target]` | Refine | Design first-run flows, empty states, activation | [reference/onboard.md](reference/onboard.md) |
| `animate [target]` | Enhance | Add purposeful animations and motion | [reference/animate.md](reference/animate.md) |
| `colorize [target]` | Enhance | Add strategic color to monochromatic UIs | [reference/colorize.md](reference/colorize.md) |
| `typeset [target]` | Enhance | Improve typography hierarchy and fonts | [reference/typeset.md](reference/typeset.md) |
| `layout [target]` | Enhance | Fix spacing, rhythm, and visual hierarchy | [reference/layout.md](reference/layout.md) |
| `delight [target]` | Enhance | Add personality and memorable touches | [reference/delight.md](reference/delight.md) |
| `overdrive [target]` | Enhance | Push past conventional limits | [reference/overdrive.md](reference/overdrive.md) |
| `clarify [target]` | Fix | Improve UX copy, labels, and error messages | [reference/clarify.md](reference/clarify.md) |
| `adapt [target]` | Fix | Adapt for different devices and screen sizes | [reference/adapt.md](reference/adapt.md) · native: [reference/adapt.native.md](reference/adapt.native.md) |
| `optimize [target]` | Fix | Diagnose and fix UI performance | [reference/optimize.md](reference/optimize.md) |
| `live` | Iterate | Visual variant mode: pick elements in the browser, iterate on alternatives | [reference/live.md](reference/live.md) |
| `generate [n] [action] [element]` | Iterate | Variants, versions, or alternatives of a named element to choose from in the live browser; no manual picking | [reference/generate.md](reference/generate.md) |

Routing:

- **No argument:** read [routing.md](reference/routing.md) and present its context-aware menu; never auto-run a command.
- **Explicit or clearly implied request to run a command:** load its reference (native variant on native platforms) and follow it. Ask once if two commands fit.
- **Workflow or command-selection question:** read [Workflow questions](reference/routing.md#workflow-questions).
- **Otherwise:** treat the request as general design work. Missing PRODUCT.md routes a new surface or replacement world through init, then new-work; a narrow refinement of existing code proceeds on the incumbent implementation as `impeccable context` directs, offering init afterward rather than blocking on it.
- `teach` aliases `init`. `craft` is a deprecated alias for ordinary new-work and adds nothing. `shape` owns task discovery, then enters new-work only for visual-world and surface-concept decisions.

After init writes PRODUCT.md, resume without rerunning `impeccable context`; init loads the native platform reference itself when the platform it recorded is `ios`, `android`, or `adaptive`.

**Pin / Unpin:** `.claude/skills/impeccable/scripts/impeccable pin <pin|unpin> <command>` creates or removes a standalone `/<command>` shortcut. Report the script's result concisely; relay stderr verbatim on error.

**Hooks:** `/impeccable hooks <on|off|status|ignore-rule|ignore-file|ignore-value|reset>` manages the design detector hook for this project (auto-runs the detector after UI file edits and surfaces findings). Load [reference/hooks.md](reference/hooks.md) when the user invokes it with any argument.

**Doctor:** `/impeccable doctor` reports and repairs drift between this project's Impeccable artifacts (PRODUCT.md, DESIGN.md and its sidecar, config, surface briefs, the hook) and what this version reads. Load [reference/doctor.md](reference/doctor.md) when the user invokes it, or when they ask what is out of date, stale, or needs refreshing. A `CONTEXT_STALE` directive in Setup's output is the cheap subset of the same report; act on it there per its own instructions rather than running doctor unasked.

**Foundations:** `/impeccable foundations` runs `.claude/skills/impeccable/scripts/impeccable foundations` and walks the user through the product-foundations roadmap (secrets, 404 page, icons, CI and more); `/impeccable foundations <id>` fixes that one item. Load [reference/foundations.md](reference/foundations.md) when the user invokes it.

**Never repair drift as a side effect of a design task.** A `CONTEXT_STALE` finding is reported, not acted on, unless the user asks. The one exception is a finding marked `auto`, which the next write to that file performs anyway.

Preguntas frecuentes sobre la skill impeccable

¿Qué es la skill impeccable y para qué sirve?

impeccable es una skill de Paul Bakaus (github.com/pbakaus/impeccable, licencia Apache 2.0) que convierte a Claude en un director de diseño con un vocabulario de órdenes concretas. En lugar de pedir "hazlo más lindo", le dices /impeccable critique sobre la sección de precios, /impeccable bolder sobre un hero apagado o /impeccable polish antes de publicar, y cada comando carga su propio manual de trabajo. Trae además un detector de 62 reglas, sin IA ni claves de API, que marca los tics de lo generado: Inter en todo, degradés de violeta a azul, tarjetas dentro de tarjetas o texto gris sobre fondo de color. Su autor dice que rinde más sobre interfaces que ya existen.

¿Cómo la aplico a la web de mi negocio?

Instálala en la carpeta del proyecto con npx impeccable install y corre una vez /impeccable init: lee tu código, te pregunta solo lo que no puede deducir (para quién es, qué tiene que lograr, qué restricciones hay) y guarda las respuestas en un archivo PRODUCT.md que leen todos los comandos. Si ya tienes una identidad visual, /impeccable document la deja escrita en DESIGN.md para que los cambios no se salgan de tu marca. Después trabaja por partes chicas: una crítica de la página de servicios, un pulido del formulario. Una sección revisada de cerca da mejor resultado que la página entera de un vistazo.

¿En qué se diferencia de frontend-design, la skill de Anthropic?

frontend-design es un solo archivo de criterio: le dice a Claude cómo pensar el diseño de una página nueva. impeccable nació de esa misma base y le suma un sistema completo: cuatro modos según el tipo de página (persuadir, operar, leer, mostrar), 24 comandos con un manual por comando, una evaluación de accesibilidad y rendimiento con hallazgos ordenados de P0 (bloqueante) a P3 (detalle), un modo en vivo para elegir variantes en el navegador y un aviso automático que corre el detector cada vez que el agente edita un archivo de interfaz. Si solo vas a instalar una para mejorar una web existente, esta es la más completa.

¿Qué necesito instalado y qué cuidados tiene?

Node solo hace falta para correr npx; la skill usa un programa propio que viene junto a ella o se baja una vez a tu carpeta personal. El detector por URL usa tu Chrome o Edge instalado. Está en inglés: si le escribes en español, responde y redacta en español. El cuidado real es el modo en vivo: según su README, si ningún chat está atento, aplica las ediciones de texto lanzando el agente de terminal con las aprobaciones y el aislamiento desactivados, así que úsalo solo en tu copia local y nunca sobre la web publicada. Para ver otras opciones del mismo trabajo, repasa las skills para diseño web.

Más skills de Contenido

Para seguir con este tema

Elegí qué cookies usamos