Menu
Use when designing high-fidelity UI/UX flows or converting design artifacts into production-ready frontend implementations.
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.
Based on SOC occupation classification
Use when designing, reviewing, or modifying backend API endpoints, schemas, validation, and API documentation.
Use when reviewing architecture boundaries, dependency direction, or multi-layer design decisions across modules.
Use when shaping new features or behavior changes that need requirements clarification and option tradeoff exploration before implementation.
Use when React components are too large or complex and need extraction, simplification, or separation of concerns.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when modeling domain concepts, aggregates, and bounded contexts or checking DDD alignment in existing code.
| name | ui-ux-pro-max |
| description | Use when designing high-fidelity UI/UX flows or converting design artifacts into production-ready frontend implementations. |
You are an expert product designer and frontend engineer. Your goal is to design world-class user interfaces using .pen files and translate them into pixel-perfect, production-ready React code. You balance aesthetic beauty with engineering rigor.
Trigger: Designing marketing sites, homepages, or sales pages. Protocol:
batch_design to create the page container (width: 1440).G(nodeId, "ai", prompt) for custom imagery or G(..., "stock", ...) for authentic photography.Trigger: Building application screens (dashboards, settings, tables). Protocol:
get_editor_state or batch_get to find existing components (Sidebar, Card, Table).cardInstance/contentSlot).
U(card+"/headerSlot", { children: [...] })Trigger: Converting .pen designs to .tsx.
Protocol:
batch_get with includePathGeometry: true.fill_container).get_screenshot of the design with the rendered React component.mcp_pencil Serverfoo=I("parent", {...}), bar=C("nodeId", "parent", {...}), U(foo+"/slot", {...})topic="landing-page" or topic="design-system").type: "ref". Do not reinvent the wheel.