What is design-to-code?

A process for turning Figma designs into organised Flutter code, including reusable assets and project-specific UI structure. Flutter is a toolkit for building apps from one codebase across platforms.

Extracting and organising SVGs, icons, photos, and other images from Figma for a Flutter app. It also covers checking for existing assets, handling missing files, and regenerating the app's asset references.

It reduces guesswork when transferring designs into code, especially around asset locations, missing exports, and generated asset references. This helps the implementation match the project's expected structure.

design-to-code — Skill by anoopsg

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 skills/anoopsg/agent_rules/design-to-code

Any agent

npx skills add anoopsg/agent_rules --skill design-to-code

Clone the repo

git clone --depth 1 https://github.com/anoopsg/agent_rules

Made for: Claude Code, Codex.

Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,171 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.00022	$0.02171
Opus 5	$0.00011	$0.01086
Sonnet 5	$0.00004	$0.00434
Haiku 4.5	$0.00002	$0.00217

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

Security

Grade A, and why

design-to-code 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.

src/exclusive/skills/design-to-code/SKILL.md · 129 lines

How it starts

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

Design-to-Code Skill

1. Asset Management

1.1 Organization

All assets must be placed in the packages/app_ui/assets/ directory following this structure:

SVGs: assets/svg/
Icons: assets/svg/icons/
SVG Images: assets/svg/images/
Raster Images: assets/images/ (PNG, JPEG, WebP — e.g., photos, hero banners)
No Feature Folders: Do not create feature-specific subfolders (e.g., login/, auth/) within these asset directories. Keep the structure flat by asset type to avoid issues if an asset is later reused in another feature.

1.2 Verification & Generation

Verify: Before adding an asset, check packages/app_ui/assets/ to see if it already exists.
Add: Place the new asset in the appropriate folder.
Generate: Run melos run generate to update the AppAssets class.
Usage: Use AppAssets to reference the asset in code:
```
AppAssets.icons.google.svg();
```

1.3 Handling Missing or Unplaced Assets

When extracting from Figma via the MCP server, assets might not be marked for export or could be missing entirely:

Detection: If the MCP server cannot locate or export an expected visual asset.
Placeholders: Use a standardized placeholder widget to maintain layout integrity. Always include a TODO comment for traceability:
```
const SizedBox(width: 120, height: 120); // TODO(design): Replace with exported asset. @Source: <Page> > <Frame> > <Element>
```
Notification: Explicitly notify the user that the asset was missing from the exportable Figma assets and request they mark it for export or provide it manually. NEVER use the Figma MCP API asset URL (https://www.figma.com/api/mcp/asset/...) directly in the code (e.g. via Image.network).

1.4 Asset Usage

No Local Package Constants: NEVER define const _kUiPackage = 'app_ui'; locally.
Use Exported kUiPackage: Rely on the exported kUiPackage from app_ui when required, but avoid using it outside the package if possible.

Read the full file on GitHub · 129 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 · 129 lines · 22 tokens per session scan A 8abe7a9fe700

Subscribe to this mod's changes

design-to-code is a skill published in the GitHub repository anoopsg/agent_rules (2 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 2,171 once invoked, about $0.0001 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-31.

Frontend Mobile agent-rules agent-skills

spawn-session

新しい detached な Claude Code Remote Control セッションを Herdr 内に起動し、Claude モバイルアプリのセッション一覧に出す。生きている任意のセッションから（多くは iPhone の Remote Control 越しに）呼んで、別プロジェクトの新規セッションを Mac に触れず立ち上げる。Use when the user says 「新しいセッション立てて」「AAP のセッション開いて／立ち上げて」「contemplative のセッション作って」「spawn a (new) session」「launch a remote control session」「start a…

shimo4228/claude-harness · 197 tokens

orca-emulator-android

Control an Android emulator / device from inside Orca using the orca CLI. Use for listing/booting AVDs, taps, swipes, typing, hardware buttons (incl. Back and Recents), rotation, app install/launch, runtime permissions, the accessibility tree, and logcat — driving a real adb-connected device or emulator.…

stablyai/orca · 104 tokens

android-tombstone-symbolication

Symbolicate the .NET runtime frames in an Android tombstone file. Extracts BuildIds and PC offsets from the native backtrace, downloads debug symbols from the Microsoft symbol server, and runs llvm-symbolizer to produce function names with source file and line numbers. USE FOR triaging a .NET MAUI or Mono Android app…

dotnet/skills · 176 tokens

design-to-code