Platform Targets
- - Web (Next.js)
- - Native (Expo/React Native)
- - Desktop (Tauri shell)
- - TUI (CLI surface)
HAUS - SPEC
Canonical platform plan for building HAUS with unified feature and design parity across web, native, desktop, and TUI.
Use one base scaffold (next-forge/eververse) and import patterns from Better-T-Stack + Midday Convex template. Do not blend multiple generators as peers.
- apps/web
- apps/native
- apps/desktop
- apps/tui
- packages/backend (Convex v1 schema/functions)
- packages/domain (shared business logic)
- packages/contracts (zod schemas + event contracts)
- packages/design-tokens (shared design tokens)
- packages/ui-web
- packages/ui-native
- packages/ui-tui
- packages/feature-flags
- packages/analytics
- packages/test-kit
parity-check
Validate each feature exists and behaves consistently across all platform targets before merge.
design-token-guard
Block hardcoded design values and enforce token usage.
contract-sync
Ensure all apps consume shared contracts with no schema drift.
convex-guard
Verify access control and data safety patterns for Convex functions.
platform-scaffold
Generate feature slices for all targets using one consistent structure.
release-readiness
Run final release matrix: tests, parity, smoke, visual checks, and regression checks.