Whole patterns, in order
A recipe is a whole screen or flow where the sequence is the knowledge. A payment form is not hard because inputs are hard; it is hard because the order, the trust signals and the decline path are load-bearing, and no component library will tell you that.
No recipe is written yet. The 12 planned are listed below, with their titles as they will ship.
Planned
Payment formPlanned
CheckoutPlanned
Sign-up and onboardingPlanned
Settings pagePlanned
Pricing pagePlanned
Dashboard shellPlanned
Data table screenPlanned
Search and resultsPlanned
ProfilePlanned
Invite and permissionsPlanned
Empty first-runPlanned
Agent review queuePlanned
Recipes depend on the reference and on Parts 3 to 5, so they are the last layer to fill in. Each one lands complete, or not at all.