What is token-sync-layer?

A one-way pipeline that turns design variables from Figma into code files. Figma is the source of truth, and the generated files can target systems such as Tailwind, MUI, CSS, iOS, or Android.

Use it to sync Figma variables, generate platform-specific token files, and install a reusable command for repeating the sync.

It removes manual copying of shared design values such as colours, spacing, and type sizes into code. Re-running the command keeps the code outputs aligned with Figma changes.

token-sync-layer — Cursor rule by jrpease

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add rules/jrpease/throughline/token-sync-layer

Clone the repo

git clone --depth 1 https://github.com/jrpease/throughline

Made for: Cursor.

Per session 126 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 4,133 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00126	$0.04133
Opus 5	$0.00063	$0.02067
Sonnet 5	$0.00025	$0.00827
Haiku 4.5	$0.00013	$0.00413

Measured 2d ago against content hash f97d3a71aaa1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

token-sync-layer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

adapters/cursor/.cursor/rules/token-sync-layer.mdc · 304 lines

How it starts

The opening of the file, as written. The whole thing — 304 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Token sync layer

Compiles Figma variables into code. The pipeline is one-directional — Figma is the source of truth for token values; code consumes generated artifacts that are never hand-edited:

Figma variables → DTCG JSON → Style Dictionary → adapter output (per platform)

This skill both performs the sync and installs the reusable /sync-figma-tokens command so the user can re-run it anytime tokens change.

Calibrate

Read user.codingLevel (.throughline/references/coding-level.md) and scale explanation accordingly. The pipeline involves several developer concepts (JSON, build tools, PRs) — for new users, explain each plainly the first time; for comfortable users, be terse. Actions are identical across levels.

Prerequisites (offer to run them, don't bail)

Read the manifest. This skill needs two things:

Tokens in Figma — tokens.semanticBuilt should be true. If no tokens exist, offer to run token-builder first.
At least a local git repo — workspace.stage must be local-git or github (so the sync can land changes as a reviewable diff/PR). If it's still folder, this is the soft-nudge seam: offer to run repository-builder to add version history first. Explain plainly why ("the sync writes code files, and git lets you review exactly what changed before keeping it"). If the user is at local-git but not github, strongly recommend connecting a remote (GitHub or similar) so the sync can land as a real reviewable PR — the cleanest review model — but don't force it; a reviewed branch diff works at local-git.

A live Figma connection is also required — do a cheap liveness read; if it fails, offer figma-environment-setup.

Step 1 — Choose target platform(s)

Ask which platform(s) the user is building for. Read .throughline/references/sync-adapters.md for the two-tier adapter model.

Curated (Tier 1): shadcn, tailwind, mui, vanilla-css, ios-swift. Vetted presets — high confidence.
Generated (Tier 2): any other framework (Ant Design, Chakra, HeroUI, Android/Kotlin, Flutter, etc.). The skill generates an adapter and verifies it against a real component before trusting it.

Read the full file on GitHub · 304 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2d ago First seen · 304 lines · 126 tokens per session scan A f97d3a71aaa1

Subscribe to this mod's changes

token-sync-layer is a cursor rule published in the GitHub repository jrpease/throughline (76 stars, last pushed 4d ago), licensed MIT. It adds 126 tokens to every session and 4,133 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Frontend Mobile

token-sync-layer

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Token sync layer

Calibrate

Prerequisites (offer to run them, don't bail)

Step 1 — Choose target platform(s)

What this file has done since we first saw it

Other cursor rules, from other repositories

cursorrules

git-commit-attribution

android-viewmodel

project-structure

cursorrules

ios-ui-development-focus