Nuxt 4 · Nuxt UI 4 · TypeScript
A composed foundation for serious frontend work.
Product-neutral by design. Bring your PRD, Figma frames, and OpenAPI contract; keep the engineering system and replace the showcase surface.
Foundations
Designed to be replaced, not fought.
Semantic tokens, restrained components, and one visual language make rebranding fast.
Typography
Clear hierarchy for public and application surfaces.
Display heading
Readable body copy with a comfortable measure and quiet rhythm.
Interface eyebrow
Semantic color
Roles survive a future Figma token replacement.
- Primary
- Success
- Warning
- Danger
- Information
Interaction vocabulary
Form strategy
One schema, explicit pending state, inline validation, persistent errors, and concise success feedback.
Application pattern
Data remains readable at every width.
Dense information uses a table when space allows and an intentionally composed list on small screens. Remote data pages inherit the same loading, empty, failure, and retry expectations.
| Pattern | Primary owner | Status |
|---|---|---|
| Public page | Route | Ready |
| API-backed form | Feature | Review |
| Generated client | Service | Optional |
- Ready
Public page
Owned by Route
- Review
API-backed form
Owned by Feature
- Optional
Generated client
Owned by Service
Application states
The edges are part of the experience.
Loading, empty, failure, offline, forbidden, and not-found states are expected—not deferred polish.
Loading
Empty
Nothing here yet
Create the first item or adjust the current filters.
Failure
Something went wrong
The request could not be completed. Try again or check the request details.
Architecture
Keep presentation clean and the backend authoritative.
The frontend consumes HTTP/OpenAPI contracts. It never imports Sequelize, backend secrets, or persistence logic.
01
Pages
Thin route composition and page-level orchestration.
02
Features
Domain UI only when a feature genuinely needs several related files.
03
Services
Typed API boundary and normalization before components see data.
04
Backend
Business rules and persistence stay in the sibling Node API.