figma-swiftui

par figma

Traduction SwiftUI ↔ Figma. À utiliser chaque fois que l'utilisateur mentionne Swift, SwiftUI, iOS, iPhone ou iPad — dans les DEUX sens — pour traduire un design Figma en…

npx skills add https://github.com/figma/mcp-server-guide --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

Plus de skills de figma

video-interaction-mapper
figma
Cette compétence doit être utilisée lorsque l'utilisateur demande d'analyser un enregistrement d'écran d'interface utilisateur et de mapper les états d'interaction dans Figma. Déclencheur pour des demandes telles que "mettre la vidéo…
official
figma-code-connect
figma
Crée et maintient les fichiers de modèle Figma Code Connect qui associent les composants Figma à des extraits de code. À utiliser lorsque l'utilisateur mentionne Code Connect, composant Figma…
official
figma-implement-motion
figma
Traduit les mouvements et animations Figma en code d'application prêt pour la production. À utiliser lors de l'implémentation d'animations/mouvements à partir d'un design Figma — l'utilisateur mentionne…
official
figma-use-motion
figma
Motion / animation context for the `use_figma` MCP tool — animating Figma nodes via manual keyframes, animation styles, easing, and timeline duration. Load…
official
figma-use-slides
figma
Cette compétence aide les agents à utiliser l'outil MCP use_figma de Figma dans le contexte des diapositives. Peut être utilisée conjointement avec figma-use qui fournit un contexte fondamental pour utiliser le…
official
figma-use-figjam
figma
Cette compétence aide les agents à utiliser l'outil MCP use_figma de Figma dans le contexte FigJam. Peut être utilisée conjointement avec figma-use qui fournit le contexte fondamental pour utiliser le…
official
code-connect-components
figma
Establish bidirectional links between Figma design components and code implementations using Code Connect. Requires Figma MCP server connection and published components on Organization or Enterprise plans Automatically identifies unmapped components in Figma selections, then scans your codebase for matching code components by name, structure, and props Presents matched components to you for review before creating mappings, allowing selective acceptance or rejection Supports multiple...
official
create-design-system-rules
figma
Custom design system rules for consistent Figma-to-code implementation across your project. Generates project-specific conventions for component organization, styling, design tokens, and asset handling that guide AI agents to produce consistent code Supports three rule file formats: CLAUDE.md for Claude Code, AGENTS.md for Codex CLI, and .cursor/rules/figma-design-system.mdc for Cursor Requires Figma MCP server connection and codebase analysis to discover existing patterns before rule...
official