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.
npx skills add memi-design/design-skills --skill figma-generate-designgit clone --depth 1 https://github.com/memi-design/design-skillsWrote 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/memi-design/design-skills/figma-generate-design)<a href="https://agentmods.dev/skills/memi-design/design-skills/figma-generate-design"><img src="https://agentmods.dev/badge/skills/memi-design/design-skills/figma-generate-design/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/memi-design/design-skills/figma-generate-design"><img src="https://agentmods.dev/badge/skills/memi-design/design-skills/figma-generate-design.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.00022 | $0.01322 |
| Opus 5.5 | $0.00009 | $0.00529 |
| Sonnet 5.5 | $0.00004 | $0.00264 |
| Haiku 4.5 | $0.00002 | $0.00132 |
Grade A, and why
figma-generate-design 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/figma-generate-design — Create Designs Using Existing Components
Generate new screens and pages in Figma using your existing components, variables, and design system. Produces structured, spec-compliant layouts with full self-healing validation. Requires /figma-use.
Freedom Level: High
Full creative freedom within the design system. Must use existing components and variables, never raw values.
Prerequisites
/figma-usefoundational skill loaded- Design system pulled (
memi pull) or variables exist in file figma_search_componentscalled this session (nodeIds are session-scoped)
Workflow
Step 1: Check Code Connect & Inventory
get_code_connect_map → what's already mapped code ↔ Figma?
figma_search_components → what components exist?
figma_get_variables → what tokens are available?
If Code Connect mappings exist: use those components. Don't recreate.
Step 2: Plan the Layout (Atomic Design)
Map the design to atomic levels:
Page: AuthLogin
├── Template: AuthTemplate (centered, max-w-md)
│ ├── Organism: LoginForm
│ │ ├── Molecule: FormField (email)
│ │ │ ├── Atom: Label
│ │ │ ├── Atom: Input
│ │ │ └── Atom: HelpText
│ │ ├── Molecule: FormField (password)
│ │ ├── Molecule: SocialLogin
│ │ │ ├── Atom: Button (Google)
│ │ │ ├── Atom: Separator
│ │ │ └── Atom: Button (GitHub)
│ │ └── Atom: Button (Submit)
│ └── Organism: Footer
Step 3: Build Bottom-Up
- Atoms — instantiate existing or create with
use_figma - Molecules — compose atoms with Auto Layout
- Organisms — compose molecules with state considerations
- Template — page frame with responsive constraints
- Page — fill template with real content
Prefer use_figma for design-aware writes. It understands your design system and returns structured output.
Step 4: Apply Design Tokens
All visual properties MUST bind to variables:
background → colors/surface/primary
text → colors/text/primary
border → colors/border/default
spacing → spacing/4, spacing/8, spacing/16
radius → radius/default, radius/lg
Never hardcode. If a token doesn't exist, create it with figma_batch_create_variables first.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 142 lines · 22 tokens per session scan A fb89f7f2898b
figma-generate-design is a skill published in the GitHub repository memi-design/design-skills (7 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 1,322 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
accessibility-per-component
Audit one design system component's accessibility against WCAG 2.2 AA: keyboard, screen reader, contrast, focus, ARIA, target size. Trigger: a11y audit, is this accessible, WCAG check, screen reader support, keyboard navigation check. Not for page- or product-wide audits.
figma-variable-audit
Audit Figma variable collections: tier mapping, naming, alias chains, modes, orphans; can fix in place with Figma Console MCP. Triggers: audit my Figma variables, review variable collections, Figma variable health. For token files in code use token-audit.
theme-audit
Audit theme parity: tokens missing or unchanged per theme, component tokens bypassing semantics, contrast within each theme, resolver contexts, theme-switch regressions. Triggers: dark mode audit, theme coverage, brand variant parity. For general token structure use token-audit.
token-audit
Audit how design tokens are defined: tiers, naming, alias chains, raw values, orphans, DTCG readiness. Triggers: audit my tokens, token architecture review, token health check. Not for code consuming tokens (token-compliance), theme parity (theme-audit) or Figma variables (figma-variable-audit).
token-compliance
Find hardcoded colour, spacing and type values and wrong-tier token references in consuming code. Trigger: find hardcoded values, any hex in the code, are we using tokens correctly, token compliance. Do NOT use for token definitions — token-audit; token file format — schema-validator.
ai-component-description
Write a six-section prose description (purpose, props, anti-patterns, composition, accessibility, examples) for a Figma component's description field so LLMs read it via MCP. Triggers: describe this component for AI, Figma MCP description. JSON metadata files: use metadata-schema-generator.