BuildWithMe UI / Handbook

Three sources. Shared intent.

Every design ships React, Vue, and Svelte source. Native-parity status is earned only after behavior, accessibility, and visual intent pass the framework matrix.

React / Next.js

React implementations use explicit client boundaries only where state or browser APIs require them. Pages, metadata, and registry documents remain server-rendered.

Vue / Nuxt

Vue implementations use Vue 3 composition patterns and single-file components. Props and events follow Vue naming conventions.

Svelte / SvelteKit

Svelte implementations target Svelte 5 and use runes where local state is required. Props preserve the shared capability contract.

Parity policy

Markup does not need to be character-for-character identical. Props, events, behavior, keyboard support, labels, motion controls, failure recovery, public capability, and visual hierarchy must be equivalent before native parity is claimed.