Projects
Describe the product. Ariki builds and ships it.
Not a code snippet generator — a full build pipeline with a plan, specialist agents, quality gates, a live preview you can edit by clicking, and one-click publish.
From brief to published
Six stages, each with a gate that has to pass before the next one starts.
Brief & design direction
Ariki asks the few questions that matter — what you're building, who it's for, colour palette, typography, and whether you have a logo. No logo? It can design one first or drop in placeholders.
Deterministic scaffold
The project starts from a hand-verified blueprint for its kind — landing page, marketing site, SaaS dashboard, internal tool or automation. Agents only fill in feature code.
Plan & specialist agents
A task plan with dependencies is generated, then specialist agents build in rounds — frontend, backend, content, QA — each with a strict output contract.
Quality gates on every round
Nothing is written until it parses, every import resolves, every dependency exists, and colour contrast passes. Failures repair themselves in a bounded loop.
Live preview & instant edits
Watch it build in a live preview. Click any text, colour or spacing to edit it directly — no model call, no waiting.
Pre-flight & publish
One button runs syntax, import, dependency, entry-point, secret, route, metadata and alt-text checks, then publishes when clean.
Safeguards
Builds that don't fall over
Green snapshots & rollback
Every clean round records a known-good file tree. If a repair loop can't recover, the project is restored to the last green build — and the rollback itself is undoable.
Self-healing preview
Runtime errors in the preview open a repair task automatically, deduped and capped so it never thrashes.
Contrast auditing
A static auditor resolves your design tokens and flags unreadable text before you ever see the page.
Restore points & diffs
Every chat message that changed files shows its diff with one-click revert.
Visual QA
Blank pages, placeholder copy and missing routes block the “done” recap instead of shipping quietly.
Secrets per project
Project secrets are stored separately and never written into generated source.
Coming to projects
Planned, not shipped: a project templates library, custom domain binding, per-project backend provisioning, explainer and demo videos as a project type, and workers that operate the products they helped build.