figma

A workflow for turning a Figma design into a working Toolcraft app. Figma is a collaborative design tool that stores layouts, components, styles, and assets.

In plain words
What is it for?
Use it when building or matching a Toolcraft app from a Figma link, node, or design specification.
Why use it?
It keeps the implementation aligned with the design's actual structure instead of relying on a screenshot or visual guess.

Skill for Claude CodeCodex

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/pixel-point/toolcraft/figma
Any agent
npx skills add pixel-point/toolcraft --skill figma
Clone the repo
git clone --depth 1 https://github.com/pixel-point/toolcraft

Made for: Claude Code, Codex.

Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 186 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.00024 $0.00186
Opus 5 $0.00012 $0.00093
Sonnet 5 $0.00005 $0.00037
Haiku 4.5 $0.00002 $0.00019

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

Security

Grade A, and why

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

examples/ascii/.agents/skills/figma/SKILL.md · 25 lines

What it actually says

Toolcraft Figma Workflow

Use this skill when the user provides a Figma URL, node ID, or asks to implement or match a Figma design.

Process

  1. Inspect the Figma file through the available Figma MCP or design context tooling.
  2. Read actual nodes, layers, components, variables, styles, assets, and layout structure.
  3. Translate the design into Toolcraft schema controls, product renderer output, canvas sizing, export behavior, and verification coverage.
  4. Use screenshots only for final visual QA, not as the source of truth.

Toolcraft Rule

Do not implement a Figma task from a screenshot or by eye when Figma context is available. The Figma structure is the reference.

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 · 25 lines · 24 tokens per session scan A f604e6030a5f

Subscribe to this mod's changes

figma is a skill published in the GitHub repository pixel-point/toolcraft (714 stars, last pushed 25d ago), licensed MIT. It adds 24 tokens to every session and 186 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-30.

Related

Other skills, from other repositories

design-guide

Paperclip UI design system guide for building consistent, reusable frontend components. Use when creating new UI components, modifying existing ones, adding pages or features to the frontend, styling UI elements, or when you need to understand the design language and conventions. Covers: component creation, design…

paperclipai/paperclip · 105 tokens

gstack-openclaw-office-hours

Use when asked to brainstorm, evaluate whether an idea is worth building, run office hours, or think through a new product idea or design direction before any code is written.

garrytan/gstack · 42 tokens

material-ui-tailwind

Integrates Material UI with Tailwind CSS v4 using cascade layers (enableCssLayer, @layer order) and documents Tailwind v3 interoperability (preflight, important, injectFirst, portals). Use when combining MUI with Tailwind utilities, slotProps className, or theme token bridges.

mui/material-ui · 67 tokens

hallmark

Anti-AI-slop design skill for greenfield pages, audits, redesigns, and design extraction from URLs or screenshots. Use when the user asks to build a new app or landing page, wants to redesign something, invokes Hallmark by name, or uses audit/redesign/study.

Nutlope/hallmark · 61 tokens

accessibility

Consolidated accessibility skill entrypoint for WCAG 2.2, ARIA Authoring Practices, cognitive accessibility, Section 508, EN 301 549, design intent verification, and the Accessibility Planner workflow.

microsoft/hve-core · 47 tokens

deck-course-module

暖纸背景 + Playfair, 左侧学习目标常驻, 含 MCQ 自测页.

nexu-io/html-anything · 25 tokens