Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From expo-rn-plugin
Compare the current screen implementation against its Figma design and fix visual discrepancies. Use after a significant UI change, new screen, redesign, or design handoff — not for every small tweak.
npx claudepluginhub ksairi-org/claude --plugin expo-rn-pluginHow this skill is triggered — by the user, by Claude, or both
Slash command
/expo-rn-plugin:figma <figma_url_or_node_id><figma_url_or_node_id>The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Run a Figma design sync for the current screen using the Figma MCP.
Guides Payload CMS config (payload.config.ts), collections, fields, hooks, access control, APIs. Debugs validation errors, security, relationships, queries, transactions, hook behavior.
Implements vector databases with Pinecone, Weaviate, Qdrant, Milvus, pgvector for semantic search, RAG, recommendations, and similarity systems. Optimizes embeddings, indexing, and hybrid search.
Share bugs, ideas, or general feedback.
Run a Figma design sync for the current screen using the Figma MCP.
Only invoke this after a significant UI change — a new screen, a redesign, or after a design handoff. Do not run on every small tweak.
Get the Figma design — use mcp__figma__get_figma_data with $ARGUMENTS as the node URL or ID to fetch the design spec
Identify the implementation file — find the screen component that corresponds to the Figma frame (use get_routes if unsure which file to look at)
Compare — list the visual differences between the Figma spec and the current implementation: spacing, typography, colors, layout, component usage
Fix — apply corrections using Tamagui design tokens from src/theme/:
$token referencessrc/theme/themes.ts for valid token names before using oneget_components to find existing components before creating new onesDownload assets if needed — use mcp__figma__download_figma_images for icons or images that need exporting
Report — summarise what was changed and what (if anything) could not be matched due to missing tokens or components
src/theme/, flag it to the user instead of approximatingtsc --noEmit after changes to confirm no type errors