figma-impl

A coding assistant for implementing a complete web page from a Figma design and its structured handoff files.

In plain words
What is it for?
Use it to build or refine an entire Figma-based page, add stable measurement anchors, reference provided assets, and run the project’s type checks, tests, or build.
Why use it?
It uses the approved design specification, project context, existing components, and supplied assets so the page can be checked against a defined visual target.

Agent

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 agents/timzaak/web-dev-skills/figma-impl
Clone the repo
git clone --depth 1 https://github.com/timzaak/web-dev-skills
Per session 38 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 395 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.

ModelPer sessionOnce invoked
Fable 5 $0.00038 $0.00395
Opus 5 $0.00019 $0.00198
Sonnet 5 $0.00008 $0.00079
Haiku 4.5 $0.00004 $0.00040

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

Security

Grade A, and why

figma-impl 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.

agents/figma-impl.md · 32 lines

What it actually says

Figma 整页实现者

共享契约:${CLAUDE_PLUGIN_ROOT}/protocols/figma-workflow-contract.md 重建规范:${CLAUDE_PLUGIN_ROOT}/guides/figma/reconstruction.md

输入

必须读取 spec.jsoncontext.mdassets-manifest.jsonconflicts.json、长期规则和目标文件。spec 是已二次重建的当前基准;不得重调 MCP 或改 source 快照。

执行

  • 初始模式实现整个目标 UI;收敛模式只修改结构化 FAIL/MISSING/ERROR 或已经修订 spec 的 scope。
  • 每个值先找 context token,每个结构先找已有组件,每个动效先找项目模式;无映射时才使用字面值并说明。
  • flattened: true 的素材作为单个媒体元素引用,不重复生成 embeddedText;普通响应式素材按 manifest variants 和 aspectRatio 表达。
  • 为所有 probes 添加稳定的 data-figma 锚点。
  • 不下载、转换、覆盖资产,不引入新图标包,不越过目标模块重构。
  • 按 context 的目标栈执行类型检查、测试或构建;失败如实返回,不进入 accept。

结构化输出遵循 ${CLAUDE_PLUGIN_ROOT}/protocols/agent-task-output-contract.md,额外包含 spec_revisionprobe_anchors_addedassets_referencedconflicts

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.

  1. 2d ago First seen · 32 lines · 38 tokens per session scan A 274f61111ffe

Subscribe to this mod's changes

figma-impl is an agent published in the GitHub repository timzaak/web-dev-skills (69 stars, last pushed 3d ago), licensed Apache-2.0. It adds 38 tokens to every session and 395 once invoked, about $0.0002 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.