Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/PMDevSolutions/Aureliusnpx agentmods add skills/pmdevsolutions/aurelius/build-from-figmaWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/pmdevsolutions/aurelius/build-from-figma)<a href="https://agentmods.dev/skills/pmdevsolutions/aurelius/build-from-figma"><img src="https://agentmods.dev/badge/skills/pmdevsolutions/aurelius/build-from-figma/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/pmdevsolutions/aurelius/build-from-figma"><img src="https://agentmods.dev/badge/skills/pmdevsolutions/aurelius/build-from-figma.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.1 | $0.00100 | $0.05318 |
| Opus 5.5 | $0.00040 | $0.02127 |
| Sonnet 5.5 | $0.00020 | $0.01064 |
| Haiku 4.5 | $0.00010 | $0.00532 |
Grade A, and why
build-from-figma 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 429 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/build-from-figma — Autonomous Figma-to-Working-App Pipeline
You are the master orchestrator for converting a Figma design into a fully working, tested React application. You receive a Figma URL and guide the entire process through 9 phases, using specialized skills and agents.
Key enforcement rules:
- TDD is mandatory — Phase 3 (TDD) MUST complete before Phase 4 (Build). No exceptions.
- The tests are the specification — Phases 4 and 5 never edit a test file; the
component-lanesworkflow checks every test file's checksum after each change. - Visual QA uses pixel diff — Phase 5 uses
scripts/visual-diff.jsfor programmatic comparison, not manual eyeballing. - E2E tests are generated — Phase 6 generates and runs Playwright E2E tests appropriate to the app type.
- App-type aware — Chrome extensions, PWAs, and web apps each get tailored test strategies.
Input
The user provides: $ARGUMENTS (a Figma URL, optionally with node-id)
Parse the Figma URL to extract:
fileKeyfrom the URL pathnodeIdfrom the?node-id=parameter (convert-to:)- For branch URLs: use
branchKeyasfileKey
Configuration
Load .claude/pipeline.config.json at the start. This provides:
- Visual diff thresholds and iteration limits
- TDD enforcement settings
- E2E strategy per app type
- Quality gate thresholds
- Lighthouse score minimums
Progress Tracking
Track the run in .claude/plans/pipeline-state.json (gitignored, beside build-spec.json). Todo tools are not offered on current models, and a file survives an interrupted session: the SessionStart hook reads it and tells the next session where the run stopped. /build-from-canva, /build-from-screenshot and /build-from-conversation use the same file and shape.
Create it when the run starts, and rewrite it at every phase boundary and after each component and page result:
{
"pipeline": "figma",
"source": "https://www.figma.com/design/abc123/My-App",
"renderer": "vite",
"appType": "web-app",
"startedAt": "2026-10-24T15:00:00Z",
"updatedAt": "2026-10-24T15:42:00Z",
"phase": "5",
"phases": {
"0": { "name": "token-sync", "status": "skipped" },
"1": { "name": "intake", "status": "done", "artifact": ".claude/plans/build-spec.json" },
"2": { "name": "token-lock", "status": "done", "artifact": "src/styles/design-tokens.lock.json" },
"3": { "name": "tdd-scaffold", "status": "done" },
"4": { "name": "component-build", "status": "done" },
"4.5": { "name": "storybook", "status": "pending" },
"5": { "name": "visual-diff", "status": "running" },
"5.5": { "name": "dark-mode", "status": "pending" },
"6": { "name": "e2e-tests", "status": "pending" },
"7": { "name": "cross-browser", "status": "pending" },
"8": { "name": "quality-gate", "status": "pending" },
"8.5": { "name": "responsive", "status": "pending" },
"9": { "name": "report", "status": "pending" }
},
"components": { "Button": { "test": "src/components/Button/Button.test.tsx", "testSha256": "…", "build": "green", "attempts": 1 } },
"pages": { "home": { "visual": "pass", "worstMismatchPct": 0.012, "rounds": 2 } },
"notes": ["Hero: needs review, 768px layout still 4.1% off after 5 rounds"]
}
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.
- yesterday First seen · 429 lines · 0 tokens per session scan A 1978b7a9f0d4
build-from-figma is a skill published in the GitHub repository PMDevSolutions/Aurelius (9 stars, last pushed yesterday), licensed MIT. It adds 100 tokens to every session and 5,318 once invoked, about $0.0004 per session on Opus 5.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-10-25.
Other skills, from other repositories
design-qa
A visual checking and correction workflow that compares a running app screen with its Figma source using captures, overlays, difference maps, and pixel measurements. An overlay places two images together so mismatches are easier to see.
qa-test-planner
Generate comprehensive test plans, manual test cases, regression test suites, and bug reports for QA engineers. Includes Figma MCP integration for design validation.
critique
Adversarial design critique of the current work. Render it, look at it, and argue for rejection. Run after the gates are green, never instead of them.
figma-codegen
Generate framework-aware code from a Figma design. Reads the project's stack profile and emits code matching the existing framework (React/Vue/Svelte/Next/etc.) and styling (Tailwind/CSS/CSS-in-JS), reusing existing components and design tokens instead of regenerating from scratch. Triggers whenever the user wants a…
figma-build
Build a Figma design from code or a description — the reverse of figma-codegen. Reuses the connected file's existing design system (components, variables, styles) instead of drawing primitives with hardcoded values. Triggers whenever the user wants something created or updated IN Figma from code or a spec — e.g.…
visual-validation
Autonomous screenshot verification — captures, compares, and AI-evaluates UI changes for visual regressions.