Otis Chen

The hozu command: check, map, why, show, get, browse, call, plan, add, build, export, gen, dev, serve, docs, migrate and skill (all with --json)

Isomorphic compiled state-machine interpreter behind Hozu features

Hozu IR types and the typed builders you author apps with: feature, machine, query, mutation, ui, contract, project

Export a Hozu app as static files

Hozu compiler: derives per-node render plans (static, ISR, SWR, streamed, client) from the IR

Test rendered Hozu pages through the real handler: status, headers, visible text, payload, form posts

Tailwind CSS v4 for Hozu, compiled from the classes the IR declares

Hozu validator: structured diagnostics with fixes, contract runner and behaviour lock

Markdown content collections with typed front matter for Hozu

Lets Hozu builder callbacks use ordinary TypeScript (===, ?:, &&, template strings, assignments) by lowering it to the IR's explicit forms

Hozu data runtime: resolvers bound by declaration (in TypeScript or a Go service through remote()), cache, tags, dedup and invalidation

Hozu server runtime: generated render functions, in-order streaming SSR and a web-standard handler

Optional build-time image optimisation (WebP srcset) and share-image cards for Hozu, using sharp

Hozu development server: CSS hot swap, state-keeping reloads and Hozu DevTools

Zod adapter for Hozu schemas (Standard Schema, stored as JSON Schema in the IR)

Bundles the client modules of Hozu client components with esbuild

tailwind-variants for Hozu components, run at record time; /config generates the tailwind-merge config

Run a Hozu app on Node: HTTP server, ISR page cache, tag revalidation and compression

Hozu DevTools: point at the screen, get a request that points the agent at the source

Create a Hozu app, set up for Claude Code or for agents that read AGENTS.md