Install
$ agentstack add skill-draz26648-flutter-claude-skills-figma-to-widget ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Figma to Widget
> Profile first. Read .claude/flutter-profile.yaml in the project root. tokens > decides how the values in a frame get resolved and structure decides where the new > widget file goes. The mapping table below is stack-independent and holds under every > profile. Field list: > ${CLAUDE_PLUGIN_ROOT}/skills/design-tokens/references/flutter-profile.md.
The failure mode this prevents: translating a design by reading pixel positions and reproducing them with Stack and Positioned. That output matches the artboard exactly and breaks on every other screen size. Figma's layout system maps cleanly onto Flutter's — use the mapping, not the coordinates.
Prerequisite
Check whether the Figma MCP server is connected. If it is, pull the frame directly and read real values. If it is not, say so before starting: without it, every value is being read off a rasterized image and is a guess. Ask for the design tokens, a Dev Mode inspection export, or the spacing scale rather than guessing silently.
The mapping
| Figma | Flutter | |---|---| | Auto Layout, vertical | Column | | Auto Layout, horizontal | Row | | Auto Layout gap | spacing: on Row/Column, or a Gap widget | | Auto Layout padding | Padding with a directional token | | Space between | MainAxisAlignment.spaceBetween | | Hug contents | MainAxisSize.min | | Fill container | Expanded, or double.infinity on a single child | | Fixed width/height | SizedBox, only when the design truly requires it | | Absolute position | Stack + Positioned — last resort only | | Frame with clip | ClipRRect with a radius token | | Component instance | An existing widget from the codebase | | Component variant | A parameter or enum on that widget, not a new widget |
Rules
Auto Layout first. If a frame uses Auto Layout, the output uses Row or Column. Reach for Stack only when the design genuinely overlaps elements — an avatar badge, a floating action button over content. Overlap is the only valid reason.
Never hardcode the artboard width. A 390pt frame is a reference, not a target. Fixed widths appear only where the design is explicitly fixed regardless of screen — an avatar, an icon, a fixed-size chip.
Check for an existing component before building a new one. A Figma component instance almost always corresponds to a widget that already exists in the codebase. Building a second PrimaryButton because the first was not found is the most common form of duplication in agent-generated UI — and the usual cause is searching for the name you expected rather than the role. Search by suffix (class .*Button), not by the name in your head. The codebase-conventions skill carries the full search protocol and the project's component locations.
Variants are parameters. A Figma component with Default, Hover, Disabled, and Loading variants becomes one widget with a state parameter — not four widgets.
Text is never Text('...') with an inline style. Style comes from the tokens (see the design-tokens skill), content comes from localization (see a11y-and-rtl).
Workflow
- Pull the frame and identify its layer tree.
- List every distinct visual value in it. Resolve each against the token set. Report
anything unmatched before writing code.
- Identify which layers are instances of existing components. Search the codebase for
each. Reuse.
- Write the widget tree following the mapping table above.
- Hand off to the visual-verification skill. Do not declare the screen done on the
basis that it compiled.
Common mistakes
- Nesting
ContainerinsideContainerbecause the design has nested frames. Collapse
them; one Container handles padding, color, and radius together.
- Producing one enormous
build()method for the whole screen. Split at the same
boundaries the design file uses for its components.
- Adding
SizedBox(height: n)between every element instead of using the parent's
spacing parameter. The design expresses it as an Auto Layout gap; express it the same way.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: draz26648
- Source: draz26648/flutterclaude_skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.