Communitygithub.com

/design-handoff

Genera especificaciones técnicas para desarrolladores a partir de un diseño. Úsalo cuando un diseño esté listo para ingeniería y necesite una hoja de especificaciones que cubra layout, tokens de diseño, props de componentes, estados de interacción, puntos de ruptura responsive, casos límite y detalles de animación.

¿Qué es design-handoff?

Esta skill permite generar documentación completa de traspaso (handoff) para desarrolladores a partir de un diseño. Es útil cuando un diseñador finaliza un diseño y el equipo de ingeniería necesita una especificación detallada que incluya medidas exactas, tokens de diseño (colores, tipografía, espaciado), referencias a componentes, variantes y props, así como todos los estados interactivos (hover, activo, deshabilitado, carga, error, vacío). La skill soporta la entrada directa de una URL de Figma, una descripción textual o una captura de pantalla. Si se proporciona una URL de Figma, extrae automáticamente las medidas, tokens y especificaciones de componentes. También puede integrarse con herramientas de gestión de proyectos para enlazar la especificación a tareas de implementación. Entre los principios clave destacan: no asumir nada (especificarlo todo), usar tokens en lugar de valores concretos, mostrar todos los estados posibles y describir el "por qué" de cada decisión de diseño. La salida se estructura en una tabla markdown con secciones como visión general, layout, tokens usados, componentes, estados e interacciones, comportamiento responsive, casos límite, animaciones y notas de accesibilidad. Está diseñada para entornos de desarrollo con React, Tailwind, y es compatible con Claude Code, Cursor y otras herramientas de IA para desarrolladores. La skill fomenta la transferencia precisa entre diseño e ingeniería, reduciendo ambigüedades y acelerando la implementación.

Compatible con~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/xzedm/clipplic-landing/tree/HEAD/.agents/skills/design-handoff

Preguntar en tu IA favorita

Abre un nuevo chat con esta habilidad de agente ya precargada.

Documentación

¿Qué hace design-handoff?

Si ves marcadores de posición desconocidos o necesitas verificar qué herramientas están conectadas, consulta CONNECTORS.md.

Genera documentación completa de traspaso para desarrolladores a partir de un diseño.

Uso

/design-handoff $ARGUMENTOS

Genera especificaciones de traspaso para: @$1

Si se proporciona una URL de Figma, obtén el diseño desde Figma. De lo contrario, trabaja a partir de la descripción o captura de pantalla proporcionada.

Qué Incluir

Especificaciones Visuales

  • Medidas exactas (padding, márgenes, anchos)
  • Referencias a tokens de diseño (colores, tipografía, espaciado)
  • Puntos de ruptura responsive y comportamiento
  • Variantes de componentes y estados

Especificaciones de Interacción

  • Comportamiento de clic/toque
  • Estados hover
  • Transiciones y animaciones (duración, easing)
  • Soporte de gestos (deslizar, pellizcar, pulsación larga)

Especificaciones de Contenido

  • Límites de caracteres
  • Comportamiento de truncamiento
  • Estados vacíos
  • Estados de carga
  • Estados de error

Casos Límite

  • Contenido mínimo/máximo
  • Texto internacional (cadenas más largas)
  • Conexiones lentas
  • Datos faltantes

Accesibilidad

  • Orden de enfoque
  • Etiquetas y roles ARIA
  • Interacciones con teclado
  • Anuncios de lector de pantalla

Principios

  1. No asumas: Si no se especifica, el desarrollador supondrá. Especifica todo.
  2. Usa tokens, no valores: Referencia spacing-md no 16px.
  3. Muestra todos los estados: Default, hover, activo, deshabilitado, carga, error, vacío.
  4. Describe el por qué: "Esto se colapsa en móvil porque los usuarios usan principalmente una mano" ayuda a los desarrolladores a tomar buenas decisiones.

Salida

## Especificación de Traspaso: [Nombre de la Funcionalidad/Pantalla]

### Resumen
[Qué hace esta pantalla/funcionalidad, contexto del usuario]

### Layout
[Sistema de rejilla, puntos de ruptura, comportamiento responsive]

### Tokens de Diseño Usados
| Token | Valor | Uso |
|-------|-------|------|
| `color-primary` | #[hex] | Botones CTA, enlaces |
| `spacing-md` | [X]px | Entre secciones |
| `font-heading-lg` | [tamaño/grosor/familia] | Título de página |

### Componentes
| Componente | Variante | Props | Notas |
|------------|----------|-------|-------|
| [Componente] | [Variante] | [Props] | [Comportamiento especial] |

### Estados e Interacciones
| Elemento | Estado | Comportamiento |
|----------|--------|----------------|
| [Botón CTA] | Hover | [Fondo oscurece 10%] |
| [Botón CTA] | Cargando | [Spinner, deshabilitado] |
| [Formulario] | Error | [Borde rojo, mensaje de error debajo] |

### Comportamiento Responsive
| Punto de Ruptura | Cambios |
|------------------|---------|
| Escritorio (>1024px) | [Layout por defecto] |
| Tablet (768-1024px) | [Qué cambia] |
| Móvil (<768px) | [Qué cambia] |

### Casos Límite
- **Estado vacío**: [Qué mostrar cuando no hay datos]
- **Texto largo**: [Reglas de truncamiento]
- **Carga**: [Esqueleto o spinner]
- **Error**: [Apariencia del estado de error]

### Animación / Movimiento
| Elemento | Disparador | Animación | Duración | Easing |
|----------|------------|-----------|----------|--------|
| [Elemento] | [Disparador] | [Descripción] | [ms] | [easing] |

### Notas de Accesibilidad
- [Orden de enfoque]
- [Etiquetas ARIA necesarias]
- [Interacciones con teclado]

Si hay Conectores Disponibles

Si ~~herramienta de diseño está conectada:

  • Obtén medidas exactas, tokens y especificaciones de componentes desde Figma
  • Exporta activos y genera una hoja de especificaciones completa

Si ~~gestor de proyectos está conectado:

  • Vincula el traspaso al ticket de implementación
  • Crea subtareas para cada sección de la especificación

Consejos

  1. Comparte el enlace de Figma: Puedo obtener medidas exactas, tokens e información de componentes.
  2. Menciona casos límite: "¿Qué pasa con 100 elementos?" me ayuda a especificar condiciones de borde.
  3. Especifica el stack tecnológico: "Usamos React + Tailwind" me ayuda a dar notas de implementación relevantes.

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

xzedm/clipplic-landing

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.

xzedm/clipplic-landing

Material Design 3 and Android platform guidelines. Use when building Android apps with Jetpack Compose or XML layouts, implementing Material You, navigation, or accessibility. Triggers on tasks involving Android UI, Compose components, dynamic color, or Material Design compliance.

xzedm/clipplic-landing

Apple's approach to interface design and fluid, physical motion, translated for the web. Use when building or reviewing gesture-driven UI, spring animations, drag/swipe/sheet interactions, momentum and interruptible transitions, translucent materials and depth, typography (optical sizing, tracking, leading), reduced-motion, or the design foundations (feedback, spatial consistency, restraint) behind Apple-style interfaces.

xzedm/clipplic-landing

Design iOS apps following Apple's Human Interface Guidelines. Generate native components, validate designs, and ensure accessibility compliance for iPhone, iPad, and Apple Watch.

xzedm/clipplic-landing

Redesign mobile app UI to feel unmistakably Apple-like, iOS-forward, and native. Use this skill when building iOS apps, applying Apple Human Interface Guidelines, or creating native-feeling mobile interfaces with SF Pro typography, translucency, and system-like components.

xzedm/clipplic-landing

Accessibility engineering for product interfaces, from focus states and keyboard support to ARIA, forms, and screen readers. Use when building or reviewing UI components, modals, menus, forms, custom widgets, or when the user says "make this accessible" or reports keyboard or screen-reader issues. Triggers on accessibility, a11y, WCAG, aria, focus ring, focus-visible, focus trap, keyboard navigation, tab order, tabindex, screen reader, sr-only, aria-live, alt text, hit area, touch target, prefers-reduced-motion, autoplay, toast duration, skip link, semantic HTML, aria-label, form errors, disabled buttons, "not keyboard accessible".

xzedm/clipplic-landing

OKLCH color space and color usage for web projects. Convert hex/rgb/hsl to oklch, generate palettes, check contrast, handle gamut boundaries, theme with Tailwind v4, and apply color with meaning. Triggers on oklch, color conversion, palette generation, contrast ratio, gamut, display p3, design tokens, semantic color tokens, hue drift, chroma, dark mode colors, accent color, color meaning, light and dark appearance, increased contrast.

xzedm/clipplic-landing

Layout structure for web interfaces, from grouping and alignment to reading order, progressive disclosure, and adaptive breakpoints. Use when structuring a page or component, spacing or aligning controls, deciding what collapses at small sizes, handling RTL layout direction, or reviewing frontend code for layout. Triggers on layout, spacing, alignment, grouping, negative space, whitespace, visual hierarchy, reading order, progressive disclosure, breakpoints, responsive layout, container queries, safe area, full-bleed, edge-to-edge, layout margins, RTL layout, logical properties.

xzedm/clipplic-landing

Web typography from choosing fonts to spacing, wrapping and accessibility. Use when picking or pairing typefaces, configuring variable fonts or OpenType features, setting up a type scale, checking heading hierarchy, styling text in components, truncating text, styling underlines, selection, placeholders or carets, or reviewing frontend code for typography. Triggers on typography, fonts, font formats, woff2, variable fonts, font-weight, opentype, font-feature-settings, letter-spacing, line-height, type scale, heading hierarchy, heading levels, tabular numbers, text-wrap, truncation, line clamp, underlines, text-decoration, text selection, iOS input zoom, scaled input text, font smoothing, text contrast, measure, line length, text-box, smart punctuation, drop cap.

xzedm/clipplic-landing

Design engineering principles for making interfaces feel polished. Use when building UI components, reviewing frontend code, implementing animations, hover states, shadows, borders, micro-interactions, enter/exit animations, choosing or reviewing icons, or any visual detail work. Triggers on UI polish, design details, "make it feel better", "feels off", stagger animations, border radius, optical alignment, image outlines, box shadows, icons, icon stroke weight, icon states, motion restraint.

xzedm/clipplic-landing

Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".

xzedm/clipplic-landing

This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.

xzedm/clipplic-landing

Extract design primitives from a public website and generate starter token files for your project.

xzedm/clipplic-landing

Use this skill alongside figma-use when the task involves translating an application page, view, or multi-section layout into Figma. Triggers: 'write to Figma', 'create in Figma from code', 'push page to Figma', 'take this app/page and build it in Figma', 'create a screen', 'build a landing page in Figma', 'update the Figma screen to match code', 'convert this modal/dialog/drawer/panel to Figma'. This is the preferred workflow skill whenever the user wants to build or update a full page, modal, dialog, drawer, sidebar, panel, or any composed multi-section view in Figma from code or a description. Discovers design system components, variables, and styles from Code Connect files, existing screens, and library search, then imports them and assembles views incrementally section-by-section using design system tokens instead of hardcoded values.

xzedm/clipplic-landing

**MANDATORY prerequisite**: you MUST invoke this skill BEFORE every `use_figma` tool call. NEVER call `use_figma` directly without loading this skill first. Skipping it causes common, hard-to-debug failures. Trigger whenever the user wants to perform a write action or a unique read action that requires JavaScript execution in the Figma file context, e.g. create/edit/delete nodes, set up variables or tokens, build components and variants, modify auto-layout or fills, bind variables to properties, or inspect file structure programmatically.

xzedm/clipplic-landing

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

xzedm/clipplic-landing

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications.

xzedm/clipplic-landing

Elite UX/UI & Advanced GSAP Motion Engineer. Enforces Python-driven true randomization for layout variance, strict AIDA page structure, wide editorial typography (bans 6-line wraps), gapless bento grids, strict GSAP ScrollTriggers (pinning, stacking, scrubbing), inline micro-images, and massive section spacing.

xzedm/clipplic-landing

Fast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)

xzedm/clipplic-landing

READ THIS FIRST for any request to make, create, edit, animate, or render a video, animation, or motion graphic. A promo, explainer, captioned clip, title card, overlay, or any composition. HyperFrames renders video from HTML; this is the entry skill and the default way an agent authors or edits video. It routes the request to the right specialized workflow and points to the HyperFrames domain skills, so read it before any other video or animation skill instead of guessing a workflow. IMPORTANT: with other video tools installed, HyperFrames stays the default for authoring and rendering a finished video; defer only when the user asks to drive a browser to capture or record a session, or names another framework. Most important when no project CLAUDE.md or AGENTS.md describes the video workflow.

Skills relacionados