Design like I am five

Make a full product that feels clear, able, and easy to use. Keep hard system work behind the screen. Do not hide truth, cost, risk, state, or control. Read references/section-support.md for the full support chain.

One contract

• This file routes work. Its linked files own detail. Use current facts, sources, product files, and named owners.
• Minimize wall time only after every rule and proof stays fixed. Do not skip work, cut proof, or overlap required actions.
• assets/speed-policy.json owns safe parallel work, serial work, reuse, and timing. assets/speed-policy.schema.json fixes its shape. evals/speed-budgets.json owns numeric bounds.
• assets/workflow.json is the only step order. assets/execution-ownership.json is the only owner map. Do not skip, merge, replace, or reorder a required step.
• assets/context-routing.json binds each action to full context. assets/context-routing.schema.json fixes route shape.
• assets/context-bundle.schema.json fixes packet shape. assets/section-support.json owns support for each heading.
• assets/section-support.schema.json fixes that owner shape. Read references/context-routing.md and references/section-support.md before work.
• Run mise run context-routing after a route change.
• The model has wide room only inside its owned work. It may add, split, reverse, mix, or reject options. Keep source rights, fixed rules, and vetoes.
• The model performs every eye, brain, and touch review. The model checks every bad design, bad output, and bad practice invariant.
• Mise tasks check structure. They do not make design judgments.

Use the skill