figma-swiftui

por openai

Traducción SwiftUI ↔ Figma. Úsalo siempre que el usuario mencione Swift, SwiftUI, iOS, iPhone o iPad — en CUALQUIER dirección — traduciendo un diseño de Figma a…

npx skills add https://github.com/openai/plugins --skill figma-swiftui

Figma ↔ SwiftUI

Translation between Figma designs and SwiftUI code, both directions. This file is a router — actual guidance lives in the references below.

Pick the direction

DirectionTriggerReference
Design → codeUser wants SwiftUI in their iOS project from a Figma file/framereferences/design-to-code.md
Code → designUser wants to push SwiftUI views / screens / tokens into a Figma filereferences/code-to-design.md

If the request is ambiguous — a Figma URL and .swift files both present, no verb makes it clear — ask the user which direction before loading a reference.

Shared context (applies to both directions)

These points hold regardless of direction; the direction-specific references assume them.

  1. get_design_context is the read tool for Figma. Pass clientLanguages: "swift" and clientFrameworks: "swiftui" so the response is framed as Swift. URL → tool args: figma.com/design/:fileKey/:fileName?node-id=:nodeId → use fileKey, replace - with : in nodeId. For figma.com/design/:fileKey/branch/:branchKey/:fileName, use branchKey as fileKey.
  2. The React+Tailwind in get_design_context output is a structural reference, not a literal source. It approximates the visual. Never transliterate position: absolute / pixel frames / mix-blend-mode stacks into SwiftUI or into Figma — the screenshot is the source of truth in both directions.
  3. iOS HIG semantic colors are tokens, not hex. var(--backgrounds/primary, …), var(--labels/secondary, …), var(--separators/non-opaque, …) etc. map to Color(.systemBackground), Color.secondary, Color(.separator) in SwiftUI, and to variables in a semantic collection in Figma. Keep the mapping; drop the literal RGBA.
  4. SF Symbols round-trip by name in both directions — never by codepoint. Design → code: get_design_context substitutes Figma's SF Symbol glyph runs back into <SFSymbol>{Image(systemName: "...")}</SFSymbol> wrappers in the response. Use those names verbatim. Code → design: call figma.util.getSfSymbolCharacter(name) inside use_figma to convert a symbol name to the matching character — never look up codepoints by hand.
  5. Recognize the underlying iOS pattern, not the literal node / view name. The same patterns recur in both directions: large title + back chevron + trailing action = NavigationStack chrome; bottom row of icon+label pairs = TabView; repeating same-height rows with leading/trailing chrome = List. Match those system patterns rather than rebuilding them from primitives.
  6. For code → design, use_figma is the API. Always load figma-use before any use_figma call. If the task involves building a full screen, also load figma-generate-design; if it involves building components or a design system, also load figma-generate-library.

References

DocWhen to load
references/design-to-code.mdTranslating a Figma design / frame into SwiftUI
references/code-to-design.mdPushing SwiftUI views / screens / tokens into Figma

Más skills de openai

release
openai
Realizar un lanzamiento de Symphony incrementando la versión confirmada, integrándola, etiquetando el commit fusionado y verificando el flujo de trabajo de lanzamiento de Burrito. Usar cuando se solicite…
signing-entitlements
openai
Inspeccionar problemas de firma, entitlements, runtime reforzado y Gatekeeper en aplicaciones de macOS. Usar cuando se solicite diagnosticar fallos de firma de código, entitlements faltantes,…
building-ai-agent-on-cloudflare
openai
Crea agentes de IA en Cloudflare usando el Agents SDK con gestión de estado, WebSockets en tiempo real, tareas programadas, integración de herramientas y chat…
epigraphdb-skill
openai
Envía solicitudes compactas a la API de EpiGraphDB para ontología, literatura, MR, genes-fármacos y evidencia de vías de soporte. Úsalo cuando un usuario desee resúmenes concisos de EpiGraphDB.
runtime-behavior-probe
openai
Planificar y ejecutar investigaciones de comportamiento en tiempo de ejecución con scripts de sonda temporales, matrices de validación, controles de estado e informes centrados en hallazgos. Usar solo cuando…
deep-security-scan
openai
Úsalo cuando el usuario solicite un escaneo de seguridad de Codex profundo, exhaustivo, de múltiples pasadas o que reduzca la varianza, en todo el repositorio o en una ruta específica. Ejecuta pasadas independientes repetidas…
define-security-policy
openai
Definir, revisar o actualizar la guía de SECURITY.md para un repositorio o componente. Úselo cuando el usuario quiera aclarar qué debe revisar Codex Security, qué está fuera de…
validation
openai
Usar cuando Codex ya está en la fase de validación de un escaneo de seguridad o el usuario solicita explícitamente determinar si uno o más posibles hallazgos de seguridad…