frontend

Route frontend tasks through triage gates and load design references.

3.2k|198|Updated May 25, 2026
One-click install
npx skills add https://github.com/code-yeongyu/lazycodex --skill frontend-code-yeongyu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: frontend
Source: https://github.com/code-yeongyu/lazycodex/tree/main/plugins/omo/skills/frontend
Command: npx skills add https://github.com/code-yeongyu/lazycodex --skill frontend-code-yeongyu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Unblocks teams from ad-hoc frontend tasks by routing them through a disciplined triage system that selects the appropriate reference sets (design, perfection, ui-ux-db) and enforces gate checks before any execution occurs.

Core Features & Use Cases

  • Routes frontend design, performance, and UI tasks through three rule sets: design, perfection, and ui-ux-db, guaranteeing gate checks and contextually loaded references.
  • Enables deterministic execution by loading Layer A (taste/style) and Layer B (design systems) references before code, ensuring token consistency and brand alignment.
  • Supports multi-brand, multi-style frontend work by combining a router with a master design-system gate, preventing generic AI slop and preserving design fidelity.

Quick Start

Describe your frontend task and let the skill route to the appropriate ruleset (design, perfection, or ui-ux-db) and execute using the loaded references.

Frequently Asked Questions about frontend

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

FAQPage Schema
How do I ensure design system token consistency across multiple frontend brands?

To ensure design system token consistency across multiple frontend brands, route tasks through a triage system enforcing master design-system gate checks. It loads Layer B references before execution, guaranteeing token consistency and preventing brand misalignment.

How does frontend task routing work for performance audits and UI execution?

Frontend task routing works by directing performance audits and UI execution through three rule sets: design, perfection, and ui-ux-db. It executes gate checks and contextually loads references, ensuring deterministic, compliant execution aligned with loaded policy.

What is the best way to prevent generic AI output in frontend UI design?

The best way to prevent generic AI output in frontend UI design is combining a task router with a master design-system gate. This loads Layer A taste and style references alongside Layer B systems, enforcing strict design fidelity and brand alignment.

Can I execute frontend design tasks without manually loading specific UI references?

Yes, you can execute frontend design tasks without manually loading UI references. Describe your task and the routing system automatically selects the appropriate reference set, loading Layer A and Layer B policies to ensure contextual execution and token governance.

Does frontend automation enforce gate checks before any UI code execution begins?

Yes, frontend automation enforces gate checks before any UI code execution begins. The triage system selects the correct reference set and applies a master design-system gate, guaranteeing token consistency, brand alignment, and deterministic execution compliance.

When should I use a multi-style design routing system for frontend development?

You should use a multi-style design routing system for frontend development when handling ad-hoc tasks across multiple brands. It unblocks teams by enforcing reference loading and design-system gating, ensuring deterministic execution and preventing design fidelity loss.