Once UI Handbook
Beginner Guides
What is Once UI?
Install & config
Page skeleton
Your first page
Build And Launch
How to launch a portfolio site that actually gets you hired
How to build a documentation site with MDX and Next.js
How to ship a landing page and dashboard with authentication in Next.js
How to launch a social app with Next.js and Supabase
Vibe Coding
Introduction to vibe coding
Set up your local dev environment
Essential tools for vibe coding
Build your first Once UI app
Common Patterns
Hero section
Static panel
Form layout
Highlighted card
Responsive stacking
Decoration layers
Dialog & modal
Toast & feedback
Tables & lists
Loading states
App shell navigation
Dashboard & charts
Chat & messaging
Auth & verification
Settings & split panels
Data filters & toolbar
Command palette
Pricing & plans
Accordion & FAQ
Media & uploads
Empty & error states
SEO, Open Graph, and structured data
Documentation code blocks with live preview
Carousels, galleries, and before/after comparisons
Date pickers and scheduling
Context menus and dropdown actions
Tags, chips, and multi-value inputs
Roadmap & kanban
Form inputs & controls
Progress, status & badges
Scrolling & feeds
Profile, avatars & identity
Social proof & logo clouds
Masonry & media grids
Table pagination, search & bulk selection
Banners & announcements
Footer layouts
Onboarding & first run
Waitlist & coming soon
Design Tips
Color & surfaces
Harness overview
Row, Column & Grid
Spacing & rhythm
Icons & buttons
Reveal & motion
Theme tokens, FOUC-free init, and runtime style controls
Tooltips and hover cards
Block updates
Block updates changelog
Agent Resources
Column, not Flex
Semantics over CSS
Typography scale
Common gotchas
Block anchors
Validate generated code
Pro block registry
Match task bundles
TrademarkTrademark
Ctrl k
Search...
Sign up
Once UI Handbook
Beginner Guides
What is Once UI?
Install & config
Page skeleton
Your first page
Build And Launch
How to launch a portfolio site that actually gets you hired
How to build a documentation site with MDX and Next.js
How to ship a landing page and dashboard with authentication in Next.js
How to launch a social app with Next.js and Supabase
Vibe Coding
Introduction to vibe coding
Set up your local dev environment
Essential tools for vibe coding
Build your first Once UI app
Common Patterns
Hero section
Static panel
Form layout
Highlighted card
Responsive stacking
Decoration layers
Dialog & modal
Toast & feedback
Tables & lists
Loading states
App shell navigation
Dashboard & charts
Chat & messaging
Auth & verification
Settings & split panels
Data filters & toolbar
Command palette
Pricing & plans
Accordion & FAQ
Media & uploads
Empty & error states
SEO, Open Graph, and structured data
Documentation code blocks with live preview
Carousels, galleries, and before/after comparisons
Date pickers and scheduling
Context menus and dropdown actions
Tags, chips, and multi-value inputs
Roadmap & kanban
Form inputs & controls
Progress, status & badges
Scrolling & feeds
Profile, avatars & identity
Social proof & logo clouds
Masonry & media grids
Table pagination, search & bulk selection
Banners & announcements
Footer layouts
Onboarding & first run
Waitlist & coming soon
Design Tips
Color & surfaces
Harness overview
Row, Column & Grid
Spacing & rhythm
Icons & buttons
Reveal & motion
Theme tokens, FOUC-free init, and runtime style controls
Tooltips and hover cards
Block updates
Block updates changelog
Agent Resources
Column, not Flex
Semantics over CSS
Typography scale
Common gotchas
Block anchors
Validate generated code
Pro block registry
Match task bundles

Set up your local dev environment

Install prerequisites and configure your local environment for AI-orchestrated development.
Updated 19d ago
Introduction to vibe coding
Essential tools for vibe coding
TrademarkTrademark
Once UIDocumentationBlog
© Once UI. All rights reserved.
Built with Aveiro

The shift from writing syntax to orchestrating intent

In 2026, the bottleneck of software development is no longer syntax—it is context. "Vibe coding" is a movement where developers use AI agents to manifest software through high-level intent rather than manual line-by-line coding. The core philosophy: Traditional coding is imperative (how to do it). Vibe coding is declarative (what the result should be).

Why vibe coding needs Once UI

Legacy frameworks like Tailwind CSS are often too "noisy" for efficient AI orchestration. They require agents to generate long strings of utility classes, which increases the token surface area and leads to hallucinations. Once UI was built for this era. It reduces interface complexity into Semantic Atoms:
  • Semantic Layouts: Instead of using AI to generate utility classes, it uses semantic, ready-made components to build complex layouts.
  • Tokenized Intent: Instead of guessing hex codes, the AI uses themed props like onBackground="neutral-strong".
  • Encapsulated Logic: Complexity lives "behind the curtain," so the AI manages 10 lines of code to do the work of 100.

The vibe coding stack

To vibe code effectively in 2026, you need three layers:
  • The orchestrator — Windsurf, Cursor, or Claude Dev: the agent that understands project context.
  • The source of truth — Once UI: high-level components, low-level primitives, and design tokens.
  • The protocol — .windsurfrules, llms.txt and MCP: the rules that prevent AI "code drift".

The process

  • Set the rules: Set up the MCP server in your IDE and provide your AI with the .windsurfrules file to align its mental model with your code.
  • Set up the UI: Speed up the process by using a pre-built boilerplate, or code your custom frontend.
  • Define the data: Design a JSON structure so you can mock the data as you build the UI.
  • Generate the database: Use AI to create an SQL query that generates your database (e.g. in Supabase) based on the JSON structure.
  • Integrate the backend: Use AI to replace the mocked data with secure API calls.

A different paradigm in web development

Vibe coding isn't about "not knowing how to code". It's about removing the friction of translation. In 2026, the best developers aren't the ones who type the fastest; they are the ones who maintain the clearest vision of the product architecture, letting the system handle the rest.