Works with
A Figma UI kit Cursor can build from.
Appetite UI works with Cursor through its rules: the Core Skill’s rules go into .cursor/rules as an .mdc file, or into an AGENTS.md at the project root, so Cursor picks tokens by name.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.
What you get
What the file gives Cursor.
As the file ships today.
A Cursor rules block.
The file includes a block written for Cursor, which goes into .cursor/rules/appetite-ui.mdc.
An AGENTS.md for the project root.
The same rules as an AGENTS.md, for Cursor and for any other coding agent that reads one.
The token names to look up.
tokens.md and design.md sit at the repository root, so the agent can find a value by name.
Set up
How to wire it up for Cursor.
- 01
Connect Figma if you want it to read frames.
Use Figma’s deep link, or add the server to .cursor/mcp.json in the project or ~/.cursor/mcp.json for every project. - 02
Create the rule file.
Paste the block that comes with the purchase into .cursor/rules/appetite-ui.mdc. You can also add it under Rules in Cursor’s settings. - 03
Or use an AGENTS.md.
Put AGENTS.md at the project root with tokens.md and design.md beside it. - 04
Ask for a screen and review the diff.
Look for hex values, literal spacing and hand-set fonts.
Sample
What it looks like.
In code.
.cursor/rules/appetite-ui.mdc: the shape of the file; the body is the block that comes with the purchase.
---
description: Appetite UI rules for screens and tokens
alwaysApply: true
---
<paste the block from AI-context/agents/cursor-rules.md here>Watch for
What to check before you rely on it.
Project rules must be .mdc.
Cursor ignores a plain .md file inside .cursor/rules. The file needs the .mdc extension and its frontmatter.
Choose how the rule applies.
Cursor can apply a rule always, when it judges it relevant, for matching files or only when you mention it. A design system rule usually wants always.
A setup, not a recorded run.
This page describes the setup from the kit’s own instructions and Cursor’s documentation. It does not show a recorded Cursor session.
Not free, and no download link.
The rules are included with the file you buy.
FAQ
Questions about Cursor.
Yes, through rules. The file you buy includes a rules block for .cursor/rules and an AGENTS.md, and both tell the agent which token to use.
Either. Cursor reads both, and an AGENTS.md also works for other coding agents that read one.
Official documentation
Cursor's own documentation.
Where the tool says how it works. The date is the day it was read or linked.
Read 30 October 2026
Rules, Cursor documentation
Check it against the tool.
This page states what the file does today and follows the documentation beside it. Where the two differ, the tool’s own page wins.
Keep reading
On this site.
Read
Appetite UI and AI agents
Read
The Core Skill for AI agents
Read
Claude Code and Figma, from one frame to one screen
Bring your own stack.
Find your tool on the list, then open the preview and see how the kit sits next to it.