What Flows just did
Based on your request to build Build a Habit Tracker App in React, Flows created 9 implementation stages and 46 checks.
You asked for: Build a real working habit tracker React app with persistent data, form validation, completion state, and simple progress summaries.. Flows generated 9 stages because the application requires Use React to build a single-page habit tracker interface; Allow users to add a new habit with at least a name field; Allow users to delete a habit. Each stage tells your AI builder what to do, tests whether it actually worked, and gives a repair instruction when it fails. These checks are designed to catch: Creating a UI that looks complete but does not actually save data to localStorage; Toggling completion visually without storing it per habit for the current day; Using hardcoded sample habits instead of real user-created data.
Example failure
The form reported success, but no database record was created.
What Flows does
Flows detects the failure, generates a repair instruction, reruns the test, and stores the passing evidence.
Stages — Plan → Build → Test → Fix → Prove → Ship
9 stages · 46 checks · progressive disclosure — open a stage for details
Copy to external builder
Copies a prompt for Claude/Cursor/etc. Records prompt_copied only — not execution, commits, or checks.
Execute through Oort
Requires Sign in with Oort + a provider connection (BYOK). Keys stay on Oort. A model name in the dropdown is not the same as a live connection.
Next
Check off: The app renders without errors
Add a proof note on each check — a checkbox alone is weak proof.
Probes & advanced tools are under “More verification tools”. Experience level: Settings.
Project (saved with proof)
Project binding: Unbound — complete project binding before trusting this run · missing repositoryUrl, repositoryStartCommit, environment, stack
More verification tools (probes, timeline, adapters)Show
App persistence (create → read → assert token)
Body template: {"probe":"{{token}}","title":"flows-probe-{{token}}"}. Needs CORS-readable public create/list endpoints (or inconclusive). Badge only when create→read→refresh finds the token (detects false success).
Two-account authorization (User B cannot see/change User A)
Authorization evidence source: Cross-account ownership test (trust level 5/6). These are not equivalent. Unauthenticated probe alone is weaker (source: unauthenticated API probe). Tokens stay in this browser session only — not uploaded to Flows servers.
Generated edge-case tests (review / approve)
- api_probe Submitting the form empty is rejected with a clear error
- api_probe Each required field can be omitted and fails validation
- api_probe Malformed email is rejected
- api_probe Malformed phone is rejected when phone is collected
- api_probe Duplicate submission does not create two records
- api_probe Double-click submit creates only one record
- false_success_probe Failed request does not show success
- browser_automation Refresh during submission does not leave corrupt state
- api_probe Oversized input is rejected
- api_probe Unsafe strings do not execute or break storage
- api_probe Create then refresh still shows the record
- api_probe Edit then refresh keeps the edit
- api_probe Delete then refresh removes the record
- api_probe Nonexistent record ID fails cleanly
- cross_account_probe Cross-user record identifier is rejected
Generated from this route’s signals — you approve; you do not invent security tests.
Content probe (GET body contains text)
In-product content probe reads response text when CORS allows — not full DOM/click automation. Playwright script is optional and external.
Proof strength
thin · 0/100
Heuristic from notes + probes + gates — not a production certification.
Verification adapters
- ● Deploy URL probe · idle
- ● API path probe · idle
- ● Authz probe (unauth → 401/403) · idle
- ● Browser persistence · idle
- ● App persistence (create→read) · idle
- ● Content / body text probe · idle
- ○ In-product Playwright DOM · not embedded (download external script)
Filled circles = available here. Empty = not shipped. Probes are not a production audit. Adapter docs
Step 1 of 9
Not startedSet up the app structure and data model
Create the React app foundation and define the habit data shape before building features.
Keep the first pass simple: one main page, one habit list, one add form, and local state wired for persistence later.
Flows keeps plan, checks, failures, and next steps connected
Your AI tool writes or changes the code
Repository grounds the plan only after inspect
Checks always carry a validation tier
How this plan was created
Plan from project details
Flows creates steps using the goal, requirements, stack, platform, and details you provide.
- Project description
- Selected template / route
- User-entered stack
- Constraints and notes
- Build a Habit Tracker App in React
No repository inspection implied. Connect and inspect a codebase to ground steps in real files.
Codebase access
Checking GitHub…
Or paste a repository URL manually
Use these instructions in Claude, ChatGPT, Cursor, Emergent, or another builder.
Create the initial React app structure for a habit tracker. Use a single main page with clearly separated components or sections for: app header, summary stats, add habit form, empty state, and habit list. Define and use a real habit data shape with fields for id, name, createdAt, and completion history keyed by date or an equivalent structure that supports marking habits complete for the current day. Initialize state with an empty habit array, not hardcoded demo habits, and keep the code organized and readable for a beginner React project.
Project context
Copies the project goal, technical details, current step, previous progress, and checks so your AI tool understands what it is working on.
Expected after this step
A working React app shell with the main sections rendered and a habit data model ready for functional features.
Should not happen
- ✕Creating a UI that looks complete but does not actually save data to localStorage
- ✕Toggling completion visually without storing it per habit for the current day
- ✕Using hardcoded sample habits instead of real user-created data
- ✕Showing a streak number that is static or incorrect
Verify gate — prove this step works before continuing
Do not move on until every check is true. Add proof notes — a checked box alone is weak proof. Checks are manual by default; deploy/API probes live under “More verification tools” and do not auto-check boxes.
Do not continue if…
- !Creating a UI that looks complete but does not actually save data to localStorage
- !Toggling completion visually without storing it per habit for the current day
- !Using hardcoded sample habits instead of real user-created data
- !Showing a streak number that is static or incorrect
- !Deleting a habit from the screen but not from persisted storage
Repair path — if this step fails
Use the Repair Prompt when a verify gate fails. Loop: Detected → Diagnosed → Repair issued → Changed → Retested → Resolved
Show repair prompt textShow
Refactor this into a real React app foundation. Remove static placeholder habit cards and define actual state for habits with a data model that includes id, name, createdAt, and completion history. Keep the layout simple but implementation-ready.
Your notes for this step
Definition of Done
Final route-level requirements. Manual checks — separate from per-step verify gates. Completing step gates does not auto-check these. Route completion is not a production-ready claim.