Purpose

Enable non-programmers to get production-grade frontend components from natural-language requirements.

This meta-skill coordinates three upstream skills and produces implementation-ready output, usually as one .tsx file plus concise setup notes.

It does not replace upstream skill logic and does not assume hidden dependencies are already installed.

Required Installed Skills

• - frontend-design-ultimate (inspected latest: 1.0.0)
• INLINECODE3 (inspected latest: 1.0.0)
• INLINECODE5 (inspected latest: 0.1.0)

Install/update:

CODEBLOCK0

Verify:

CODEBLOCK1

OpenClaw Compatibility Notes

This skill is written to match OpenClaw skill-loading rules:

• - SKILL.md with YAML frontmatter and Markdown body
• single-line frontmatter keys
• INLINECODE8 encoded as a single-line JSON object
• no unsupported custom top-level frontmatter keys

If this file is edited later, keep those constraints intact.

Runtime Prerequisites

Minimum local stack:

• - Node.js 18+
• npm
• React + TypeScript project with Tailwind configured

Adjacent ecosystem dependencies (from inspected upstream skill content):

• - tailwindcss (layout/styling baseline)
• INLINECODE10 (icons used by many shadcn examples)
• INLINECODE11 (theme toggle patterns in shadcn guidance)
• INLINECODE12, zod, @hookform/resolvers (form patterns)
• optional: framer-motion (motion patterns from frontend-design-ultimate)
• optional: recharts or equivalent if a real chart package is required

If user wants shadcn components and they are missing, include explicit setup commands in output:

CODEBLOCK2

Do not assume Next.js unless the user says Next.js.
Default to framework-agnostic React .tsx output that can run in Vite or Next.js with minimal adaptation.

Inputs the LM Must Collect First

• - ui_goal (dashboard, landing page, admin panel, etc.)
• INLINECODE19 (dark, light, or system)
• INLINECODE23 (for example revenue, MRR, growth)
• INLINECODE24 (line, bar, area; static or interactive)
• INLINECODE25 (compact, balanced, spacious)
• INLINECODE29 (colors, logo, typography constraints)
• INLINECODE30 (vite-react, nextjs, or generic-react)
• INLINECODE34 (true/false)

If any critical input is missing, make explicit defaults and state them in Assumptions.

Tool Responsibilities

frontend-design-ultimate

Use for visual direction and anti-generic design decisions:

• - choose strong aesthetic direction
• define typographic hierarchy and color system
• enforce mobile-first responsiveness
• avoid boilerplate “AI-slop” layouts

From inspected upstream guidance:

• - commit to one clear tone
• include an unforgettable visual element
• prefer CSS variables and strong contrast
• avoid generic default fonts

shadcn-ui

Use for robust UI primitives and composition patterns:

• - cards, tabs, sheets, navigation, table, badges, dialogs
• theming conventions and dark mode compatibility
• predictable component structure for fast shipping

From inspected upstream guidance:

• - components are copied into the project (not a hosted runtime UI SDK)
• include install commands for any components you reference
• prefer composable primitives for layout and data display

react-expert

Use for behavioral correctness and maintainability:

• - state design and data flow
• strict TypeScript-first component patterns
• accessibility and predictable rendering behavior
• optional performance hardening for non-trivial UI

From inspected upstream guidance:

• - avoid state mutation and unstable keys
• use semantic structure and cleanup in effects
• ship clear typed interfaces for props/data

Canonical Causal Chain

Use this exact orchestration order.

1. 1. INLINECODE38

• - Normalize user request into goals, constraints, and output contract.

1. 2. INLINECODE39

• - Select one explicit aesthetic mode.
• Define palette, type scale, spacing, and page composition.
• Decide dark-mode token strategy.

1. 3. INLINECODE40

• - Map UI blocks to component primitives (sidebar, card, tabs, table, badge).
• Declare required shadcn installs for referenced primitives.

1. 4. INLINECODE41

• - Implement typed data models and render loops.
• Add local state/hooks where required.
• Keep logic simple and deterministic for copy-paste usability.

1. 5. INLINECODE42

• - Produce one .tsx file by default.
• Include short Setup section with required install commands.
• Include Assumptions and Adaptation Notes.

Output Contract

Default output must contain:

• - Setup:

• - Single TSX File:

• - Assumptions:

• - Adaptation Notes:

No auxiliary script generation. No multi-file scaffolding unless user explicitly asks.

Chart Handling Rule

If chart library is not guaranteed in target project:

• - default to a semantic “chart-ready” card layout with placeholders, or
• use lightweight inline SVG chart logic in the same .tsx.

Do not hallucinate unavailable chart components.
If using external chart lib (for example Recharts), include install command and clearly label as optional.

Scenario Mapping: Revenue Dashboard (Dark Mode)

For scenario:
"I need a dark-mode dashboard showing revenue metrics"

Execution:

1. 1. frontend-design-ultimate defines dark palette, bold typography, and dashboard composition (sidebar + metric grid + chart area).
2. shadcn-ui maps layout to Card, Badge, Tabs, optional Sidebar primitives.
3. react-expert creates typed metric arrays and rendering loops for KPI tiles + trend view.
4. final output returns one production-usable .tsx component plus setup commands.

Quality Gates

Before finalizing output, ensure:

• - component compiles as TSX (no missing symbols in emitted code)
• design is intentional, not default-template generic
• dark mode tokens are coherent and readable
• mobile behavior is included (sm/md/lg responsive strategy)
• all referenced UI components are listed in setup commands
• no fake API calls presented as real integrations

If any gate fails, return Needs Revision with a concrete missing-items list.

Guardrails

• - Never claim “works out of the box” without listing dependency assumptions.
• Never emit components from libraries not declared in setup.
• Never hide unresolved decisions (state them under Assumptions).
• Prefer one high-quality component over broad but shallow scaffolding.

Failure Handling

• - Missing upstream skills: stop and report exact missing skills.
• Missing project context: output generic React version and mark adaptation points.
• Missing chart dependency: provide fallback rendering path and optional install command.
• Conflicting constraints (for example “single file” + “full app routing”): prioritize single-file contract and document tradeoff.