build-figma

Use for "/build-figma", a figma.com/design URL with node-id, or "implement this Figma" into a web, desktop, or shared UI. Orchestrates Figma MCP intake, maps nodes to the repo's own design system, then a verify-this visual judge. Do not paste Figma Tailwind.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exemplary thin-orchestrator skill: lean, gated, with explicit validation loops and real one-level-deep references. The only gaps are judgment-dependent details in the intake step and one cross-skill reference path that does not resolve within this bundle.

Dimension	Reasoning	Score
Conciseness	The ~67-line body is dense with rules and pointers and explains nothing Claude already knows ("Gate 1 blocks coding. 'Functional first, polish visuals later' is the main failure mode." is the only justification given, and it is one line). Every token earns its place. Not 4: there is nothing trimmable.	5 / 5
Actionability	Concrete, executable guidance throughout: URL parsing rule ("`1-2` → `1:2`", branch URLs, "No node-id → stop"), named MCP tools ("get_design_context and get_screenshot"), the exact artifact path "/tmp/build-figma/<slug>/intake.md" with its required contents, and six hard bans. Not 5: the split criterion ("If the response is sparse or too large, split to implementable child nodes") and "Download brand assets from MCP URLs" leave key execution details to judgment.	4 / 5
Workflow Clarity	Phases 0–4 are clearly sequenced with a gate checklist, two explicitly blocking gates ("Gate 1 blocks coding", "Visual judge (blocking)"), and a full feedback loop: "After NOT VERIFIED, fix the failed rows, recapture, and apply the rubric again. Repeat until VERIFIED or INCONCLUSIVE. Stop and report the blocker." Matches the anchor with validation steps, recovery loops, and a checklist.	5 / 5
Progressive Disclosure	A genuinely thin orchestrator body delegates to three real, one-level-deep reference files (references/design-system-discovery.md, references/visual-judge.md, references/failure-lessons.md — all present, none nesting further) and a clear per-phase delegation table. Not 5: the body links to ../dyl-mode/references/requirements.md, which is not present in this bundle, a minor navigation gap.	4 / 5
	Total	18 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: explicit trigger conditions, a concrete three-part capability statement in third person, and a clear exclusion boundary. The only weakness is that the implementation step itself is implied rather than named, leaving a small specificity gap.

Dimension	Reasoning	Score
Specificity	"Orchestrates Figma MCP intake, maps nodes to the repo's own design system, then a verify-this visual judge" lists three concrete actions in third person, but the actual implementation/output step is only implied rather than named, so coverage has a minor gap. Not 3: far more than 1-2 actions; not 5: the build/implement action itself is not explicitly listed.	4 / 5
Completeness	Both questions are explicitly answered: "what" via "Orchestrates Figma MCP intake, maps nodes to the repo's own design system, then a verify-this visual judge" and "when" via the concrete "Use for..." trigger phrases, plus a boundary statement ("Do not paste Figma Tailwind"). Matches the anchor for clear, explicit what AND when with concrete triggers.	5 / 5
Trigger Term Quality	"Use for \"/build-figma\", a figma.com/design URL with node-id, or \"implement this Figma\"" covers the command, the URL pattern, and a natural user phrase users would actually say. A few natural variants (\"Figma file\", \"mockup\", \"design\") are missing, so it is not the comprehensive synonym coverage of a 5.	4 / 5
Distinctiveness Conflict Risk	The niche (Figma → production web/desktop/shared UI) is unambiguous, triggers are distinct (a figma.com/design URL with node-id, the /build-figma command), and the explicit exclusion "Do not paste Figma Tailwind" further separates it from generic Figma-to-code skills. Minimal conflict risk.	5 / 5
	Total	18 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 1 suspicious	Warning

	Total	14 / 16 Passed

Repository: cursor/plugins
Path: dyl-stack/skills/build-figma/SKILL.md
Commit: c47b128

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.