Example project — Frond is not real.

Authored demo content for a fictional plant-care app, rendered by the same parsers and held to the same invariants as a real project's dashboard. This is the system in use, three months in.

docs/features/onboarding.mdCommitmentsactivebuilt2026-07-14Read when: before changing anything in this feature's surface

Onboarding

What it does

Three screens: what Frond is, add one plant, then an optional account to keep it. The account screen is skippable and returns to it later.

Why it is shaped this way

The signup wall was the funnel's failure point (decisions.md → 2026-07-09). Creating something first gives the account a job: protecting work the user already did.

Edge cases

A skipped account means local-only data, and the app says so plainly rather than pretending sync is happening.