← ClaudeAtlas

import-figma-assetslisted

Import Figma assets into Apple Xcode projects while preserving vector artwork and generating complete 1x/2x/3x raster image sets. Use when implementing iOS, iPadOS, macOS, watchOS, tvOS, or visionOS UI from a Figma URL or node ID; downloading PNG, SVG, or PDF resources from Figma; creating or updating Assets.xcassets image sets; or wiring Figma artwork into SwiftUI, UIKit, or AppKit code.
gwair1989/figma-full-cycle · ★ 0 · AI & Automation · score 67
Install: claude install-skill gwair1989/figma-full-cycle
# Import Figma Assets Import production artwork from an exact Figma node into an existing Xcode asset catalog. Preserve vectors as vectors; derive raster variants from one verified 3x PNG. ## Follow the required flow 1. Load the Figma workflow skill your agent's catalog actually registers before calling Figma tools, and follow its required context-first workflow. Take the name from the live catalog, not from memory; inside `figma-full-cycle`, reuse the `design-to-code-workflow` binding already recorded in the capability ledger. Tool names below (`get_design_context`, `get_screenshot`, `download_assets`) are the Figma MCP defaults — use the actual registered names when the server prefixes or renames them. 2. Inspect the repository before downloading anything: - Locate the relevant `.xcodeproj` or `.xcworkspace`, target, platform, and existing `Assets.xcassets` catalogs. - Follow the project's existing asset naming, rendering-mode, namespace, and code-access conventions. - Search all catalogs assigned to the target for the intended qualified asset name. Treat namespace-providing groups as part of the runtime name. 3. Fetch the exact Figma node with `get_design_context`. If truncated, fetch metadata and then the smallest exact node. Fetch `get_screenshot` before downloading assets. 4. Classify each production asset as vector, raster, or mixed before exporting it. 5. Download only the exact assets used by the implementation. Never use the inspection screenshot as a pr