agentleFS
memi-designmemi-design/design-skills/skills/figma-implement-design/SKILL.md

figma-implement-design

Skill7 starsChanged 4 months agoMITView on GitHub

Route Figma-to-code implementation to Figma's current official MCP workflow while preserving repository conventions and independent verification. Use when a supplied Figma selection must become production code.

23 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use tailwind-patterns, shipping-and-launch and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • xenitV1Skill

    tailwind-patterns

    Tailwind CSS v4 principles. CSS-first configuration, container queries, modern patterns, design token architecture.

    Also in 3 projects that use this

  • LLl0k0laDSkill

    shipping-and-launch

    Use when preparing to deploy to production. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.

    Also in 3 projects that use this

  • guaderramaSkill

    spec-driven-development

    Generate comprehensive specifications for software projects using spec-driven development methodology. Leverages Bright Data MCP tools to research documentation, analyze competitor implementations, gather real-world examples, and enrich specs with architectural insights. Use when user requests specifications, technical plans, project specs, or architecture documentation.

    Also in 3 projects that use this

  • GoogleSkill

    algorithmic-art

    Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.

    Also in 4 projects that use this

  • JetBrainsSkill

    canvas-design

    Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.

    Also in 4 projects that use this

  • JetBrainsSkill

    brand-guidelines

    Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 20 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read local instructions, components, tokens, framework conventions, tests, and accessibility requirements.

    line 13
  2. Distinctive:

    Use the official integration to obtain current design context and assets.

    line 15
  3. Very specific:

    Use design-to-code-handoff to map the selection to existing components and tokens, implement through the repository's normal test workflow, …

    line 17
  4. Distinctive:

    If the official skill is unavailable, request exported context or screenshots and proceed only as an explicitly limited static …

    line 19

“Common” is measured: kept by at least 6 in 10 of the 20 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Figma Implement Design Router

This repository does not reproduce Figma's implementation skill. Use the official workflow as the integration layer and the local codebase as the implementation authority.

Procedure

  1. Confirm the exact Figma file or selection and the target repository surface.
  2. Read local instructions, components, tokens, framework conventions, tests, and accessibility requirements.
  3. Load Figma's current implementation skill from the official MCP guide distribution.
  4. Use the official integration to obtain current design context and assets.
  5. Reuse local components and tokens before creating new ones.
  6. Use design-to-code-handoff to map the selection to existing components and tokens, implement through the repository's normal test workflow, and create or update Storybook stories when present.
  7. Compare the result against the supplied design at representative states and viewport sizes, including interaction and accessibility states.
  8. If the official skill is unavailable, request exported context or screenshots and proceed only as an explicitly limited static implementation.

Official source: Figma MCP Server Guide

Return files changed, reused components, verification evidence, visual differences, and unresolved integration limits.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.