Your ideas,
shipped
Think it through on the page.
Start on the page — or open Awareness first, to figure out what's worth building. HudHud reads as you write, asks the questions you haven't asked yourself, and turns the clarity you reach into scope.
Three surfaces, one document.
The document stays central. Threads sharpen decisions. Canvas gives loose ideas a shape. Capabilities turn the whole thing into work you can approve.
A thinking partner in the margin.
HudHud reads as you write and starts a thread beside the line that needs it — a question, a piece of critique, a small embed to look at together.
Lock-screen banner shape — app icon, label, and inline actions. Reply chip stays on the banner; everything else routes through the app. Three densities: priority, batched, system — the user sets the cadence per app.
First-run welcome — workspace name, trust copy, single primary action. Nothing lights up before the field has content; the CTA is the only attractor on the page. Setup unfolds quietly after the tap.
Trip route preview — origin, waypoint, destination on real streets. The step card pins to the waypoint, not the polyline midpoint, so the turn instruction sits where the user has to act. Plan-mode and nav-mode stay visibly distinct.
A/B retention — variant B leads day-7 by +4.2 pts. CI overlaps past day 3; reading the curve, not the topline. Hold the call until d10 — the reading should be cleaner by then.
When an idea is still a shape, not a sentence.
When an idea is still loose, sketch it on the canvas. HudHud reads what you draw and turns the sketch into a real piece of scope.
What gets built, named before it's built.
HudHud reads everything you've written and proposes the capabilities it'll deliver. You can edit each one before approving — nothing runs until you do.
- Define the account-first onboarding pathInvite, identity, workspace, first project
- Simplify the welcome and signup card statesCTA hierarchy, trust note, setup choice
- Convert the canvas map into milestonesIdentity, workspace setup, project handoff
- Write the first empty-state copyOne move after the project exists
- Check the flow across surfacesDesktop, mobile, focus states, handoff
From thought to
finished work.
Document
Intent, context, decisions, artifacts — all on one page.
Margin threads
Questions, critique, decisions — anchored to the line they're about.
Capabilities list
Each capability is named and editable before any code runs.
Execution hub
Watch it work — or don't. Steps, time, cost — all on the page, none of it required.
Handoff
Finished work — with the capabilities and the evidence still attached. Mark it done locally, or open a PR.