What Flows just did
Based on your request to build Add Core SEO Features to Existing App, Flows created 6 implementation stages and 22 checks.
You asked for: Add essential SEO features: dynamic meta tags, Open Graph/Twitter cards, a generated sitemap.xml, and a robots.txt, all persisted in the codebase and rendered on the server side.. Flows generated 6 stages because the application requires Meta title and description must be dynamic per route and appear in server‑side HTML.; Open Graph and Twitter Card tags must use the same data.; sitemap.xml must be generated from real route data and be valid XML.. 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: AI returns UI mockups or screenshots instead of real code.; Meta tags are added only client‑side, not present in server‑rendered HTML.; Generated sitemap contains placeholder URLs or misses routes..
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
6 stages · 22 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: Does seoRoutes.json exist in the project root?
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)
- cross_account_probe User B cannot see or change User A’s data
- cross_account_probe Participant cannot call coach/admin endpoints
- cross_account_probe URL/body ID tampering cannot cross tenant boundary
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 6
Not startedAudit existing routes for SEO data
Identify every public route and create a source of truth for meta information
The project is a React SPA using react‑router. Assume source files live under src/pages or src/routes.
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
- Add Core SEO Features to Existing App
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.
Scan the repository for all public route definitions (ignore admin or auth‑only paths). Generate a file named seoRoutes.json in the project root containing an array of objects, each with keys: path (string, starting with '/'), name (human readable), title (string placeholder, e.g., "My Page Title"), description (string placeholder, e.g., "A brief description."). Commit the file. Do not include any private routes.
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
seoRoutes.json exists at project root and lists every public route with placeholder meta fields.
Should not happen
- ✕AI returns UI mockups or screenshots instead of real code.
- ✕Meta tags are added only client‑side, not present in server‑rendered HTML.
- ✕Generated sitemap contains placeholder URLs or misses routes.
- ✕robots.txt placed in wrong folder or contains incorrect content.
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…
- !AI returns UI mockups or screenshots instead of real code.
- !Meta tags are added only client‑side, not present in server‑rendered HTML.
- !Generated sitemap contains placeholder URLs or misses routes.
- !robots.txt placed in wrong folder or contains incorrect content.
- !Missing persistence: changes are described but not written to disk.
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
The AI did not create a real seoRoutes.json or omitted required keys. Re‑run the step and explicitly write a valid JSON file with the exact schema described, ensuring it is saved to the repository.
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.