Works with
The tools Appetite UI works with today.
One page for each tool or stack, with what the file gives it, how to wire it up, what to watch for and the tool’s own documentation.7 tools, updated Appetite UI is a Figma UI kit for iOS and Android apps, built like a design system. One token source drives Apple and Material components in light and dark mode, and exports to SwiftUI, Jetpack Compose, Flutter and CSS.
The tools
7 pages, one for each tool.
Each row is a page that says what the file gives that tool today, how to wire it up and what to check.
| Tool | What you get | Where to find it |
|---|---|---|
| SwiftUI | A Swift token file: dynamic colors, Dynamic Type text, spacing and radius, named like the Figma variables. | SwiftUI page |
| Jetpack Compose | A Kotlin token output read as AppetiteTheme, with a ready Material 3 typography object. | Jetpack Compose page |
| Flutter | A Dart token file and ThemeData for Light and Dark, named like the Figma variables. | Flutter page |
| CSS | A CSS file of --ap custom properties, with the dark values as a second block. | CSS page |
| Claude Code | The Core Skill, a slop linter skill and an AGENTS.md, for .claude/skills. | Claude Code page |
| Cursor | A rules block for .cursor/rules and an AGENTS.md, both from the Core Skill. | Cursor page |
| Figma Make | SKILL.md and tokens.md to attach to a Figma Make chat. | Figma Make page |
How the pages are written
Only what the file does today.
Said here so a page never promises more than the file.
The four code pages are about tokens.
One token source generates SwiftUI, Jetpack Compose, Flutter and CSS, and the source and all four outputs come with the file you buy. The components are Figma components, and coded components are not part of the file.
The three AI pages are about instructions.
The Core Skill is included with the purchase. It tells an agent which token and pattern to use, and each tool reads it from its own place.
Each page names its sources.
It links the tool’s own documentation with the day it was read or linked, so you can check the setup against the tool.
A tool that is not here has no page yet.
The list is the tools the kit works with today, not the tools it might. Questions go to the address on the contact page.
Bring your own stack.
Find your tool on the list, then open the preview and see how the kit sits next to it.