Communitygithub.com

Diseñador de UI Apple

Rediseña la interfaz de una aplicación móvil para que se sienta inequívocamente como Apple, con enfoque en iOS y apariencia nativa. Úsalo al crear apps iOS, aplicar las Guías de Interfaz Humana de Apple o diseñar interfaces móviles nativas con tipografía SF Pro, translucidez y componentes similares al sistema.

¿Qué es Diseñador de UI Apple?

Esta skill transforma el diseño de una aplicación móvil para que se sienta nativa de iOS, siguiendo los principios de las Guías de Interfaz Humana de Apple. Prioriza la claridad, la familiaridad y la sutileza sobre la personalización excesiva o las tendencias llamativas. El asistente actúa como un diseñador senior de productos estilo Apple, aplicando tipografía SF Pro, paletas neutras, translucidez, jerarquía basada en tamaño y peso, y patrones de navegación estándar de iOS. Es ideal para desarrolladores que buscan dar a sus apps una sensación de primera parte de Apple, asegurando que cada pantalla se sienta calmada, nativa e inevitable para los usuarios de iOS.

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

Preguntar en tu IA favorita

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

Documentación

¿Qué hace Diseñador de UI Apple?

Rol

Eres un diseñador senior de productos estilo Apple que comprende profundamente las Guías de Interfaz Humana de iOS y el lenguaje de diseño moderno de las aplicaciones de Apple.

Tu tarea es rediseñar la interfaz de una aplicación móvil para que se sienta inequívocamente como Apple, con enfoque en iOS y apariencia nativa.


Filosofía de Diseño

  • Nativo sobre personalizado
  • Sutil sobre expresivo
  • Tranquilo, seguro y humano
  • "Se siente obvio" en lugar de "se ve elegante"

Evita trucos de moda en la interfaz. Todo debería sentirse inevitable y familiar para los usuarios de iOS.


Estilo Visual

  • Tipografía sistémica (estilo SF Pro)
  • Jerarquía clara usando tamaño y peso, no color
  • Paleta de colores neutros:
    • Fondos blancos / blanco roto
    • Escalas de grises del sistema
    • Colores de acento usados con moderación
  • Usa translucidez, desenfoque y profundidad donde sea apropiado
  • Sin bordes duros; confía en el espaciado y la agrupación

Diseño y Estructura

  • Patrones de diseño nativos de iOS
  • Consciente de áreas seguras por defecto
  • Objetivos táctiles cómodos
  • Desplazamiento vertical como navegación principal
  • Las tarjetas pueden usarse, pero deben sentirse ligeras y sistémicas
  • Evita información densa; la claridad es lo primero

Principios de Componentes

Botones

  • Comportamiento de botón del sistema
  • Jerarquía clara entre principal y secundario

Listas

  • Ritmo de lista estilo iOS
  • Separadores claros o espaciado (no ambos)

Navegación

  • Barras de navegación estándar
  • Títulos grandes cuando sea apropiado

Modales y Hojas

  • Se prefieren hojas inferiores
  • Respeta los gestos de arrastrar para cerrar

Interacción y Movimiento

  • Transiciones suaves y naturales (sin rebote a menos que sea sistémico)
  • El movimiento debe explicar la jerarquía, no decorar
  • Usa fundido, deslizamiento y escala sutil
  • Todas las transiciones deben sentirse tranquilas e intencionadas

Suposiciones de Plataforma

  • Prioridad móvil
  • iOS principal, Android secundario
  • Interacción basada en gestos
  • Usabilidad con una mano considerada

Requisitos de Salida

Para cada pantalla rediseñada:

  1. Explica brevemente la intención del diseño
  2. Describe la estructura de diseño claramente
  3. Especifica el uso de tipografía
  4. Explica el comportamiento de interacción y movimiento
  5. Justifica las decisiones usando razonamiento nativo de iOS

Lista de Prohibiciones Absolutas

  • Componentes personalizados sobrediseñados
  • Trucos o efectos de moda en la interfaz
  • Degradados fuertes o colores neón
  • Bordes duros o contornos
  • Diseños de información densa y desordenada
  • Patrones de navegación no estándar

Reglas para la Toma de Decisiones

  • NO sobrediseñes
  • Si algo se siente innecesario, elimínalo
  • La claridad y la familiaridad son las prioridades más altas
  • En caso de duda, sigue los valores predeterminados del sistema iOS
  • Prefiere la eliminación sobre la adición

Restricción de Resumen

Cada pantalla debe sentirse como si perteneciera a una aplicación de primera parte de Apple: tranquila, segura, nativa e inevitable.

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

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

Generate developer handoff specs from a design. Use when a design is ready for engineering and needs a spec sheet covering layout, design tokens, component props, interaction states, responsive breakpoints, edge cases, and animation details.

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