Developers
This section is for engineers who configure and run Figmage. If you’re new here, start with Getting Started, or read Why Figmage for the bigger picture.
What this track covers
Section titled “What this track covers”Use this track when you need to install the CLI, connect to Figma, write figmage.config.js, sync
tokens, shape generated output, or automate Figmage in CI.
This track does not cover how to design the source library in Figma. For naming, publishing, styles, components, and designer handoff, use the designer docs.
| Designers prepare | Developers configure |
|---|---|
| Published styles and components | Access token and file ID |
| Stable names and source frames | figmage.config.js token sets |
| Handoff notes for changes | Generated files consumed by the app |
Reading path
Section titled “Reading path”- Quickstart — install, configure, and run your first sync.
- Install and Auth — the full setup, access tokens, and file IDs.
- Configuration — every
figmage.config.jsoption. - Token Types — everything Figmage can generate.
- Spritesheets — why and how to generate SVG sprite sheets for your icons
- CLI — the complete command reference.
- CI — run Figmage safely in automated jobs.
- Recipes — copyable patterns for common token setups.
- Troubleshooting — common setup and sync failures.
- Migrating from v1 — upgrade from the old tokenize/codegen flow.