Stats
Actions
Tags
From nexus
Auto-triggers when the user mentions Figma-related tasks like inspecting designs, extracting design tokens, getting screenshots, searching design systems, creating or editing Figma files, generating diagrams, or working with Code Connect. Trigger phrases include "figma", "design tokens", "design system", "component mapping", "code connect", "figjam", "diagram", "mockup", "frame", "layer", "variant", "screenshot of design", and Figma URL patterns like "figma.com/design/".
How this skill is triggered — by the user, by Claude, or both
Slash command
/nexus:figma-workflowThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill activates when the user mentions Figma-related work in conversation.
This skill activates when the user mentions Figma-related work in conversation.
Invoke /nexus:figma with the user's request. The figma command handles everything — MCP setup detection, plan-based rate-limit gating, and all Figma workflows.
npx claudepluginhub piyu7994/nexus --plugin nexusBridges Designpowers specs and Figma in both directions: pushes visual decisions or code into Figma frames, pulls Figma files in for review or design-system source. Falls back to HTML prototype when Figma is unavailable.
Generates Figma components or screens by compiling a CSpec into a scene graph and executing it via MCP. Use when the user asks to make, design, or build new UI in Figma.
Builds or updates full-page screens, modals, dialogs, drawers, sidebars, and panels in Figma by reusing published design system components, variables, and styles instead of drawing primitives with hardcoded values.