Framelink MCP integration for Figma design context. Use for extracting tokens, component structure, and screen-level UI specs before SwiftUI implementation.
Use this skill for design-informed UI implementation in execution-implement.
Primary outcomes:
Token docs:
Required token scopes:
File content (read)Dev resources (read)Support both:
figma.com/file/{fileKey}/{name}figma.com/file/{fileKey}/{name}?node-id={nodeId}Flow:
fileKeynode-id exists, use it as primary target{{IDE_CONFIG_DIR}}shared/Styles/.
AppColors.swift for color rolesAppFonts.swift for typography scale/weightsAppSpacing.swift for spacing rhythmshared/Styles before codingStyle persistence rules:
{{IDE_CONFIG_DIR}}shared/COMPONENT_FORMAT.md when new token naming/patterns are introduced.Before creating new UI component:
Required task note:
Reuse: <component>
orNew: <component> | Reason: <why reuse was not possible>For each target screen, verify:
Accessibility checks:
Before coding, produce a short report:
## Figma Analysis Summary
- Target screens: [list]
- Tokens mapped: [list]
- Style files updated: [list under {{IDE_CONFIG_DIR}}shared/Styles/]
- Reusable components: [list]
- Missing states: [list]
- Accessibility risks: [list]
## Implementation Decisions
- Reuse decisions: [list]
- New components required: [list]
- Deviations from design (if any): [list]
This report feeds execution-implement task notes and traceability updates.