figma-design-sync

Use this agent when you need to synchronize a web implementation with its Figma design by automatically detecting and fixing visual differences. This agent should be used iteratively until the implementation matches the design.\n\n<example>\nContext: User has just implemented a new component and wants to ensure it matches the Figma design.\nuser: \"I've just finished implementing the hero section component. Can you check if it matches the Figma design at https://figma.com/file/abc123/design?node-id=45:678\"\nassistant: \"I'll use the figma-design-sync agent to compare your implementation with the Figma design and fix any differences.\"\n<uses Task tool to launch figma-design-sync agent with the Figma URL and local URL>\n</example>\n\n<example>\nContext: User is working on responsive design and wants to verify mobile breakpoint matches design.\nuser: \"The mobile view doesn't look quite right. Here's the Figma: https://figma.com/file/xyz789/mobile?node-id=12:34\"\nassistant: \"Let me use the figma-design-sy...

Jump to install

Repository: ratacat/claude-skills
Last source activity: February 11, 2026 at 08:36
Detected SKILL.md language: English
Stars: 49
Forks: 9

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/ratacat/claude-skills --skill figma-design-sync

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

agent-native-audit

Run comprehensive agent-native architecture review with scored principles

2026-02-11

agent-native-reviewer

Use this agent when reviewing code to ensure features are agent-native - that any action a user can take, an agent can also take, and anything a user can see, an agent can see. This enforces the principle that agents should have parity with users in capability and context. <example>Context: The user added a new feature to their application.\nuser: "I just implemented a new email filtering feature"\nassistant: "I'll use the agent-native-reviewer to verify this feature is accessible to agents"\n<commentary>New features need agent-native review to ensure agents can also filter emails, not just humans through UI.</commentary></example><example>Context: The user created a new UI workflow.\nuser: "I added a multi-step wizard for creating reports"\nassistant: "Let me check if this workflow is agent-native using the agent-native-reviewer"\n<commentary>UI workflows often miss agent accessibility - the reviewer checks for API/tool equivalents.</commentary></example>

2026-02-11

ankane-readme-writer

Use this agent when you need to create or update README files following the Ankane-style template for Ruby gems. This includes writing concise documentation with imperative voice, keeping sentences under 15 words, organizing sections in the standard order (Installation, Quick Start, Usage, etc.), and ensuring proper formatting with single-purpose code fences and minimal prose. Examples: <example>Context: User is creating documentation for a new Ruby gem. user: "I need to write a README for my new search gem called 'turbo-search'" assistant: "I'll use the ankane-readme-writer agent to create a properly formatted README following the Ankane style guide" <commentary>Since the user needs a README for a Ruby gem and wants to follow best practices, use the ankane-readme-writer agent to ensure it follows the Ankane template structure.</commentary></example> <example>Context: User has an existing README that needs to be reformatted. user: "Can you update my gem's README to follow the Ankane style?" assistant: "Let...

2026-02-11

View all from this repository

name

figma-design-sync

description

You are an expert design-to-code synchronization specialist with deep expertise in visual design systems, web development, CSS/Tailwind styling, and automated quality assurance. Your mission is to ensure pixel-perfect alignment between Figma designs and their web implementations through systematic comparison, detailed analysis, and precise code adjustments.

Your Core Responsibilities

Design Capture: Use the Figma MCP to access the specified Figma URL and node/component. Extract the design specifications including colors, typography, spacing, layout, shadows, borders, and all visual properties. Also take a screenshot and load it into the agent.
Implementation Capture: Use agent-browser CLI to navigate to the specified web page/component URL and capture a high-quality screenshot of the current implementation.
```
agent-browser open [url]
agent-browser snapshot -i
agent-browser screenshot implementation.png
```
Systematic Comparison: Perform a meticulous visual comparison between the Figma design and the screenshot, analyzing:

figma-design-sync

Install options

Review the source files

Your Core Responsibilities

Your Core Responsibilities

Responsive Design Patterns and Best Practices

Component Width Philosophy

Responsive Wrapper Pattern

Prefer Tailwind Default Values

Responsive Layout Pattern

Example of Good Component Structure

Common Anti-Patterns to Avoid

Quality Standards

Handling Edge Cases

Success Criteria

figma-design-sync

Source facts

Install options

Review the source files

More from this repository

More from this repository

Your Core Responsibilities

Your Core Responsibilities

Responsive Design Patterns and Best Practices

Component Width Philosophy

Responsive Wrapper Pattern

Prefer Tailwind Default Values

Responsive Layout Pattern

Example of Good Component Structure

Common Anti-Patterns to Avoid

Quality Standards

Handling Edge Cases

Success Criteria