Figmagic is the missing piece between DevOps and design: Generate design tokens, export graphics, and extract design token-driven React components from your Figma documents.
🏕️ Kumbaya, friends. Figmagic automates the world into a better place, but does not attempt to completely remove designers or developers: It just aims to move them closer, while eliminating most of the tedious busywork that has grown around front-end development.
Built initially as an internal handoff tool for Humblebee.
Interested in understanding the vision for Figmagic? Then you should read the product vision.
You can also read this README in the following languages:
See more on the version 4.5.0 release page.
When files (and Elements) are written to disk these now use a PascalCase format. This is partly because recent versions have also started to accept dashes and underscores in names, for example for Elements and tokens named things like my-design-system-button, which would be transformed into MyDesignSystemButton.
To ensure that files and imports have usable and working names, the decision was made to add a string transformer to the file output stage.
This may break stuff on your end if you were dependent on the previous, non-transformed format.
Previous versions in the 4.0 series have been using trash to handle files that need to be replaced. In 4.3.0 this is no longer the case.
Any deleted files are now permanently destroyed by the Node native fs module.
Versions 4.3.0 and 4.3.1 used a flaky dual-mode, configurable pattern where you could use either a "hard" or "soft" delete mode (soft deletes meaning placing files in a local trash folder). This is NOT supported and intended from 4.3.2 and forward as that was too buggy.
Please note: Figmagic requires that your document structure follows the conventions in this document; a full setup can be seen in the template at https://www.figma.com/community/file/821094451476848226/Figmagic-%E2%80%94-Design-System-for-Tokens.
Figmagic is compiled from Typescript to ES6, so you should have Node 12 or later (Node 14 and newer recommended) for it to work on your machine.
Figmagic is a very straightforward, super-flexible command-line tool that helps you do three things well:
Outputting and using design tokens aids in designing with a structured approach. These tokens are completely platform agnostic when output into JSON, or for most web developers, more readily useable in various supported flavors of JavaScript (TS, JS, MJS). It's web-oriented but works well with React Native too.
A basic set of tokens can look like this:
const tokens = {
colors: {
blue: 'rgba(20, 20, 255, 1)',
warmWhite: 'rgba(240, 240, 240, 1)'
},
spacing: {
small: '1rem',
medium: '1.5rem'
}
};You use these tokens like so, color: ${colors.blue};, to shape and specify your coded components, web sites, apps, and what have you, instead of hard-coding every single value.
This way, you decouple implementation from data. You can now easily drive changes as design choices through Figma instead of as code changes.
Say goodbye to ever manually exporting graphics from Figma again. Grab your graphics as PNG, SVG, as React components with inlined SVG, or as objects that export all graphics from a single file.
Figmagic also allows you to generate React components from Figma components that follow a specific formal structure. It's best at fairly low-level components that you can piece together to make more complex organisms on your own. You can significantly cut down on boilerplate churn and scaffolding time with Figmagic.
And, no, the code actually doesn't suck! This was my own biggest gripe with services promising this functionality, so I knew it had to be good, or at least tolerable. Therefore Figmagic supports things like actually using your own tokens (so we can cut down on hard-coded garbage, unless matches aren't found) and you can completely customize the number of related generated files.
While not perfect, it's definitely better than many things I've seen, made by big companies. All of this is explained later here in the docs.
Here are a few reasons you'd want to use Figmagic rather than anything similar:
- In Figmagic, design tokens are a first-class concept since day 1
- Figmagic is designer-driven, since Figma is seen as the source of truth
- Figmagic is automatable and very lightweight (~45kb compressed), with no external dependencies
- Figmagic is developer-friendly and makes very few assumptions on your use and/or setup and supports a range of output formats plus that it's extensible through custom templates if you need something completely different
- Figmagic is open-sourced under the MIT license and has a long track record of very short implementation cycles for new features/fixes
- Generated React components bind to any token values you've defined so these are equally useful as starter code or as code you continually output
The Figmagic developer docs are auto-generated on every push and can be found at the dedicated documentation site.
For deeper information pertaining to Figmagic Elements and syncing them, see the dedicated README page.
In addition to Figmagic itself, there are several more repos/projects around Figmagic:
figmagic-example: This repository is a demo of Figmagic. In this project you're going to see how a project running Webpack, React and Styled Components might use tokens. See more below!figmagic-action: Figmagic GitHub action. Use Figmagic to retrieve tokens, graphics, and/or React components from a Figma document.demo-figmagic-action: Demo of the above GitHub action.figma-plugin-continuous-design: Continuous Design is a Figma plugin that lets you run GitHub Actions, Bitbucket Pipelines, and Azure DevOps Pipelines from Figma.automator-figmagic: Mac OS X Automator service for Figmagic.
An example project—using React, Styled Components and Storybook—is available at https://github.com/mikaelvesavuori/figmagic-example.
Note that this demo is not meant to fully style and do all of the things in the Figma document. I wanted to straddle a middle-of-the-road solution where I did the least work possible to get it working with React and style only a few of the most obvious and helpful elements, like setting disabled state on the button and checkbox.
Figmagic Example Demo: On the left is a big Figma component assembled of a number of "Elements", Figmagic-compliant components that can be output into code. On the right is the React-composed version of those after just a few minutes of coding and closing elements correctly.
Run npm install -g figmagic or yarn global add figmagic.
Local usage is possible by installing Figmagic as a developer dependency (under devDependencies) with npm install figmagic -D or yarn add figmagic -D, then using a script pointing to the local version, like so:
"scripts": {
"figmagic": "npx figmagic"
}
Figmagic can be run without any configuration. You will always need to specify your Figma API token and Figma document ID, though! However, it's highly recommended to add a configuration: it's easy and gives you a ton of possibilities to optimize for your own needs.
Run figmagic init to initialize a basic configuration file, either named figmagic.json or .figmagicrc file. As long as you provide your Figma token and document ID/URL, the new generated file is ready to use for Element Sync which can only be done if your configuration points to valid code generation templates (which the generated one does). You'll see that the config will point templates.templatePath{Graphic|React|Styled|Storybook} to ./node_modules/figmagic/templates/{graphic|react|styled|story}. Read more under the Configuration file section.
First of all, get your Figma API token and Figma URL:
- Get your file ID by right-clicking your Figma tab inside of the app and click
Copy Link—the first, long junk-looking bit is the ID. - For more on API keys, go to Figma's developer docs.
Pass in your Figma API token and Figma URL by either:
- Stepping into your project directory (where you want Figmagic to run), and add or replace FIGMA_URL and FIGMA_TOKEN in a
.envfile with your own file ID (i.e. similar to821094451476848226) or full Figma URL (i.e. similar tohttps://www.figma.com/file/821094451476848226/Figmagic-%E2%80%94-Design-System-template-4.0) and API token key. - Passing in API token and URL through the CLI, like this
figmagic --token {TOKEN} --url {URL}(substitute curly braces for your actual values) - Setting them in
figmagic.json/.figmagicrcundertokenandurl. This is discouraged since you will display these values in clear text and you probably don't want that.
Then:
- Run
figmagic - You should now have a folder with the raw JSON dump (default:
/.figmagic) and a folder with tokens (default:/tokens) in the root
Folder names below follow their default naming. The naming is possible to change via configuration.
.figmagicwill contain the extracted JSON retrieved from Figma's APItokenswill contain the token fileselementswill contain the generated codegraphicswill contain graphics
For a more complete description of the code structure, see the Code structure section.
Go to https://www.figma.com/community/file/821094451476848226/Figmagic-%E2%80%94-Design-System-for-Tokens and make your own copy. Go at it by using the document ID as the FIGMA_URL or start copying in your own work.
Your structure needs to correspond to the following:
- A Page needs to exist, called
Design tokens. Without this page you can't really do much with Figmagic. - Further, inside the
Design tokenspage, frames need to exist. You can have any number of supported token frame. For starters, name themColors,Font sizes,Font families,Font weights,Line heights, andSpacing– exact casing is not important, however the spelling is important! For a full list of token types, see the types of design tokens Figmagic can extract. - All items on a page need to be contained within one or more frames.
- Want element syncing? Then create an "Elements" page and place any components there. For the generation to work correctly, you need to stay within the limits specified above.
See a template design system at https://www.figma.com/community/file/821094451476848226/Figmagic-%E2%80%94-Design-System-template-4.0. Feel free to simply copy-paste it or base your own work around it.
Note: Refer to the document structure in the image below and in the template linked above.
How a Figmagic project could be structured in regards to tokens, if you want to support all currently available token types.
Design tokens are the abstract and shared elements from which your design system is built.
Design tokens express any of the individual values that you build from, such as colors, spacing, and typographic features.
Tokens offer a form of “contract” between a designer’s intent and its fulfillment by developers. This means that both sides agree to treat the individual parts of a complete design through the tokens that represent those values. As a format, they are super easy to read and understand and are adaptable for consumption by many types of systems or applications. That’s very important as you start doing cross-platform apps and things like that.
Tokens ensure that values are not magic numbers or ”just picked at random”. This makes communication precise and effortless. Creating actual code for components, even complex ones, also becomes a lot less of a bore, since what you are doing is just pointing stuff like padding, Z indices, and anything else to their token representations.
However: You may still want to add written guidance for usage. It’s just that the tokens should be able to be consumed without understanding anything specific about them.
You should bind tokens to Figma styles whenever and wherever possible to simplify your own design work, but make sure that those are also represented in the Tokens page, as this page is where a developer will pick up tokens with Figmagic.
You can currently extract design tokens for:
- Colors (including linear and radial gradients, though note: linear gradients which are not using straight angles will get an incorrect calculation)
- Font Sizes
- Spacing
- Font Weights
- Line Heights
- Font Families
- Letter Spacings
- Z Indices
- Radii
- Border Widths
- Shadows (currently supports single/multiple Drop Shadows; see caveat below)
- Opacities
- Durations (for animations)
- Delays (for animations)
- Easing functions (for animations)
- Media Queries
A typical use-case for the generated documents is to feed the extracted values into CSS systems that support external values (such as Styled Components, Emotion, Styled System, any other CSS-in-JS libraries, or maybe even Sass).
From alehar9320 commenting on issue 111:
Figma calls everything Drop-shadow, while translating the design into box-shadow or drop-shadow CSS dependent upon whether it's a ~ shape or a vector graphic. See blog post from the Figma developer who built the feature.
This means that if Figmagic is used to define shadow tokens, it should be recommended to only have one drop-shadow definition per rectangle. To maintain compatibility with both drop-shadow and box-shadow CSS. The exception would be if there is a clear distinction between tokens to be used with box-shadow and drop-shadow. As drop-shadow can only accept a single shadow parameter. Any token that has two values will simply be incompatible with drop-shadow.
Figma styles became publicly available in June 2018 and are incredibly valuable for designers to create single-sources-of-truth when it comes to design values (tokens). When using Figmagic though, the thinking and usage is a bit different from how Figma styles work.
A Figma style is multidimensional: It contains any number of properties wrapped into one style, acting as kind of a package. This is handy in a design environment and is practical from a user standpoint. The user doesn't have to think too hard about storing "redundant" values that are the same in another component, such as N number of units for line height: They are all taken care of.
Figmagic instead expresses tokens as instances of every individual value, thus being unidimensional – meaning they store only one value per item. Examples could be sets of line heights, font weights, or font sizes, each one individually specified. What this entails for they developer and designer, is that values can be used and mixed as pleased in any number of contexts, not becoming bound to one specific context such as a certain kind of heading. For a developer this is good because we would rather just map out the definitive values for something, onto a component (a "context" so to speak).
Because of this difference, the appropriate way to structure a Figmagic-compatible Figma design document is to display one or more items/tokens in the respective frames that correspond to the accepted token types (line height, font size...) where each item has only one key property that's changed in-between them (such as one text using size 48, the next using size 40...), since those items are what Figmagic loops through when creating your code tokens.
One of the major deviations from this principle is "Fonts" where you can specify more properties than one. However, then those need to individually match other typographical tokens you might have, such as line heights.
The "Heading L" font token is composed of values that are also represented in the "lesser" uni-dimensional tokens: displayed here are "Line Height S" (135% line height), "H1" (size 48), and "Font Bold" (Bold font style). Setting this font as a Figma Style will make your life as a designer much easier as your apply the text style to things. Auto-generating code with Figmagic will also work just fine, since the individual values are respected.
Whatever suits you! As long as you remember that what Figmagic fetches are those single (unidimensional) values from each design item/token it should all work. I've seen that Figma styles make the "contract" between tokens and their day-to-day workflow with designers a lot easier. Again though, Figmagic does not use those values; think of them as a convenient glue.
By default this is turned on. You will need to have a page named "Design tokens", where your tokens lay within named frames.
Tokens are the "bread and butter" of Figmagic. Without tokens, Figmagic cannot create elements. And even without elements, tokens provide the core experience to help you run a competent design system with code.
In case you want to skip generating tokens for a given frame, you can just add a leading underscore to the frame name. You can also skip individual items by naming them ignore or adding a leading underscore.
This is activated by default, but it's now possible to deactivate it if you have very specific reasons to do so.
By default this is turned off. Pass in --syncGraphics as a flag to sync them or enable that in your configuration file. You will need to have a page named "Graphics", where your components lay directly on the artboard.
Graphics can be exported in multiple formats with Figmagic. Instead of doing manual hand-overs, just tell your developer(s) that there have been updates to the graphics and let them pull the latest versions from your Figma document.
After version 4.4.6, you can either place graphics as Figma components right into the Graphics page, or nest them into frames.
Again, please look at the template at https://www.figma.com/community/file/821094451476848226/Figmagic-%E2%80%94-Design-System-for-Tokens for reference.
This is also turned off by default. Pass in --syncElements or enable it in your configuration file to generate code from your Figma components.
Upcoming versions of Figmagic may attempt to support Figma Variants, but that will have to be publicly released first, and then vetted against what Figmagic can generate before I commit to supporting that model. Until then, the existing mental model of "Elements" will continue to be used.
Elements are named so because they are primarily meant to help scaffold anything that maps to standard HTML elements like input, button, h1, and form. With scaffolding we mean that these elements can be generated as code in a shape that is fitting for continued development. Elements are a good entry-point both for design and for code generation, since they are relatively simple and as a concept map to HTML, which in turn is based on tags ("elements").
Elements are generated by parsing your structured Figma components into either "flat" or "nested" varieties. Any values, say a height of 48px and a specific blue color, will try to be derived from your relevant tokens. Therefore, without tokens, elements cannot be generated! In this example, maybe the height will map to a spacing token that uses 48px (mapping to 3rem where 3 x 16 = 48, with 16 being the root REM value) and the color might be mapped to a color in your color tokens.
If you need more information and guidance on this, see the dedicated documentation section at Figmagic Element Sync.
There are several ways in which you can provide Figmagic with knowledge about how you want it to parse your tokens. You can combine them, but beware of the below prioritization chart (from lowest to highest):
- User-provided configuration from
figmagic.json/.figmagicrcfile - Environment variables (also loaded from
.envfile) - Command-line arguments and flags
If possible, stick to one way of providing settings.
Non-provided values will fall back to defaults outlined in bin/entities/Config/baseConfig.ts.
You can use a JSON-formated configuration file at the root of a project to use its settings. Figmagic will pick up the path by assessing the current working directory and looking for either a figmagic.json or .figmagicrc file there. If it finds it, it will use it.
An example file is provided in Figmagic—you can find it in the root of the project. The file is named figmagicrc, just add the leading dot and place the file in your own project folder to use it. To use it as JSON, add json as the file ending.
Since this is a configuration file, you'll need to be careful to write it correctly or you may end up with failures and errors.
Below is a complete set of what you can configure, together with the defaults.
{
"debugMode": false,
"camelizeTokenNames": true,
"borderWidthUnit": "px",
"fontUnit": "rem",
"letterSpacingUnit": "em",
"lineHeightUnit": "unitless",
"opacitiesUnit": "float",
"durationUnit": "s",
"radiusUnit": "px",
"shadowUnit": "px",
"figmaData": "figma.json",
"figmagicFolder": ".figmagic",
"outputFolderElements": "elements",
"outputFolderGraphics": "graphics",
"outputFolderTokens": "tokens",
"outputFormatColors": "rgba",
"outputFormatCss": "ts",
"outputFormatDescription": "md",
"outputFormatElements": "tsx",
"outputFormatGraphics": "svg",
"outputFormatStorybook": "js",
"outputFormatTokens": "ts",
"outputGraphicElements": false,
"outputGraphicElementsMap": false,
"outputScaleGraphics": 1,
"outputDataTypeToken": null,
"overwrite": {
"css": false,
"description": false,
"graphic": false,
"react": false,
"storybook": false,
"styled": false
},
"recompileLocal": false,
"refreshType": "soft",
"remSize": 16,
"skipFileGeneration": {
"forceUpdate": true,
"skipCss": false,
"skipDescription": false,
"skipReact": false,
"skipStorybook": false,
"skipStyled": false
},
"spacingUnit": "rem",
"syncElements": false,
"syncGraphics": false,
"syncTokens": true,
"templates": {
"templatePathGraphic": "templates/graphic",
"templatePathReact": "templates/react",
"templatePathStorybook": "templates/story",
"templatePathStyled": "templates/styled"
},
"token": "",
"unitlessPrecision": 2,
"url": "",
"usePostscriptFontNames": false,
"useLiteralFontFamilies": false,
"versionName": null
};Run these in your command line environment of choice.
figmagic [--debug | -d]
Default: false.
figmagic [--noCamelizeTokenNames | -cml]
Default: true.
The Figmagic default has always been to camel-case ("camelize") token names, so that for example kebab-case-word becomes kebabCaseWord.
From version 4.3.7, you can now also opt-in to have no transforms applied to your token name. The name will still be sanitized, and only dashes and underscores will be valid special characters, but this will be something you'd want to use if casing is very important to you. An example could be $my-design-system-error500 which would end up being my-design-system-error500.
figmagic [--borderWidthUnit | -bwu] [px|rem|em]
Default: px.
figmagic [--radiusUnit | -ru] [px|rem|em]
Default: px.
figmagic [--shadowUnit | -su] [px|rem|em]
Default: px.
figmagic [--fontUnit | -fu] [rem|em|px]
Default: rem.
figmagic [--letterSpacingUnit | -lsu] [em|px]
Default: em.
figmagic [--lineHeightUnit | -lhu] [unitless|em|px|rem]
Default: unitless.
figmagic [--opacitiesUnit | -ou] [float|percent]
Default: float.
figmagic [--durationUnit | -du] [s|ms]
Default: s.
figmagic [--spacingUnit | -s] [rem|em|px]
Default: rem.
figmagic [--outputFormatCss | -fc] [ts|mjs|js]
Default: ts.
figmagic [--outputFormatDesc | -fd] [md|txt]
Default: md.
figmagic [--outputFormatElements | -fe] [tsx|jsx|mjs|js]
Default: tsx.
figmagic [--outputFormatGraphics | -fg] [svg|png]
Default: svg.
figmagic [--outputFormatStorybook | -fs] [ts|js|mdx]
Default: js.
figmagic [--outputFormatTokens | -ft] [ts|mjs|js|json]
Default: ts.
figmagic [--outputFormatColors | -fcol] [hex|rgba]
Default: rgba.
This only applies to solid colors; gradients will still use RGBA colors.
Hex color support may potentially interfere with element generation and binding to tokens, since RGB(A) is the format that Figma itself uses, so there is a slight possibility of mismatches in the Figmagic binding process.
Note that hex colors will not use any alpha/transparency!
figmagic [--figmaData | -file] [filename]
Default: figma.json.
figmagic [--figmagicFolder | -base] [folder]
Default: .figmagic.
figmagic [--outputFolderElements | -elements] [folder]
Default: elements.
figmagic [--outputFolderGraphics | -graphics] [folder]
Default: graphics.
figmagic [--outputFolderTokens | -tokens] [folder]
Default: tokens.
figmagic [--outputGraphicElements | -oge]
Default: false.
figmagic [--outputGraphicElementsMap | -ogm]
Default: false.
figmagic [--outputScaleGraphics | -scale] [number]
Default: 1.
Note that from the CLI you must specify the scale size like 3x (or anything at the end, as long as it includes a letter at the end). This only applies to CLI configuration, and does not apply to other types of config, such as through figmagic.json or .figmagicrc.
figmagic [--outputDataTypeToken | -tokentype] [null | enum]
Default: null.
This is not currently possible to adjust from the CLI.
figmagic [--recompileLocal | -local]
Default: null, and will then be taken from local .env file if not explicitly passed in through the CLI.
figmagic [--remSize | -rem] [number]
Default: 16.
Note that from the CLI you must specify the REM size like 16p (or anything at the end, as long as it includes a letter at the end). This only applies to CLI configuration, and does not apply to other types of config, such as through figmagic.json or .figmagicrc.
figmagic [--forceUpdate | -force]
Default: true.
Forces all elements and file types to be regenerated.
figmagic [--skipCss | -nocss]
Default: false.
Skip creating CSS file when syncing elements.
figmagic [--skipDescription | -nodesc]
Default: false.
Skip creating Markdown file when syncing elements.
figmagic [--skipReact | -noreact]
Default: false.
Skip creating React file when syncing elements.
figmagic [--skipStorybook | -nostory]
Default: false.
Skip creating Storybook file when syncing elements.
figmagic [--skipStyled | -nostyled]
Default: false.
Skip creating Styled Components file when syncing elements.
figmagic [--syncElements | -se]
Default: false, and will then be taken from local .env file if not explicitly passed in through the CLI.
Use this when you want to sync elements in your "Elements" page in Figma.
figmagic [--syncGraphics | -sg]
Default: false, and will then be taken from local .env file if not explicitly passed in through the CLI.
Use this when you want to sync graphics in your "Graphics" page in Figma. Use the RC or configuration file to pass in options. Default format will be SVG.
figmagic [--syncTokens | -st]
Default: true, and will then be taken from local .env file if not explicitly passed in through the CLI.
Use this when you want to sync tokens in your "Design tokens" page in Figma. Use the RC configuration file to pass in options.
figmagic [--templatePathGraphic | -tpgraphic] [path]
Default: templates/graphic.
Your local figmagic.json or .figmagicrc file must have a block with templates.templatePathGraphic that specifies a valid path, such as ./node_modules/figmagic/templates/graphic.
figmagic [--templatePathReact | -tpreact] [path]
Default: templates/react.
Your local figmagic.json or .figmagicrc file must have a block with templates.templatePathReact that specifies a valid path, such as ./node_modules/figmagic/templates/react.
figmagic [--templatePathStorybook | -tpstory] [path]
Default: templates/story.
Your local figmagic.json or .figmagicrc file must have a block with templates.templatePathStory that specifies a valid path, such as ./node_modules/figmagic/templates/story.
figmagic [--templatePathStyled | -tpstyled] [path]
Default: templates/styled.
Your local figmagic.json or .figmagicrc file must have a block with templates.templatePathStyled that specifies a valid path, such as ./node_modules/figmagic/templates/styled.
figmagic [--token | -t] [token]
Default: null, and will then be taken from local .env file if not explicitly passed in through the CLI.
figmagic [--tokensRelativeImportPrefix | -tip] [path]
Default: '' (effectively just blank or the same folder). Use this so CSS files can import tokens from the correct location, for example to resolve something like ../../tokens/colors.ts you would pass in ../../ and tokens would be whatever your outputFolderTokens value is.
figmagic [--url | -u] [url_id]
Default: null, and will then be taken from local .env file if not explicitly passed in through the CLI.
figmagic [--unitlessPrecision | -up] [number]
Default: 2.
Defines the precision (decimals) for unitless values (rounded using .toFixed() internally).
figmagic [--usePostscriptFontNames | -ps]
Default: false, i.e. common name.
figmagic [--useLiteralFontFamilies | -lff]
Default: false, i.e. uses common name or Postscript name applied to the Figma's frame.
That's particularly useful for defining the whole font family stack with the fallbacks instead of a single font name, i.e.: Roboto, BlinkMacSystemFont, Helvetica, Arial, sans-serif
figmagic [--versionName | -v]
Default: null which will resolve to the latest version. The value you specify here is the name of the version in the Figma file's Version history.
From version 4.5.8, you can also export color themes tokens.
Consider the following example in Figma, as example of an app that allows the user to switch between Dark Theme and Light Themes for enhancing accessibility:
It will translate into the following generated tokens:
const colors = {
black: 'rgba(51, 51, 51, 1)',
white: 'rgba(255, 255, 255, 1)',
red: 'rgba(235, 87, 87, 1)',
blue8: 'rgba(47, 128, 237, 1)',
green6: 'rgba(33, 150, 83, 1)',
darkTheme: {
emptyShade: 'rgba(51, 51, 51, 1)',
fullShade: 'rgba(255, 255, 255, 1)',
mediumShade: 'rgba(189, 189, 189, 1)',
darkShade: 'rgba(224, 224, 224, 1)',
danger: 'rgba(248, 102, 102, 1)',
warning: 'rgba(246, 212, 107, 1)',
primary: 'rgba(39, 131, 255, 1)',
success: 'rgba(68, 239, 141, 1)'
},
lightTheme: {
fullShade: 'rgba(51, 51, 51, 1)',
emptyShade: 'rgba(255, 255, 255, 1)',
darkShade: 'rgba(130, 130, 130, 1)',
mediumShade: 'rgba(189, 189, 189, 1)',
danger: 'rgba(235, 87, 87, 1)',
warning: 'rgba(242, 201, 76, 1)',
primary: 'rgba(47, 128, 237, 1)',
success: 'rgba(33, 150, 83, 1)'
}
};Which in a practical example you could use as follows:
// initialize with default theme
let theme = 'lightTheme';
// Primary action button with white color token and with different primary background color according to the theme
let button = `<button style="background: ${colors[theme].primary}; color: ${colors.white}">Primary Action</button>`;
// Background color that changes according to the theme
let panel = `<div style=`color: ${colors[theme].emptyShade}`>Panel background</div>`Note on Components generation
Please note that component generation using the --syncElements options doesn't support color tokens yet. In case you have a component with a color that only exists on the colors -> color theme frame Figmagic will warn about: "No matching token! Hard-coding to expected value". Which means, that the component will still be created, just without a token assigned to it the color, since it currently only looks for the Colors frame and not for nested frames.
Starting with Figmagic version 4.0, four types of generated files have customizable templates:
- Graphic elements
- React elements
- Storybook files
- Styled Components (React) files
These four types have support for a variety of formats that differ a bit between each type.
Figmagic comes with a set of templates for several file formats. In case you want to customize these, you should respect and keep any substitution tags that exist in the original files; removing them may cause your templates to function incorrectly. For example, the React template includes a substitution tag called {{NAME_STYLED}} which will be changed to your adjusted element name with a "Styled" suffix. Removing it would make your generated code useless as-is.
The recommended way of adding and using your own templates would be to copy-paste any/all existing templates from Figmagic into your project, pointing the configuration file to your local copies, and then modifying them as needed.
The font family name, either as its common name (as picked up by Figma; spaces are removed) or its Postscript name (eg. FiraSans-Regular).
Default: Common name.
Note: In previous versions of Figmagic the Postscript font family name was used.
Typical font weight values like 200, 300 etc.
Units based on global font size (base 16px).
Default: rem units. Can be set to rem or em.
Unitless.
2 decimals numbered values by default. Precision can be configured with unitlessPrecision (see config)
Default: rgba. Can be set to rgba or hex.
Default: rem units. Can be set to rem or em.
Default: px units.
Default: em units.
Default: px units.
Typical 2 decimals numbered values between 0 and 1 like 0 or 0.65.
Can be set to percent to have them converted to % strings instead like 0% or 65%.
Default: s units. Can be set to ms.
Default: px units.
Default: px units for three values (horizontal offset, vertical offset, blur) and RGBA for the color.
Default: numbers (whole numbers, i.e. integers).
| Folder | Description |
|---|---|
__tests__/ |
Tests, structured similarly to the bin folder source code |
.github/ |
GitHub files for CI and issue template |
.husky/ |
Husky pre-commit configuration |
.vscode/ |
Visual Studio Code configuration |
bin/ |
Source code |
bin/contracts |
Types and interfaces |
bin/controllers |
Controllers |
bin/entities |
Entities (DDD-style), this is where most of the logic will be contained |
bin/frameworks |
Non-domain functionality, like string manipulation and downloading files etc. |
bin/usecases |
Where the application "features" are orchestrated, as per Clean Architecture |
build/ |
ES6-compiled code (this is the code that consumers of the Figmagic binary actually use) |
images/ |
Documentation, mostly images and screen shots. You can manually generate the Arkit diagram with npm run docs. |
readme/ |
Additional README files |
templates/ |
Files that are used as templates for code generation |
testdata/ |
Most of the tests point to stored test data which is stored in this folder |
translation/ |
Translations (localizations) of the README |
typedoc-docs/ |
Documentation generated by TypeDoc, which gets hosted at https://docs.figmagic.com. You can manually generate these with npm run docs. |
index.ts |
The file that initializes and sets up everything required to run Figmagic |
This is how Arkit models Figmagic and its source code structure and dependencies. Note that this diagram omits frameworks, external dependencies and contracts (i.e. types) to focus on the primary flows.
Note! Only visible on the documentation site.
Figmagic is licensed under the MIT License.
It uses a number of developer dependencies under various open source licenses, but none of these are bundled into the actual binary that users consume as Figmagic itself has no end-user-facing dependencies.
Copyright 2018-2023 Mikael Vesavuori
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
You are welcome to contribute to the project! Pull requests, as well as issues or plain messages, work fine. For pull requests, please refer to the contribution guidelines in CONTRIBUTING.md.
Thanks goes to these wonderful people (emoji key):
 Florent SCHILDKNECHT 💻 |
 Paulo Henrique 💻 |
 Petra Jaros 💻 |
 Marko Marković 💻 |
 mykhailoInnovecs 💻 |
 Zack Brown 💻 |
 Stanko Tadić 💻 |
 Ishmam Chowdhury 💻 |
 Ana Carolina 📖 |
 Shawn McCabe 💻 |
 Mitch O'Hair 💻 |
This project follows the all-contributors specification. Contributions of any kind welcome!