Claude Skills
The open format is called Agent Skills and works in Claude Code, Codex, Cursor and other agents — most people know it as Claude Skills.
Every Agent Skill we could find on GitHub, deduplicated by content. 86 696 files from 2 113 authors, of which 68 413 are unique — the rest is the same skill repackaged into someone else's repository. For each one: what it weighs in tokens, whether it ships runnable scripts, and which MCP servers it needs.
> Finds fast-growing international (imported) products ACROSS ALL Mercado Livre (Brasil) categories, using JoomPulse, and returns them as one product table that includes each item's category, with price, estimated weekly sales and revenue, rating, time on air, shipping, listing type, seller medal, and a JoomPulse link per item. Use it when a seller wants rising imported products international products", "imported products that are taking off", "cross-border winners across all categories", and the pt-BR equivalents "produtos internacionais em alta", "produtos importados crescendo rápido", "produtos internacionais que mais crescem em todas as categorias". Sales and revenue are JoomPulse estimates, not real transactions. For the same search limited to one category, use the single-category international skill.
> Monitors one Mercado Livre (Brasil) category's aggregate health via JoomPulse — estimated sales, number of products and catalog products, active sellers, the seller-medal distribution, and the monopolization level. Each run builds today's snapshot table and offers it for download; to see what changed, the user sends a table from a previous period and the skill shows the metric-by-metric difference. The baseline is whatever table the user this category", "track category sales and sellers", and the pt-BR "monitorar esta categoria", "o que mudou na categoria", "comparar a categoria com o período anterior". Sales and revenue are JoomPulse estimates, not real transactions. To track one named product over time use the product-change-monitor skill; for a one-shot market-size or opportunity snapshot use the category-opportunity-index skill.
> Monitors how one or a few Mercado Livre products or listings changed over a period — by default week over week. Use it when a user wants to track how a named product changes over time, given a Mercado Livre link, a JoomPulse link, a Mercado Livre listing identifier, or a catalog product identifier. It returns week ago for price, rating, and review count, plus the current estimated weekly sales and revenue, logistics, listing type, seller medal, and time on air, with price changes", "what changed this week", "did the price drop", and the pt-BR equivalents "monitorar este produto", "acompanhar este anúncio", "o preço caiu", "variação de avaliações". Sales and revenue are JoomPulse estimates, not real transactions; price, rating, and reviews are real history. For point-in-time product and competitor analysis, use the single-product analysis skill.
> Ranks the brands within one Mercado Livre (Brasil) category by estimated weekly revenue and tracks how each brand's position changes between periods, using JoomPulse. Each run builds today's brand-ranking table and offers it for download; to see how positions moved, the user sends a brand table from a previous period and the skill shows each brand's movement (rose, fell, new, or out). The baseline is whatever table the user supplies — no hidden session memory. Use it to see the top brands in a category and which are rising or falling. the pt-BR "principais marcas da categoria", "ranking de marcas", "quais marcas estão crescendo". Mercado Livre (Brasil) only; sales and revenue are JoomPulse estimates, not real transactions. To rank sellers (shops) rather than brands use the top-sellers-in-category skill; for category market size use the category-opportunity-index skill.
> Finds product listings that appear to represent the same real-world product as a reference item. Use this skill when a user wants to find duplicate listings, match a product across listings, identify identical products by title or URL, compare product photos against marketplace listings, or find the same product on Mercado Livre.
> Finds fast-growing international (imported) products inside ONE chosen Mercado Livre (Brasil) category, using JoomPulse, and returns them as a product table with price, estimated weekly sales and revenue, rating, reviews, time on air, shipping, listing type and seller medal, a JoomPulse link per item, and a pointer to JoomPro for sourcing. Use it when a seller wants the trending products in this category", "fast-growing imported products", and the pt-BR equivalents "produtos internacionais em alta nessa categoria", "produtos importados que mais crescem", "achados internacionais para importar". Sales and revenue are JoomPulse estimates, not real transactions. For the same search across all categories at once, use the all-categories international skill.
> Snapshot tracker for one Mercado Livre (Brasil) seller via JoomPulse — estimated monthly revenue and sales, listing count, sales trend, reputation, seller medal, categories covered, and cancellation rate. Each run builds today's snapshot table and offers it for download; to see what changed, the user sends the seller's table from a previous period and the skill shows the metric-by-metric difference (old → new). The baseline is whatever table the user supplies — no hidden session memory. Use it to track one specific seller over time. "compare this seller with last period", and the pt-BR "monitorar este vendedor", "acompanhar esta loja", "o que mudou nesse vendedor". Sales and revenue are JoomPulse estimates, not real transactions. To rank many sellers in a category and track how that ranking moves, use the top-sellers-in-category skill. Mercado Livre (Brasil) only.
> Ranks the top sellers in one Mercado Livre (Brasil) category by estimated average monthly monthly sales and revenue, 365-day completed sales, cancellation rate, sales trend, brands, product counts, international shipping, and listing-type counts, with a JoomPulse link each. category and it shows each seller's movement (rose / fell / new) plus the biggest movers. revenue", and the pt-BR "principais vendedores da categoria", "maiores lojas da categoria", "quem mais vende nessa categoria". Sales and revenue are JoomPulse estimates, not real transactions. To monitor one seller over time use the seller-overview-tracker skill; to rank brands use the top-brand-position-tracker skill.
> Lists the top trending search keywords for one Mercado Livre (Brasil) category — the real Mercado Livre search-trends ranking of what shoppers look for — with each keyword's rank and how many products compete for it. Use it when a seller wants to know what people search in their niche, which terms to put in titles category", "trending search terms", "what do people search for", "best keywords for my listings", and the pt-BR equivalents "palavras-chave mais buscadas", "termos em alta na categoria", "o que as pessoas pesquisam", "melhores palavras-chave para meus anúncios". The keywords and ranks are real search-trend data, not estimates. For category market size and opportunity, use the category-opportunity-index skill; for ranking the sellers in a category, use the top-sellers-in-category skill.
> Finds products with no brand (unbranded / no-name / generic) in one Mercado Livre (Brasil) category via JoomPulse — an opening to enter with your own brand / private label, since buyers there aren't anchored to a brand name. Asks for a category, lists the active no-brand listings ranked by estimated weekly demand, and returns a product table (price, estimated weekly sales and revenue, rating, reviews, time on air, shipping, listing type, seller brand", "private-label opportunities", and the pt-BR "produtos sem marca", "genéricos que vendem", "oportunidade de marca própria". Sales and revenue are JoomPulse estimates, not real transactions. NOT for ranking brands (use top-brand-position-tracker), brand-new listings (use new-growing-products-in-category), high-demand low-rated products (use high- demand-low-quality-finder), or niches without platinum sellers (use uncontested-niche- finder).
> Finds low-competition niche products on Mercado Livre (Brasil) — active listings in deep sub-categories (deeper than the third level) of a chosen category that have no platinum seller at all, surfaced via JoomPulse. Use it when a seller wants uncontested niches, gaps without strong incumbents, or where to enter without fighting a dominant platinum seller. platinum", "nicho pouco disputado", "subcategorias sem platinum". It returns one table of niche products, each with a competition signal (number of sellers) and a JoomPulse link. Sales and revenue are JoomPulse estimates, not real transactions; price, rating, and reviews are real history. For one product and its competitors use the ml-product-analysis skill; for fast-growing deep categories rather than products use the growing-leaf-category-tracker skill.
Core agent-browser usage guide. Read this before running any agent-browser commands. Covers the snapshot-and-ref workflow, navigating pages, interacting with elements (click, fill, type, select), extracting text and data, taking screenshots, managing tabs, handling forms and auth, waiting for content, running multiple browser sessions in parallel, and troubleshooting common failures. Use when the user asks to interact with a website, fill a form, click something, extract data, take a screenshot, log into a site, test a web app, or automate any browser task.
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", or "switch to --preset".
>- The moi workspace — the web UI the user chats from, extended with agent-authored applets (widgets, views) plus theme & config. Read this FIRST in two cases. (a) A message carries a hidden nothing else says so. (b) The user uses moi vocab — workspace, applet, widget, view, scratchpad, dashboard, or a `moi` command — or asks to build, edit, customize, or theme the workspace UI or its layout.
Release moi-computer to npm — verify locally, hand off to the gated GitHub Actions workflow, then verify the published package. Defaults to a `next` preview; pass `stable` for a `latest` release. Use when the user asks to publish, release, ship a version, or cut a dev preview.
SLASH-COMMAND-ONLY. Invoke ONLY when the user explicitly types the literal `/watch-video` slash command. Never auto-trigger on phrases like "watch this video," "summarize this video," "take notes on this video," or on a bare YouTube URL. For ad-hoc YouTube questions, fetch the transcript directly (YouTube page or yt-dlp) and skim — do not run this heavyweight pipeline.
| Meta Media Buyer — publish, manage, and analyze Meta (Facebook/Instagram) ad campaigns via the Marketing API. Includes guided setup for first-time users. USE WHEN user says "meta ads", "facebook ads", "instagram ads", "publish ads", "create campaign", "launch campaign", "ad performance", "ROAS", "which ad is winning", "ad spend", "campaign metrics", "pause campaign", "resume campaign", "upload ad images", "ad set performance", "creative performance", "set up meta ads", "connect meta ads", "meta ads setup", or needs to publish, manage, or analyze paid Meta advertising campaigns.
One-click starter pack and curator for Codex/agent skills. Use when a beginner wants a high-quality default skills setup across common needs, when the user asks to install useful skills without researching them one by one, or when the installed skills library needs auditing, deduplication, conflict resolution, global-vs-backup selection, restore planning, or a written skills inventory.
Repo-local meta-skill for improving Xiaobai Skills over time. Use after significant project changes, user feedback, install failures, promotion experiments, or repeated workflow friction to update AGENTS.md, capture project-specific gotchas, or propose new repo-local skills. Do not use globally or after every small task.
| to restate the user's intent to align before working, then diagnose the root cause and reuse the domain's mature, established practices before improvising. Clear prompts pass through untouched.
> Query `.belief_map.sexp` before non-trivial code changes to find module boundaries, dependencies, blast radius, and the minimal files to read. Use for architecture discovery, impact analysis, and boundary checks.
This skill should be used when writing Ruby gems following Andrew Kane's proven patterns and philosophy. It applies when creating new Ruby gems, refactoring existing gems, designing gem APIs, or when clean, minimal, production-ready Ruby library code is needed. Triggers on requests like "create a gem", "write a Ruby library", "design a gem API", or mentions of Andrew Kane's style.
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...
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>
Run comprehensive agent-native architecture review with scored principles
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.
Use when needing to look up book content, find a book by title/author, download an ebook, or reference material from a published book. Triggers on book lookups, ebook downloads, "find the book", "get the PDF/EPUB of". Downloads produce PDF/EPUB/MOBI files - use ebook-extractor skill to convert to text.
Use this agent when you need to analyze code changes from an architectural perspective, evaluate system design decisions, or ensure that modifications align with established architectural patterns. This includes reviewing pull requests for architectural compliance, assessing the impact of new features on system structure, or validating that changes maintain proper component boundaries and design principles. <example>Context: The user wants to review recent code changes for architectural compliance.\\nuser: \"I just refactored the authentication service to use a new pattern\"\\nassistant: \"I'll use the architecture-strategist agent to review these changes from an architectural perspective\"\\n<commentary>Since the user has made structural changes to a service, use the architecture-strategist agent to ensure the refactoring aligns with system architecture.</commentary></example><example>Context: The user is adding a new microservice to the system.\\nuser: \"I've added a new notification service that integrates with...
>- Migrate docs from bd (beads) to br (beads_rust). Use when updating AGENTS.md, converting bd commands, "bd sync" → "br sync --flush-only", or beads migration.
Render Mermaid diagrams as readable ASCII/Unicode art in the terminal (from .mmd/.mermaid files, stdin, or Markdown ```mermaid fences). Use when installing or using lukilabs/beautiful-mermaid, creating a CLI renderer for Mermaid-to-ASCII output, previewing Mermaid diagrams in terminal, or extracting/rendering Mermaid blocks from Markdown files.
This skill should be used before implementing features, building components, or making changes. It guides exploring user intent, approaches, and design decisions before planning. Triggers on "let's brainstorm", "help me think through", "what should we build", "explore approaches", ambiguous feature requests, or when the user's request has multiple valid interpretations that need clarification.
This skill should be used when working with AssemblyAI’s Speech-to-Text and LLM Gateway APIs, especially for streaming/live transcription, meeting notetakers, and voice agents that need low-latency transcripts and audio analysis.
Use when user asks to search the web, look something up online, find current/recent/latest information, or needs cited answers. Triggers on "search", "look up", "find out about", "what is the current/latest", image searches, news lookups. NOT for searching code/files—only for web/internet searches.
Use this agent when you need to research and gather external best practices, documentation, and examples for any technology, framework, or development practice. This includes finding official documentation, community standards, well-regarded examples from open source projects, and domain-specific conventions. The agent excels at synthesizing information from multiple sources to provide comprehensive guidance on how to implement features or solve problems according to industry standards. <example>Context: User wants to know the best way to structure GitHub issues for their Rails project. user: \"I need to create some GitHub issues for our project. Can you research best practices for writing good issues?\" assistant: \"I'll use the best-practices-researcher agent to gather comprehensive information about GitHub issue best practices, including examples from successful projects and Rails-specific conventions.\" <commentary>Since the user is asking for research on best practices, use the best-practices-researcher a...
Creates and reviews CLAUDE.md configuration files for Claude Code. Applies HumanLayer guidelines including instruction budgets (~50 user-level, ~100 project-level), WHAT/WHY/HOW framework, and progressive disclosure. Identifies anti-patterns like using Claude as a linter for style rules.
Use this agent when you receive a bug report or issue description and need to verify whether the reported behavior is actually a bug. This agent will attempt to reproduce the issue systematically, validate the steps to reproduce, and confirm whether the behavior deviates from expected functionality. <example>\\nContext: The user has reported a potential bug in the application.\\nuser: \"Users are reporting that the email processing fails when there are special characters in the subject line\"\\nassistant: \"I'll use the bug-reproduction-validator agent to verify if this is an actual bug by attempting to reproduce it\"\\n<commentary>\\nSince there's a bug report about email processing with special characters, use the bug-reproduction-validator agent to systematically reproduce and validate the issue.\\n</commentary>\\n</example>\\n<example>\\nContext: An issue has been raised about unexpected behavior.\\nuser: \"There's a report that the brief summary isn't including all emails from today\"\\nassistant: \"Let me launch the b...
Create or edit Claude Code skills with expert guidance on structure and best practices
Use this agent when you need a final review pass to ensure code changes are as simple and minimal as possible. This agent should be invoked after implementation is complete but before finalizing changes, to identify opportunities for simplification, remove unnecessary complexity, and ensure adherence to YAGNI principles. Examples: <example>Context: The user has just implemented a new feature and wants to ensure it's as simple as possible. user: \"I've finished implementing the user authentication system\" assistant: \"Great! Let me review the implementation for simplicity and minimalism using the code-simplicity-reviewer agent\" <commentary>Since implementation is complete, use the code-simplicity-reviewer agent to identify simplification opportunities.</commentary></example> <example>Context: The user has written complex business logic and wants to simplify it. user: \"I think this order processing logic might be overly complex\" assistant: \"I'll use the code-simplicity-reviewer agent to analyze the complexity...
Capture solved problems as categorized documentation with YAML frontmatter for fast lookup
Expert guidance for creating, writing, and refining Claude Code Skills. Use when working with SKILL.md files, authoring new skills, improving existing skills, or understanding skill structure and best practices.
Use when writing, reviewing, or refactoring code. Apply when naming variables or functions, structuring classes, handling errors, writing tests, or when code feels complex or hard to understand. Based on Robert C. Martin's Clean Code.
Create engaging changelogs for recent merges to main branch
Use this agent when reviewing PRs that touch database migrations, data backfills, or any code that transforms production data. This agent validates ID mappings against production reality, checks for swapped values, verifies rollback safety, and ensures data integrity during schema changes. Essential for any migration that involves ID mappings, column renames, or data transformations. <example>Context: The user has a PR with database migrations that involve ID mappings. user: \"Review this PR that migrates from action_id to action_module_name\" assistant: \"I'll use the data-migration-expert agent to validate the ID mappings and migration safety\" <commentary>Since the PR involves ID mappings and data migration, use the data-migration-expert to verify the mappings match production and check for swapped values.</commentary></example> <example>Context: The user has a migration that transforms enum values. user: \"This migration converts status integers to string enums\" assistant: \"Let me have the data-migration-ex...
Use this agent when you need to review database migrations, data models, or any code that manipulates persistent data. This includes checking migration safety, validating data constraints, ensuring transaction boundaries are correct, and verifying that referential integrity and privacy requirements are maintained. <example>Context: The user has just written a database migration that adds a new column and updates existing records. user: \"I've created a migration to add a status column to the orders table\" assistant: \"I'll use the data-integrity-guardian agent to review this migration for safety and data integrity concerns\" <commentary>Since the user has created a database migration, use the data-integrity-guardian agent to ensure the migration is safe, handles existing data properly, and maintains referential integrity.</commentary></example> <example>Context: The user has implemented a service that transfers data between models. user: \"Here's my new service that moves user data from the legacy_users table...
Enhance a plan with parallel research agents for each section to add depth, best practices, and implementation details
Use when designing databases for data-heavy applications, making schema decisions for performance, choosing between normalization and denormalization, selecting storage/indexing strategies, planning for scale, or evaluating OLTP vs OLAP trade-offs. Also use when encountering N+1 queries, ORM issues, or concurrency problems.
Validate and prepare documentation for GitHub Pages deployment
Systematic debugging that identifies root causes rather than treating symptoms. Uses sequential thinking for complex analysis, web search for research, and structured investigation to avoid circular reasoning and whack-a-mole fixes.
Use this agent when a PR touches production data, migrations, or any behavior that could silently discard or duplicate records. Produces a concrete pre/post-deploy checklist with SQL verification queries, rollback procedures, and monitoring plans. Essential for risky data changes where you need a Go/No-Go decision. <example>Context: The user has a PR that modifies how emails are classified. user: \"This PR changes the classification logic, can you create a deployment checklist?\" assistant: \"I'll use the deployment-verification-agent to create a Go/No-Go checklist with verification queries\" <commentary>Since the PR affects production data behavior, use deployment-verification-agent to create concrete verification and rollback plans.</commentary></example> <example>Context: The user is deploying a migration that backfills data. user: \"We're about to deploy the user status backfill\" assistant: \"Let me create a deployment verification checklist with pre/post-deploy checks\" <commentary>Backfills are high-risk de...
Use this agent when you need to verify that a UI implementation matches its Figma design specifications. This agent should be called after code has been written to implement a design, particularly after HTML/CSS/React components have been created or modified. The agent will visually compare the live implementation against the Figma design and provide detailed feedback on discrepancies.\\n\\nExamples:\\n- <example>\\n Context: The user has just implemented a new component based on a Figma design.\\n user: \"I've finished implementing the hero section based on the Figma design\"\\n assistant: \"I'll review how well your implementation matches the Figma design.\"\\n <commentary>\\n Since UI implementation has been completed, use the design-implementation-reviewer agent to compare the live version with Figma.\\n </commentary>\\n </example>\\n- <example>\\n Context: After the general code agent has implemented design changes.\\n user: \"Update the button styles to match the new design system\"\\n assistant: \"I've updated the butto...
Use this agent PROACTIVELY when design work isn't coming together on the first attempt. If you've made 1-2 design changes and the result still feels off, suggest using this agent with 5x or 10x iterations for deeper refinement. This agent takes screenshots, analyzes what's not working, implements improvements, and repeats N times to systematically fix design issues. Perfect when colors feel wrong, layouts aren't balanced, or the overall aesthetic needs work that single changes can't achieve. <example>Context: User asks to change button color but result still looks off. user: \"Change the button to blue\" assistant: [makes change, takes screenshot] \"The button is now blue, but I notice the overall color balance still feels off. Would you like me to use the design-iterator agent with 5 iterations to systematically improve the color harmony and visual balance?\" <commentary>PROACTIVE USE: After a simple change doesn't fully resolve the design issue, suggest the design-iterator to do deeper work.</commentary></ex...
Use when designing software architecture, refactoring code structure, solving recurring design problems, or when code exhibits symptoms like tight coupling, rigid hierarchies, scattered responsibilities, or difficult-to-test components. Also use when choosing between architectural approaches or reviewing code for structural improvements.
This skill should be used when writing Ruby and Rails code in DHH's distinctive 37signals style. It applies when writing Ruby code, Rails applications, creating models, controllers, or any Ruby file. Triggers on Ruby/Rails code generation, refactoring requests, code review, or when the user mentions DHH, 37signals, Basecamp, HEY, or Campfire style. Embodies REST purity, fat models, thin controllers, Current attributes, Hotwire patterns, and the "clarity over cleverness" philosophy.
This skill should be used when working with DSPy.rb, a Ruby framework for building type-safe, composable LLM applications. Use this when implementing predictable AI features, creating LLM signatures and modules, configuring language model providers (OpenAI, Anthropic, Gemini, Ollama), building agent systems with tools, optimizing prompts, or testing LLM-powered functionality in Ruby applications.
Use this agent when you need a brutally honest Rails code review from the perspective of David Heinemeier Hansson. This agent excels at identifying anti-patterns, JavaScript framework contamination in Rails codebases, and violations of Rails conventions. Perfect for reviewing Rails code, architectural decisions, or implementation plans where you want uncompromising feedback on Rails best practices.\\n\\n<example>\\nContext: The user wants to review a recently implemented Rails feature for adherence to Rails conventions.\\nuser: \"I just implemented a new user authentication system using JWT tokens and a separate API layer\"\\nassistant: \"I'll use the DHH Rails reviewer agent to evaluate this implementation\"\\n<commentary>\\nSince the user has implemented authentication with patterns that might be influenced by JavaScript frameworks (JWT, separate API layer), the dhh-rails-reviewer agent should analyze this critically.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: The user is planning a new Rails feature and wan...
Use when needing to scrape documentation websites into markdown for AI context. Triggers on "scrape docs", "download documentation", "get docs for [library]", or creating local copies of online documentation. CRITICAL - always analyze sitemap first before scraping.
Use when user wants to extract text from ebooks (EPUB, MOBI, PDF). Use for converting ebooks to plain text for analysis, processing, or reading. Handles all common ebook formats.
Use this agent when you need to review and edit text content to conform to Every's specific style guide. This includes reviewing articles, blog posts, newsletters, documentation, or any written content that needs to follow Every's editorial standards. The agent will systematically check for title case in headlines, sentence case elsewhere, company singular/plural usage, overused words, passive voice, number formatting, punctuation rules, and other style guide requirements.
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...
Record a video walkthrough of a feature and add it to the PR description
Claude Skills — questions
Answers built from the skills we actually parsed.