JohnWayneeee/ai-agent-skills / skills/figma-pencil-fsd-tailwind4
figma-pencil-fsd-tailwind4
VerifiedConvert Figma or Pencil designs into production-ready frontend code using Feature-Sliced Design and Tailwind CSS v4. Use when translating designs into code, extracting tokens, mapping UI to FSD layers (shared / entities / features / widgets / pages / app-shell / app), enforcing Server vs Client boundaries when applicable, or validating design-to-code fidelity.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 9.1 KB |
| references/accessibility-checklist.md | markdown | 2.8 KB |
| references/example-mapping.md | markdown | 4.2 KB |
| references/figma-mcp-workflow.md | markdown | 3.4 KB |
| references/fsd-mapping.md | markdown | 4.5 KB |
| references/pencil-workflow.md | markdown | 2.8 KB |
| references/project-contracts.md | markdown | 3.4 KB |
| references/rsc-boundaries.md | markdown | 2.9 KB |
| references/tailwind-tokens.md | markdown | 3.8 KB |
references/accessibility-checklist.md
View on GitHub# Accessibility Checklist
Designs rarely document accessibility. Treat this checklist as mandatory when translating any design into code.
## Semantic HTML
- Use native `<button>` for actions, `<a>` for navigation. Never attach `onClick` to a `<div>` or `<span>` for primary interaction.
- Use native form controls (`<input>`, `<select>`, `<textarea>`) inside a `<form>` with proper labels.
- Use `<nav>`, `<main>`, `<header>`, `<footer>`, `<aside>` for landmarks. Exactly one `<main>` per page.
- Headings form a single hierarchical outline. One `<h1>` per page; do not skip levels for visual sizing.
## Interactive elements
- Every interactive element is reachable by Tab in a logical order.
- Visible focus state on every interactive element. Use a token-backed ring (`focus-visible:ring-2 focus-visible:ring-ring focus-visible:ring-offset-2`), not `outline: none`.
- Hover-only affordances must have a non-hover equivalent (focus, persistent state on touch).
- Disabled state communicates via `disabled` attribute on form controls or `aria-disabled` on buttons that intentionally remain focusable.
## Labels and names
- Icon-only buttons must have `aria-label` or visually hidden text.
- Form fields have an associated `<label>` (via `htmlFor`/`id` or wrapping). Placeholder text is not a label.
- Images use `alt`. Decorative images use `alt=""`. Never omit the attribute.
## ARIA
- Use ARIA only when semantic HTML is insufficient. Native first.
- For composite widgets (combobox, tabs, dialog, menu), prefer a tested primitive library (Radix, shadcn/ui, Headless UI) over hand-rolled ARIA.
- Live regions (`aria-live="polite"`) for async feedback (toasts, validation, status updates).
## Color and contrast
- Body text contrast at minimum 4.5:1 against its background. Large text minimum 3:1.
- Do not rely on color alone to communicate state. Pair color with icon, text, or shape.
- Verify contrast for both light and dark themes.
## Keyboard
- Modals trap focus while open and restore focus on close.
- Escape closes dialogs, popovers, command menus.
- Arrow-key navigation inside composite widgets (tabs, menus, radio groups, listboxes).
## Motion
- Honor `prefers-reduced-motion`. Disable non-essential animation when the user has requested reduced motion.
- Auto-playing media has a pause control.
## States to implement for every interactive component
- default
- hover
- focus-visible
- active / pressed
- disabled
- loading (if the component triggers async work)
- error (if the component can produce one)
## Quick failures to look for
- `<div onClick={...}>` instead of `<button>`.
- `outline: none` without a replacement focus ring.
- Icon-only buttons without `aria-label`.
- Images without `alt`.
- Modals that do not trap focus or do not close on Escape.
- Color-only error indication (red text without an icon or message).
- Skipped heading levels for visual weight.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies 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. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |