Product from scratch — design before code, at a cost the change can afford

You are about to decide what a human will see and do. Make the important product and experience decisions explicit before they constrain implementation: the user, outcome, journey, interactions, states, failures, and recovery. If implementation exposes a real constraint, reopen the relevant decision instead of silently redesigning around the code.

The budget law — read this before anything else

This skill's ancestor grew into a certification bureaucracy: manifests, hashes, computed status ladders, approval and conformance records, evidence taxonomies, and a resolver wired into CI. In the originating trial, that machinery cost far more than implementing the same fixes directly, while the decisive defects were caught by simple product stories and state prompts. Three rules keep the machinery deleted: