from vapor-ui35
Design-system-aware assistant for Vapor UI: component docs, icon lookup, mockup generation, and Figma-to-code conversion producing production-ready Vapor UI Rea
Vapor UI Design System skill equips the agent to answer component-level questions, generate UI mockups, and convert Figma designs into production-ready Vapor UI React code. It exposes scripts to detect library versions, list components, fetch component props/examples, and map Figma auto-layout and design tokens into Vapor UI primitives so the agent can output copy-pasteable JSX. Use cases include answering "how to use" queries, generating mockups from a brief, and transforming Figma frames into componentized, tokenized code.
Invoke this skill when a user asks about Vapor UI components (e.g. "Button", "Input", "Modal"), requests icon lookup, asks for mockup generation, or provides a Figma URL and asks to convert designs to code. Also use it when the user specifies a Vapor UI version, or when codebase auto-detection is needed to choose component behavior.
scripts/).references/).Best used by code-capable assistant agents (Copilot/Codex/Claude Code/Gemini-like models) that can run small node scripts or call MCP tools to fetch Figma node trees.
Vapor UI is a design-system skill for the goorm-dev/vapor-ui React component library. It provides 5 Node.js scripts for version detection, component listing, component info, examples, and icon lookup, plus Figma-to-code conversion instructions. Scripts were skipped by the runner due to .mjs extension. Static analysis shows well-structured, secure code with no malicious patterns. Template literal URL construction from CLI args is the only minor concern.
node (required for .mjs scripts)Clean skill targeting Vapor UI (goorm-dev) component library. Good separation of concerns across 5 focused scripts. The .mjs extension is standard for ESM Node.js but the auditor runner only handles .py/.sh — not a skill quality issue. Figma MCP integration is a nice touch for design-to-code workflow.
