Modo
Agendar llamada

frontend-design: diseñar interfaces web que no parezcan hechas con IA

Le da a Claude criterio de director de arte para que la web que construye tenga una identidad propia y no la cara genérica de una página generada.

frontend-design: diseñar interfaces web que no parezcan hechas con IA

Respuesta rápida

Qué es
frontend-design es una skill de Anthropic (licencia Apache 2.0) que le enseña a Claude a diseñar interfaces con un punto de vista propio en vez de la plantilla de siempre.
Qué le das
El brief de la página: qué vendes, a quién y qué tiene que lograr quien la visita
Qué te devuelve
Un plan de diseño (paleta, tipografía, maqueta y principios) revisado contra el brief y la página construida en código
Licencia
Apache 2.0
En GitHub
195,4 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 anthropics/skills --skill frontend-design -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.

  • Diseña la landing de ortodoncia invisible de mi clínica en Guadalajara: atendemos adultos que trabajan, el objetivo es que agenden por WhatsApp y tengo 12 fotos de casos. Muéstrame primero la paleta, las fuentes y la maqueta.

  • Rediseña la portada de mi estudio contable para que no parezca una plantilla: este es el texto actual [pega el texto].

  • Arma una página de producto para una marca de café de especialidad colombiana con su historia de origen y un botón de compra.

#Qué hace

frontend-design es una de las skills oficiales de Anthropic. Le pide a Claude que encare cada pedido de interfaz como el director de diseño de un estudio conocido por darle a cada cliente una identidad que no se confunde con la de nadie. Lo primero es anclar el diseño en el tema: si el brief no dice qué es el producto, a quién va y cuál es el trabajo principal de la página, Claude tiene que proponerlo y confirmarlo. De ahí salen las decisiones visuales, porque el rubro, sus materiales y su vocabulario son la fuente de lo distintivo.

Trae reglas concretas de oficio. El hero abre con lo más característico del mundo del cliente (un titular, una imagen, una demo en vivo), no con el número grande y el degradé de siempre. Una o dos familias tipográficas elegidas a propósito, con una escala clara y líneas de menos de 80 caracteres. Prohíbe los tics más comunes de lo generado: resaltar una sola palabra del titular, etiquetas en mayúsculas sobre cada bloque y numeraciones 01, 02, 03 cuando el contenido no es una secuencia. El movimiento se usa poco: un solo momento orquestado al cargar vale más que cada sección entrando con un fundido.

El proceso tiene dos pasadas. Primero un plan compacto: 4 a 6 colores con nombre y código hexadecimal, las fuentes y su rol, una maqueta descrita en una frase y en un boceto de texto, y los principios que hacen única a esa página. Ese plan se revisa contra cinco rasgos que el archivo identifica como la estética típica de la IA (el fondo crema con acento terracota, el negro con verde ácido, el estilo diario, el kit de tarjetas SaaS y los adornos de plantilla) y se corrige lo que suene genérico, explicando qué cambió. Recién después se escribe el código, con un piso de calidad: adaptable al móvil, foco de teclado visible, respeto por quien reduce el movimiento y una sección final sobre cómo escribir los textos de la interfaz.

#Cómo aplicarla a tu negocio

Caso de ejemplo: una clínica odontológica de Guadalajara quiere una landing para su servicio de ortodoncia invisible, con un botón para agendar la primera consulta.

  1. Dale un brief real. En vez de "hazme una landing de ortodoncia", le pasas: atendemos a adultos de 25 a 45 años que trabajan y no quieren brackets visibles, la consulta inicial cuesta 600 pesos (ejemplo), tenemos 12 fotos de casos con permiso de los pacientes y el objetivo es que agenden por WhatsApp.
  2. Revisa el plan antes del código. La skill hace que Claude te muestre primero la paleta, las fuentes y la maqueta en texto. Si te propone el típico azul médico con tarjetas redondeadas, es el momento de pedir otra cosa ("algo más cercano a una marca de cosmética que a un hospital").
  3. Pide la página construida. Sale con el hero armado alrededor de lo más propio del caso (por ejemplo, la sonrisa de antes y después a pantalla completa, no un ícono de diente), los textos escritos desde el paciente y un solo botón que dice exactamente lo que hace: "Agendar mi consulta".
  4. Quita un accesorio. El archivo cita el consejo de Chanel de mirarse al espejo y sacar una cosa antes de salir. Pídele a Claude que lo haga con la página: suele sobrar un efecto o una sección.

Para cuidar además la conversión del texto, combínala con improved-copywriting, y antes de publicar pasa la página por web-design-guidelines para revisar accesibilidad y formularios.

#Cómo instalarla

Es un solo SKILL.md, sin scripts ni dependencias, y corre en cualquier agente que lea skills.

  • Con una línea, para cualquier agente: npx skills add anthropics/skills --skill frontend-design -g la deja instalada en todos tus proyectos.
  • Claude Code, como plugin: /plugin marketplace add anthropics/skills y después /plugin install example-skills@anthropic-agent-skills (trae esta skill junto con las demás de ejemplo de Anthropic).
  • A mano: copia la carpeta frontend-design del repo a ~/.claude/skills/ para Claude Code, o a ~/.agents/skills/ para Cursor, Codex y Gemini CLI (las tres leen esa carpeta).
  • App de Claude: comprime la carpeta en un ZIP y súbela desde Customize, Skills, «Upload a skill».

No pide nada más: ni Node, ni Python, ni claves de API. Para que Claude se autocritique con capturas, ayuda que tu entorno pueda abrir la página en un navegador.

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

El SKILL.md completo

Skill original de Anthropic (Apache 2.0). Fuente: github.com/anthropics/skills/tree/main/skills/frontend-design.

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 (78 líneas)

Frontend Design

Approach this as the design lead at a design studio known for giving every client a distinct visual identity that is not mistaken for anyone else's. This client has already rejected proposals that felt cliché or templated, and is paying for a distinctive point of view: make deliberate, opinionated choices about palette, typography, and layout that are specific to this brief, and take aesthetic risk if justified.

Ground your designs in the subject matter

If the brief does not identify what the product or subject matter is, identify it yourself before designing, and confirm with the client. You can come up with one concrete subject, the design's audience, and the design's primary job, as a proposal. If there's any information in your memory about the client's preferences or context about what they're building, use that as a hint. The subject's industry, subject matter, materials, and vernacular are where distinctive visual choices come from — a design for a toy for girls aged 8–11 will be very aesthetically different from a dashboard for financial analysts. Build with the brief's real content and subject matter throughout.

Design principles

For web designs, the hero is the first thing viewers will see. Open with the most characteristic thing in the subject's world, in the form that is most appropriate: a headline, an image, an animation, a live demo, an interactive moment, or other treatments. Be deliberate with your choice: a big number with a small label, supporting stats, and a gradient accent is the default treatment, so only use it if that's truly the best option.

Typography carries the personality of the page. You don't need a different typeface for display or headline text and body content: use one family or two, and if two, make them clearly distinct.

Choose your typefaces deliberately, not the default families you would reach for on any other project, and set a clear type scale following the default guidance of The Elements of Typographic Style with intentional weights, widths, and spacing. When type is used as a headline or visual element, use the type treatment itself as an active part of the design, not a neutral delivery vehicle for the content.

Default to line lengths of less than 80 characters. Serif typefaces can have slightly longer line lengths; give serif body text slightly more line-height than a sans-serif.

Avoid these default typographic treatments; they are the commonest tells of a generated page:

  • Accenting just a single word or phrase in a headline, like putting one word in italic/bold or a different color.
  • Using all caps for labels.
  • Adding unnecessary typographic labels above content.

Visual structure is information. Structural devices like outlines, borders, numbering, eyebrows, dividers, labels, etc., encode useful information about the content rather than decorate it. Many generic designs use numbered markers (01 / 02 / 03), but that's only appropriate if the content actually is a sequence — like a stepped process or a timeline. Before adding numbered markers, check the content really is a sequence.

Use non-user-triggered motion sparingly and deliberately, only to draw attention. A single orchestrated moment — one page-load sequence or one reveal — lands better than scattered effects; fade-and-slide-up entrances on each section and hover transitions on every card are the generic default and read as AI-generated. Motion that answers a person's action (opening, expanding, confirming) is welcome when it shows what changed.

Consider written content carefully. Often a design brief may not contain real content, and it's up to you to come up with copy and placeholder content. Copy can make a design feel as templated as the design itself. See the below section on writing for more guidance.

Process: plan, review against the brief, build, critique

For calibration, AI-generated design right now clusters around some traits:

  1. a warm cream background (near #F4F1EA) with a high-contrast serif display and a terracotta or warm-clay accent (often near #D97757 — Anthropic's own Claude-interaction accent, so on a user's brief it reads as a tell);
  2. a near-black background with a single bright acid-green or vermilion accent;
  3. a broadsheet-style layout with hairline rules, zero border-radius, and dense newspaper-like columns;
  4. the SaaS-card kit: content chopped into identical rounded cards, one border-radius on everything regardless of hierarchy, the same soft grey shadow (rgba(0,0,0,.1)) under each, and gradient washes as decoration;
  5. template chrome that appears whatever the subject: a tracked-out ALL-CAPS eyebrow label above every heading; meta strings joined with middle dots ('A · B · C'); labels built as 'WORD — fragment' with a spaced em dash; tinted near-black (#0B0B0B, #111) standing in for black; a monospace face for small data labels; a '→' appended to link and button text.

All traits are legitimate for some briefs, but they are defaults rather than choices, and they appear regardless of subject. Where the brief pins down a visual direction, follow it exactly — the brief's own words always win, including when it asks for one of these looks. Where it leaves an axis free, don't spend that freedom on one of these defaults. As with a hired human designer, there's often a careful balance between doing what you're good at and taking each project as a chance to experiment and learn.

Work in two passes. First, brainstorm a short design plan based on the client's design brief: create a compact token system with color, type, layout, and principles.

  • Color: describe the core base palette as 4–6 named hex values.
  • Type: the typefaces and their roles.
  • Layout: a layout concept, using one-sentence prose descriptions and ASCII wireframes to ideate and compare. Include alignment guidance; should the content be left aligned, center aligned, justified?
  • Principles: the high-level guidance for what makes this page unique.

Then review that plan against the brief before building: if any part of it reads like the generic default you would produce for any similar page (work through a similar prompt to see if you arrive somewhere similar) rather than a choice made for this specific brief — revise that part, say what you changed and why. Only after you've confirmed the relative uniqueness of your design plan should you start to write the code, following the revised plan.

When writing the code, be careful of structuring your CSS selector specificities. It's easy to generate CSS classes that cancel each other out (especially with a type-based selector like .section and an element-based selector like .cta). This can happen often with padding/margin between sections.

Restraint and self-critique

Spend your boldness in one place. Let one element be the memorable thing, keep everything around it quiet and disciplined, and cut any decoration that does not serve the brief. Build to a quality floor without announcing it: responsive down to mobile, visible keyboard focus, reduced motion respected, visually accessible, harmonious color palettes. Critique your own work as you build, taking screenshots to review if your environment supports it — a picture is worth 1000 tokens. Consider Chanel's advice: before leaving the house, take a look in the mirror and remove one accessory. Human creatives have memory and always try to do something new, so if you have a space to quickly jot down notes about what you've tried, it can help you in future passes.

More on writing in design

Words appear in a design for one reason: to make it easier to understand and use. They are design content, not decoration. Bring the same intentionality and minimalism to copywriting that you would bring to spacing and color. Before writing anything, ask what the design needs to say, and how it can best be said to help the person navigate the experience.

Write from the end user's perspective. Name things by what users will understand in simple language, not by how the system is built. A user manages notifications, not webhook config. Describe what something is or does in plain terms rather than selling it. Being specific and legible to new users is always better than being clever.

Use active voice as default. A CTA says exactly what happens when it is used: "Save changes," not "Submit." An action keeps the same name through the whole flow, so the button that says "Publish" produces a toast that says "Published." The vocabulary of an interface is the signposting for someone navigating the product. Cohesion and consistency are how people learn their way around.

Treat failure and emptiness as moments for direction, not mood. Explain what went wrong and how to fix it, in the interface's voice rather than a person's. Errors don't apologize, and they are never vague about what happened. An empty screen is an invitation to act.

Keep the tone conversational: plain verbs, sentence case, no filler, with tone matched to the brand and the audience. Let each written element do exactly one job.

Copiar el archivo tal cual
---
name: frontend-design
description: Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
license: Complete terms in LICENSE.txt
---

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

# Frontend Design

Approach this as the design lead at a design studio known for giving every client a distinct visual identity that is not mistaken for anyone else's. This client has already rejected proposals that felt cliché or templated, and is paying for a distinctive point of view: make deliberate, opinionated choices about palette, typography, and layout that are specific to this brief, and take aesthetic risk if justified.

## Ground your designs in the subject matter

If the brief does not identify what the product or subject matter is, identify it yourself before designing, and confirm with the client. You can come up with one concrete subject, the design's audience, and the design's primary job, as a proposal. If there's any information in your memory about the client's preferences or context about what they're building, use that as a hint. The subject's industry, subject matter, materials, and vernacular are where distinctive visual choices come from — a design for a toy for girls aged 8–11 will be very aesthetically different from a dashboard for financial analysts. Build with the brief's real content and subject matter throughout.

## Design principles

For web designs, the hero is the first thing viewers will see. Open with the most characteristic thing in the subject's world, in the form that is most appropriate: a headline, an image, an animation, a live demo, an interactive moment, or other treatments. Be deliberate with your choice: a big number with a small label, supporting stats, and a gradient accent is the default treatment, so only use it if that's truly the best option.

Typography carries the personality of the page. You don't need a different typeface for display or headline text and body content: use one family or two, and if two, make them clearly distinct.

Choose your typefaces deliberately, not the default families you would reach for on any other project, and set a clear type scale following the default guidance of The Elements of Typographic Style with intentional weights, widths, and spacing. When type is used as a headline or visual element, use the type treatment itself as an active part of the design, not a neutral delivery vehicle for the content.

Default to line lengths of less than 80 characters. Serif typefaces can have slightly longer line lengths; give serif body text slightly more line-height than a sans-serif.

Avoid these default typographic treatments; they are the commonest tells of a generated page:
- Accenting just a single word or phrase in a headline, like putting one word in italic/bold or a different color.
- Using all caps for labels.
- Adding unnecessary typographic labels above content.

Visual structure is information. Structural devices like outlines, borders, numbering, eyebrows, dividers, labels, etc., encode useful information about the content rather than decorate it. Many generic designs use numbered markers (01 / 02 / 03), but that's only appropriate if the content actually is a sequence — like a stepped process or a timeline. Before adding numbered markers, check the content really is a sequence.

Use non-user-triggered motion sparingly and deliberately, only to draw attention. A single orchestrated moment — one page-load sequence or one reveal — lands better than scattered effects; fade-and-slide-up entrances on each section and hover transitions on every card are the generic default and read as AI-generated. Motion that answers a person's action (opening, expanding, confirming) is welcome when it shows what changed.

Consider written content carefully. Often a design brief may not contain real content, and it's up to you to come up with copy and placeholder content. Copy can make a design feel as templated as the design itself. See the below section on writing for more guidance.

## Process: plan, review against the brief, build, critique

For calibration, AI-generated design right now clusters around some traits:
1. a warm cream background (near #F4F1EA) with a high-contrast serif display and a terracotta or warm-clay accent (often near #D97757 — Anthropic's own Claude-interaction accent, so on a user's brief it reads as a tell);
2. a near-black background with a single bright acid-green or vermilion accent;
3. a broadsheet-style layout with hairline rules, zero border-radius, and dense newspaper-like columns;
4. the SaaS-card kit: content chopped into identical rounded cards, one border-radius on everything regardless of hierarchy, the same soft grey shadow (rgba(0,0,0,.1)) under each, and gradient washes as decoration;
5. template chrome that appears whatever the subject: a tracked-out ALL-CAPS eyebrow label above every heading; meta strings joined with middle dots ('A · B · C'); labels built as 'WORD — fragment' with a spaced em dash; tinted near-black (#0B0B0B, #111) standing in for black; a monospace face for small data labels; a '→' appended to link and button text.

All traits are legitimate for some briefs, but they are defaults rather than choices, and they appear regardless of subject. Where the brief pins down a visual direction, follow it exactly — the brief's own words always win, including when it asks for one of these looks. Where it leaves an axis free, don't spend that freedom on one of these defaults. As with a hired human designer, there's often a careful balance between doing what you're good at and taking each project as a chance to experiment and learn.

Work in two passes. First, brainstorm a short design plan based on the client's design brief: create a compact token system with color, type, layout, and principles.
- Color: describe the core base palette as 4–6 named hex values.
- Type: the typefaces and their roles.
- Layout: a layout concept, using one-sentence prose descriptions and ASCII wireframes to ideate and compare. Include alignment guidance; should the content be left aligned, center aligned, justified?
- Principles: the high-level guidance for what makes this page unique.

Then review that plan against the brief before building: if any part of it reads like the generic default you would produce for any similar page (work through a similar prompt to see if you arrive somewhere similar) rather than a choice made for this specific brief — revise that part, say what you changed and why. Only after you've confirmed the relative uniqueness of your design plan should you start to write the code, following the revised plan.

When writing the code, be careful of structuring your CSS selector specificities. It's easy to generate CSS classes that cancel each other out (especially with a type-based selector like .section and an element-based selector like .cta). This can happen often with padding/margin between sections.

## Restraint and self-critique

Spend your boldness in one place. Let one element be the memorable thing, keep everything around it quiet and disciplined, and cut any decoration that does not serve the brief. Build to a quality floor without announcing it: responsive down to mobile, visible keyboard focus, reduced motion respected, visually accessible, harmonious color palettes. Critique your own work as you build, taking screenshots to review if your environment supports it — a picture is worth 1000 tokens. Consider Chanel's advice: before leaving the house, take a look in the mirror and remove one accessory. Human creatives have memory and always try to do something new, so if you have a space to quickly jot down notes about what you've tried, it can help you in future passes.

## More on writing in design

Words appear in a design for one reason: to make it easier to understand and use. They are design content, not decoration. Bring the same intentionality and minimalism to copywriting that you would bring to spacing and color. Before writing anything, ask what the design needs to say, and how it can best be said to help the person navigate the experience.

Write from the end user's perspective. Name things by what users will understand in simple language, not by how the system is built. A user manages notifications, not webhook config. Describe what something is or does in plain terms rather than selling it. Being specific and legible to new users is always better than being clever.

Use active voice as default. A CTA says exactly what happens when it is used: "Save changes," not "Submit." An action keeps the same name through the whole flow, so the button that says "Publish" produces a toast that says "Published." The vocabulary of an interface is the signposting for someone navigating the product. Cohesion and consistency are how people learn their way around.

Treat failure and emptiness as moments for direction, not mood. Explain what went wrong and how to fix it, in the interface's voice rather than a person's. Errors don't apologize, and they are never vague about what happened. An empty screen is an invitation to act.

Keep the tone conversational: plain verbs, sentence case, no filler, with tone matched to the brand and the audience. Let each written element do exactly one job.

Preguntas frecuentes sobre la skill frontend-design

¿Qué es la skill frontend-design y para qué sirve?

frontend-design es una skill oficial de Anthropic (github.com/anthropics/skills, licencia Apache 2.0) que se activa cuando le pides a Claude construir o rediseñar una interfaz: una landing, una web institucional, un panel. Le dice que trabaje como el director de diseño de un estudio cuyo cliente ya rechazó propuestas con cara de plantilla. En la práctica lo obliga a anclar el diseño en el rubro real del negocio, a elegir tipografía y paleta a propósito, a planificar antes de escribir código y a revisar ese plan contra el brief. Sirve para que la página salga con identidad y no con el aspecto que se repite en todo lo generado con IA.

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

Instálala y pídele a Claude la página como se la pedirías a un diseñador: qué vendes, a quién, qué tiene que hacer el visitante (reservar, pedir presupuesto, comprar) y el material real que tienes (fotos, textos, precios). Si el brief no dice de qué es el negocio, la skill le indica a Claude que lo proponga y te lo confirme antes de diseñar. Primero te muestra un plan compacto con 4 a 6 colores con nombre y código, las fuentes y una maqueta en texto, y recién después construye. Ese es el momento de corregir el rumbo. Si quieres otras opciones para el mismo trabajo, mira las skills para diseño web.

¿En qué se diferencia de pedirle a Claude "hazme una landing" sin la skill?

Sin la skill, Claude tiende a sus valores por defecto. El propio archivo los enumera: fondo crema con serif y acento terracota, fondo casi negro con un solo color ácido, columnas de diario con filetes finos, contenido picado en tarjetas redondeadas iguales con la misma sombra gris, etiquetas en mayúsculas sobre cada título y una flecha al final de cada botón. Con la skill, cada uno de esos rasgos solo entra si el brief lo pide o si es de verdad la mejor opción. Además lo obliga a escribir los textos desde el usuario (el botón dice "Guardar cambios", no "Enviar") y a autocriticarse con capturas de pantalla si el entorno lo permite.

¿Qué necesito para usarla y qué limitaciones tiene?

No necesita claves de API ni programas extra: es un solo archivo de instrucciones, sin scripts. Está escrita en inglés, pero si le hablas en español Claude escribe los textos de la página en español; conviene aclarar si quieres español neutro o de tu país. La limitación real es que da criterio, no material: si no le das fotos ni textos reales, inventa contenido de relleno y la página pierde fuerza. Tampoco revisa una web que ya existe con un sistema de comandos; para eso está impeccable, que nació a partir de esta skill y le suma auditoría y pulido.

Más skills de Contenido

Para seguir con este tema

Elegí qué cookies usamos