agentleFS
epamepam/ai-dial-chat/.claude/skills/figma/SKILL.md

figma

Skill501 starsChanged 17 days agoApache-2.0View on GitHub

Design-to-code workflow for Figma designs. Use when the user shares a Figma URL or asks to implement a design into the codebase.

53 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use analytics-metrics, aws-account-management 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.
  • hoodiniSkill

    analytics-metrics

    Build data visualization and analytics dashboards. Use when creating charts, KPI displays, metrics dashboards, or data visualization components. Triggers on analytics, dashboard, charts, metrics, KPI, data visualization, Recharts.

    Also in 3 projects that use this

  • hoodiniSkill

    aws-account-management

    Manage AWS accounts, organizations, IAM, and billing. Use when setting up AWS Organizations, managing IAM policies, controlling costs, or implementing multi-account strategies. Triggers on AWS Organizations, AWS IAM, AWS billing, Cost Explorer, SCPs, multi-account, AWS SSO, Identity Center.

    Also in 3 projects that use this

  • LangChainSkill

    slideshow

    Author a HyperFrames slideshow — a presentation, pitch deck, or interactive deck with discrete slides, fragment reveals, branching, hotspot navigation, and built-in presenter mode with speaker notes; also converts an existing page into a deck. Output is a navigable deck, not a rendered MP4. If the user didn't explicitly ask for a slideshow, confirm before authoring. Unclear → /hyperframes.

    Also in 8 projects that use this

  • jaron-goh-centrSkill

    talking-head-recut

    Package an existing talking-head / interview / podcast video with timed, designed GRAPHIC OVERLAY cards — kinetic titles, lower-thirds, data callouts, quotes, side panels, picture-in-picture — synced to the transcript, on a 16:9 / 9:16 / 4:5 canvas of your choice; the clip plays untouched underneath. Trigger on "graphic overlays", "on-screen graphics", "package / dress up my video". Not plain subtitles (/embedded-captions). Unclear → /hyperframes.

    Also in 6 projects that use this

  • LangChainSkill

    faceless-explainer

    Turn arbitrary text — an article, notes, a topic, a brief — into a faceless explainer video: there is no site or footage to capture, so the visuals are invented per scene (typography, abstract graphics, diagrams, data-viz). Use for topic explainers, concept breakdowns, how-tos, listicles. Not a video built from a website (/product-launch-video — promo or tour). Unclear → /hyperframes.

    Also in 6 projects that use this

  • ElyzeSolutionsSkill

    captions-overlay

    Overlay doctrine for the embedded-captions workflow — the caption MODEL (drop / rail / embed) and the rule that captions are an OVERLAY composited on top of the film, never a reserved bottom band you shift content up to avoid. Load when adding captions/subtitles to a talking-head or launch video, when deciding whether a phrase should be dropped, ride the verbatim rail, or be promoted to a scarce embedded climax, when laying out a composition that will carry captions (do NOT reserve a keep-out band), or when centering a composition on the true frame center under captions. Quotes the rail+embed model from embedded-captions and constraint #13 (captions overlay, keep-out band retired) from the product-launch-video scene agent. Applies ON TOP of embedded-captions.

    Also in 3 projects that use this

  • +4 more from hoodini

The file

Show its rules and text

We split this skill into the rules it gives an agent

15 rules. 0 are common, 11 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 45 edited versions we read keep these.

  • 11

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Very specific:

    Call get_design_context with the fileKey and nodeId extracted from the URL.

    line 22
  2. Distinctive:

    If the design context includes Code Connect snippets, prefer those — they map directly to codebase components.

    line 29
  3. Distinctive:

    Before writing any new code, check whether ui-kit or existing project components cover the need:

    line 35
  4. Distinctive:

    Write TypeScript + JSX; no plain JS

    line 52
  5. Very specific:

    Use async/await with try/catch/finally for frontend async flows.

    line 53
  6. Distinctive:

    Use Tailwind for all styling — no inline styles, no CSS modules unless they already exist in the target file

    line 54
  7. Distinctive:

    Do not copy raw hex colors from Figma.

    line 55
  8. Distinctive:

    Keep components small and focused — split at logical boundaries, not at line count

    line 58
  9. Very specific:

    When implementing under libs/*, keep the component host-agnostic: no host-owned integration details such as /api URLs, generated clients, …

    line 59
  10. Very specific:

    Run npm exec nx lint <project> — fix any lint errors before reporting done

    line 69
  11. Distinctive:

    If the component has logic, add a unit test in the same lib

    line 70
  12. Distinctive:

    If the dev server is running, open the component in the browser and compare with the Figma screenshot at each breakpoint the design covers …

    line 71
  13. Distinctive:

    Never use absolute positioning unless the Figma design explicitly requires it and no flex/grid alternative exists

    line 75
  14. Distinctive:

    Do not add new dependencies without asking — check if the need is already met

    line 76
  15. Distinctive:

    If the design is ambiguous or missing states (hover, disabled, error), flag them explicitly rather than guessing

    line 78

“Common” is measured: kept by at least 6 in 10 of the 45 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 Design-to-Code

Overview

Translate Figma designs into production-ready React components that match project conventions: React 19, Tailwind CSS, TypeScript, and @epam/ai-dial-ui-kit.

When to Use

  • User shares a figma.com URL
  • User says "implement this design" or "build this screen"
  • User asks to match a Figma component or layout

Workflow

Step 1 — Fetch the design

Call get_design_context with the fileKey and nodeId extracted from the URL.

URL parsing rules:

  • figma.com/design/:fileKey/...?node-id=:nodeId → replace - with : in nodeId
  • figma.com/board/:fileKey/... → FigJam file, use get_figjam instead

If the design context includes Code Connect snippets, prefer those — they map directly to codebase components.

Responsive variants. Before fetching, scan the file for sibling frames at mobile vs. desktop sizes (typically 375/390 and 1280/1440/1920). When both exist, fetch both node IDs and reconcile the divergences (layout swaps, hidden sections, drawer vs. sidebar) before writing code. When only desktop is provided, ask the user before deriving a mobile version rather than guessing. See .claude/skills/responsive-design/SKILL.md for the breakpoint mapping and decision rubric.

Step 2 — Map to project components

Before writing any new code, check whether ui-kit or existing project components cover the need:

Design needCheck first
Buttons, inputs, modals, icons@epam/ai-dial-ui-kit
Generic icons@tabler/icons-react
Layout, spacing, colorTailwind CSS classes
Project-specific patternslibs/ and apps/ in this monorepo

Grep the codebase before building from scratch:

Grep("ComponentName", path="libs/")

Step 3 — Implement

  • Write TypeScript + JSX; no plain JS
  • Use async/await with try/catch/finally for frontend async flows; avoid Promise chains with .then()/.catch()
  • Use Tailwind for all styling — no inline styles, no CSS modules unless they already exist in the target file
  • Do not copy raw hex colors from Figma; map to Tailwind tokens or CSS variables already in the project
  • Match the naming conventions of surrounding files (PascalCase components, kebab-case files)
  • Name React event callback props onEvent and component-local handlers handleEvent
  • Keep components small and focused — split at logical boundaries, not at line count
  • When implementing under libs/*, keep the component host-agnostic: no host-owned integration details such as /api URLs, generated clients, server-api imports, app contexts, auth/session/cookie/env access, feature flags, route/navigation knowledge, analytics/telemetry, SDK setup, platform bridges, app-specific URL schemes, or storage keys/schemas. Expose props/callbacks/resolved values for app behavior instead.

Step 4 — Verify

After implementation:

  1. Run npm exec nx lint <project> — fix any lint errors before reporting done
  2. If the component has logic, add a unit test in the same lib
  3. If the dev server is running, open the component in the browser and compare with the Figma screenshot at each breakpoint the design covers (360 / 768 / 1024 / 1280 / 2560 as applicable)

Constraints

  • Never use absolute positioning unless the Figma design explicitly requires it and no flex/grid alternative exists
  • Do not add new dependencies without asking — check if the need is already met
  • Pixel-perfect fidelity matters less than semantic correctness and accessibility
  • If the design is ambiguous or missing states (hover, disabled, error), flag them explicitly rather than guessing

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.