frontend-ui-ux

Route frontend UI/UX tasks to a designer agent or Gemini MCP.

Updated Feb 15, 2026
One-click install
npx skills add https://github.com/leejaedus/pepcode --skill frontend-ui-ux-leejaedus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: frontend-ui-ux
Source: https://github.com/leejaedus/pepcode/tree/main/skills/frontend-ui-ux
Command: npx skills add https://github.com/leejaedus/pepcode --skill frontend-ui-ux-leejaedus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Frontend UI/UX tasks often require coordinated designer-developer workflows; this Skill routes tasks to the appropriate designer agent or MCP, enabling faster, aligned outcomes.

Core Features & Use Cases

  • Routing to the designer agent or Gemini MCP for frontend work.
  • Fallback path to Claude agent when MCP tools are unavailable.
  • Supports design system consistency, responsive layouts, and accessibility.

Quick Start

Describe your design task to the frontend-ui-ux skill by issuing /pepcode:frontend-ui-ux <design task>.

Frequently Asked Questions about frontend-ui-ux

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route frontend UI/UX tasks to a designer agent?

Route frontend UI/UX tasks to a designer agent by issuing a standardized Task(...) prompt structure to the skill, which directs the design execution request to the Gemini MCP or falls back to a Claude agent.

What is the fallback mechanism when MCP tools are unavailable for frontend design?

The fallback mechanism for unavailable MCP tools routes frontend design tasks to a Claude agent, ensuring design-system consistency, responsive layouts, and accessibility compliance still proceed without interruption.

How do I maintain design system consistency and accessibility compliance during frontend generation?

Maintain design system consistency and accessibility compliance by routing your design task prompt through the skill, which aligns the designer agent execution with standardized responsive layout requirements.

Do I need MCP discovery via ToolSearch to execute responsive layout tasks?

Yes, you need MCP discovery via ToolSearch to execute responsive layout tasks when routing directly to Gemini MCP, though the skill provides a Claude agent fallback if MCP tools are unavailable.

What's the best way to structure prompts for frontend design execution via Gemini MCP?

The best way to structure prompts for frontend design execution via Gemini MCP is using a standardized Task(...) prompt format that clearly describes the design task for accurate agent routing.