| name | create-web-app |
| description | Build or modify Equal Experts web application UI — forms, dashboards, app screens, navigation, settings, tables, product flows. Use when creating product UI (React/Vue/HTML) that should follow EE brand, design tokens, accessibility, and the Kuat component system. Not for marketing pages (use web-marketing reference) or slides. |
Create EE web app UI
Build on-brand, accessible Equal Experts product UI. Reuse existing Kuat/shadcn components before writing custom code, use semantic tokens (never raw hex), and follow the patterns below — don't invent layouts.
This skill links to the passive reference library; load only the slices you need, when you need them. Standards live in /reference — never paste reference content inline.
Step 1 — Intake
Run the grouped intake first: see ../_shared/intake.md. For web product, confirm at least:
- Scenario / page type — form, dashboard, documentation, auth flow, table, settings, etc.
- Framework + deliverable — React, Vue, or plain HTML/CSS? Code, or a mockup (Figma / Claude Design — if mockup, switch to create-design)?
- Scope of states — happy path only, or also empty / loading / error states?
- Component source available — is
@equal-experts/kuat-react/kuat-vue (or an overlay) installed? (Drives Step 3.)
If the deliverable format is ambiguous, ask once before building.
Step 2 — Load the standards you need
Load progressively — start with foundations, add the medium + pattern slices the scenario needs:
| Need | Load |
|---|
| Colour / type / spacing / radius tokens | ../../reference/design-language/ (colours, typography, spacing, borders) |
| Colour tiers, pairing, extended-palette rules | ../../reference/design-language/colour-usage.md |
| Shadcn light/dark colour mapping | ../../reference/media-types/web-product/colour-modes.md |
| Accessibility requirements | ../../reference/accessibility/accessibility.md + ../../reference/media-types/web-product/accessibility.md |
| Layout & navigation (dark nav patterns, logo placement) | ../../reference/media-types/web-product/design.md |
| Component selection priority | ../../reference/media-types/web-product/component-decision-tree.md |
| UX writing (actions, errors, empty states, forms, confirmations) | ../../reference/media-types/web-product/content/ + ../../reference/content/ |
| The specific page type | ../../reference/media-types/web-product/patterns/ — outcome-framed: Help users to sign-in, complete-a-form; Pages dashboard, documentation |
| Logo usage | ../../reference/brand/logo.md |
| Transactional email UI | ../../reference/media-types/web-product/emails.md |
Token/layout syntax (illustrative only): ../../reference/media-types/web-product/examples/ shows React/Vue/CSS token usage. Treat it as syntax reference, not canonical component API — prefer component guides (Step 3).
Step 3 — Resolve components (Kuat-first, graceful fallback)
Follow the decision tree: Kuat Blocks → Kuat Components → shadcn (themed via kuat-core) → custom build.
Per-component API/usage/a11y is not in this repo — it ships with the implementation. Resolve by stable ID via ../../reference/media-types/web-product/component-registry.md:
- Map the need to an ID (e.g.
shadcn:button, kuat:button-group, kuat:kuat-header).
- Read the guide at
{package}/agent-docs/components/{slug}.md (installed package) or {OVERLAY_DIR}/components/{slug}.md (contributor overlay), resolved via components.manifest.json. The slug drops the namespace (shadcn:button → button).
- Read technical setup (Tailwind / kuat-core preset, theming, tokens) from the package's
agent-docs/setup/ — it is implementation-owned and ships downstream, not in this reference.
Graceful fallback — when a component or its guide is missing:
- Build from the documented pattern in ../../reference/media-types/web-product/patterns/ + token syntax in
examples/, using semantic tokens.
- Flag the gap explicitly in your output: name the component ID you wanted, note it wasn't resolvable, and that you fell back to documented patterns — so it can be added to the library later.
- Never silently invent a component API or hardcode values to paper over a missing guide.
If the deliverable is a mockup — Figma or Claude Design — rather than code: the component-registry
above doesn't apply the same way. Use create-design instead of this step
— it decides single-vs-multiple concepts and fidelity, routes to
figma-build-intake or
mockup-build-intake, and neither customises a
vendor-provided skill.
Step 4 — Build
- Reuse existing components/patterns first; build custom only when the decision tree bottoms out.
- Semantic tokens only (
bg-primary, bg-sidebar, p-4) — never raw hex or arbitrary px.
- Product layouts use dark navigation (Tech Blue) with white monochrome logo; light content areas.
- EE Blue for buttons/icons/CTAs (
primary); the link semantic token for text links and small text — never EE Blue for a text link, it fails small-text contrast. See colour-modes.md.
- Surfaces, borders, and dividers use the EE neutral scale (
neutral-* / muted, border, input), not Server Slate (a distinct brand grey) or raw greys.
- Status colours use the semantic tokens (
error/warning/success/info) — always paired with an icon/label, never colour alone.
- Radius: 0px static content, 6px interactive, 4px inputs.
- Build the scoped states (empty / loading / error) when in scope, per the content rules.
Step 5 — Pre-handoff checklist
Conflict & ambiguity
- If a user request conflicts with a brand/accessibility rule, flag the conflict in your output and recommend the compliant option rather than silently breaking the rule.
- If a foundation rule and a web-product rule conflict, the foundation wins — raise it.
- Ask when scenario, framework, or scope is unclear; don't guess.
Related
