Trunative

Mobile-only design. This file routes, it does not hold the content: the rules live in heuristics/, the procedures in flow/, the lookup material in references/.

A phone is not a small desktop. Input is imprecise and one-handed, the session gets interrupted, the network drops, the OS owns gestures and insets and permissions, text scales to whatever the user set, and the battery is finite. Design for that, not for a narrow viewport.

Flow

Follow it in order. Never skip init, never end on build.

1. init, read flow/init.md. Once per project, and again whenever npx trunative doctor fails.
2. spec, read flow/spec.md. Whenever the task establishes or changes hierarchy, actions, states or navigation, which a new screen, a new component with state of its own, or a new flow always does. It writes the screen brief, renders it as a greyscale wireframe, and asks the user once, before any code exists. Skipping it is a verdict written in one line, never a default: only a cosmetic or local change goes straight to build.
3. build, read flow/build.md. One screen, one component, or one flow at a time.
4. review, read flow/review.md. Runs on the code that was just written, and again on request over a finished screen. It scores every rule in scope from 1 to 5, and a 1 or a 2 is a violation.
5. loop, back to build while review reports violations. Stop when review comes back clean.

Loaded by build, not a step: flow/firebase.md, whenever the screen touches Firebase.

Heuristics