agentic-coding: Skill for Claude Code

.agents/skills/figma-implement/SKILL.md

figma-implement is a skill for Claude Code, Codex from P2ERGmbH/agentic-coding. It costs 41 tokens per session (4,746 once invoked), scanned A, original, MIT.

A workflow for turning downloaded Figma design data into a working Tailwind CSS interface. Figma is a design tool, while Tailwind CSS is a system of reusable styling classes.

In plain words
What is it for?
Implementing Figma frames, converting designs to Tailwind classes, mapping design layers to components, and validating reusable UI components.
Why use it?
It helps developers translate exact design layers, fonts, colors, borders, and spacing into code and check the result in Storybook and a live page.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents; installed under .agents/ (shared by several agents); mentions AGENTS.md.

This is P2ERGmbH/agentic-coding's own configuration. It tells Claude Code and Codex how to work on agentic-coding itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything agentic-coding configures →

Reuse

Borrowing it

Nothing to install: this file belongs to P2ERGmbH/agentic-coding. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/P2ERGmbH/agentic-coding/main/.agents/skills/figma-implement/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/P2ERGmbH/agentic-coding

Made for: Claude Code, Codex.

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

agentmods badge for figma-implement

README.md
[![agentmods](https://agentmods.dev/badge/skills/p2ergmbh/agentic-coding/figma-implement/github.svg)](https://agentmods.dev/skills/p2ergmbh/agentic-coding/figma-implement)
Your own site
<a href="https://agentmods.dev/skills/p2ergmbh/agentic-coding/figma-implement"><img src="https://agentmods.dev/badge/skills/p2ergmbh/agentic-coding/figma-implement/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.

agentmods 80×15 button for figma-implement

Your own site · 80×15
<a href="https://agentmods.dev/skills/p2ergmbh/agentic-coding/figma-implement"><img src="https://agentmods.dev/badge/skills/p2ergmbh/agentic-coding/figma-implement.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,746 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00041 $0.04746
Opus 5.5 $0.00016 $0.01898
Sonnet 5.5 $0.00008 $0.00949
Haiku 4.5 $0.00004 $0.00475

Measured 2mo ago against content hash 4f5c96795eda, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

figma-implement 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 2mo ago.

The scan reads SKILL.md. This mod also ships 3 executable files (scripts/compile-component-map.mjs, scripts/generate-figma-css.mjs, scripts/parse-figma-vars.mjs), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

.agents/skills/figma-implement/SKILL.md · 294 lines

How it starts

The opening of the file, as written. The whole thing — 294 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Figma Layout Implementation Workflow

This skill guides you through implementing precise Figma designs by parsing Figma design tokens (JSON + CSS) into Tailwind utility classes, building a component-to-layer map, and verifying via Storybook and live page testing.

Trigger

Use this skill when the user asks to "implement a Figma design", "convert Figma to Tailwind", "use the reusable figma implementation solution", or "build a component from a Figma frame".


Phase 1: Requirements Gathering

Before any download or implementation work, gather the following using ask_user_question:

1.1 Figma Source

Ask the user for:

  • Figma URL or file key + node ID — the exact frame/layer to implement.
  • Component name — the kebab-case name for the React component (e.g., product-card).

1.2 Search for Existing Matching Components

After receiving the component name, search the codebase for existing components that might correspond:

  • Search for files/components matching the name (glob for **/[ComponentName]*.tsx)
  • Search for existing Figma references in .stories.tsx files that reference a similar URL/node
  • Search for existing @figma-layer annotations that mention the layer name

If matches are found, you MUST explicitly present the exact matching component files that were found to the user in the chat interface. Propose updating the existing component rather than creating a new one.

1.3 Implementation Mode

When an existing component is found, you MUST explicitly ask the user if they want a pixel-perfect design or an incremental layout improvement (e.g., "Do you want a pixel-perfect match or an incremental layout improvement?"). Do not make this decision without seeking their explicit choice.

Mode Description
New component The component doesn't exist yet — create from scratch.
Improve existing layout The component exists; adjust spacing, colors, typography to better match the design while keeping the current structure.
Pixel-perfect replacement The component exists but should be rewritten entirely to match the Figma frame exactly, discarding the current layout in favor of the figma design.

Read the full file on GitHub · 294 lines

Files

What ships with it

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

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. 2mo ago First seen · 294 lines · 41 tokens per session scan A 4f5c96795eda

Subscribe to this mod's changes

figma-implement is a skill published in the GitHub repository P2ERGmbH/agentic-coding (9 stars, last pushed 4mo ago), licensed MIT. It adds 41 tokens to every session and 4,746 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

anti-slop-design

Autonomous Principal Design Technologist. Cures vibe-coded software from AI frontend slop using curated token archetypes and 7-axis quality gating.

sickn33/agentic-awesome-skills · 34 tokens

chakra-ui-builder

Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…

chakra-ui/chakra-ui · 214 tokens

visual-ralph

Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ultragoal with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.

Yeachan-Heo/oh-my-codex · 52 tokens

frontend-ui-dark-ts

Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations. Use when creating dashboards, admin panels, or data-rich interfaces with a refined dark aesthetic.

microsoft/skills · 48 tokens

open-design-setup

Prepare or repair a project's prototyping environment so open-design can build prototypes with the project's own component library and render them through the project's toolchain. Use when the library target is needed and docs/design/prototyping.md is missing, stale, or failing; excludes HTML-only design work and…

compozy/compozy · 67 tokens

frontend-visual-qa

Audits rendered UI and specific task/object-link handoffs; excludes ordinary source citations alone. Audits already-rendered UI and Markdown/Obsidian image layout — web app, deck/slide, dashboard, design-system, or Electron/native app — via real-browser/native-app journeys and a Playwright sweep. Use after UI…

daymade/claude-code-skills · 125 tokens