agentleFS
Sign inStart free
mtarcuremtarcure/claude-vibe-squad/.agents/skills/figma-implement-design/SKILL.md

figma-implement-design

Skill220 starsChanged 18 days agoMITView on GitHub

Use when a Figma file or frame is the authoritative implementation source and production UI must reproduce its tokens, component variants, auto-layout, interaction states, and responsive breakpoints through the project’s established primitives. This is source-to-code translation; post-build acceptance and inventing a visual language are separate work.

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

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

  • 0

    Common

    Most of the 20 edited versions we read keep these.

  • 2

    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 the design's structure and design tokens (color, type, spacing, radius) from the source, not from a screenshot guess.

    line 12
  2. Very specific:

    Verify against the source for fidelity and against wcag-conformance-audit for accessibility.

    line 16
  3. Distinctive:

    All specified states, variants, and breakpoints are implemented.

    line 20

“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

Translate a Figma design into production UI code faithfully — tokens, components, states, and responsive behavior — not a pixel-approximation.

Steps

  1. Read the design's structure and design tokens (color, type, spacing, radius) from the source, not from a screenshot guess.
  2. Map Figma components to existing code components; reuse the design system rather than re-implementing primitives.
  3. Implement layout with the real layout model (auto-layout → fl/grid), not absolute pixel offsets.
  4. Cover all states and variants (hover/focus/active/disabled/empty/error) and responsive breakpoints the design specifies.
  5. Verify against the source for fidelity and against wcag-conformance-audit for accessibility; flag any design gap (missing state/token) back rather than inventing it.

Acceptance

  • Tokens and components map to the design system; no re-implemented primitives.
  • All specified states, variants, and breakpoints are implemented.
  • Output is verified for fidelity and accessibility; design gaps are flagged, not guessed.

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.

Check your setup, free