SOP.md

sop — standard study / build routine

sop = how you run a session so you dont thrash.

---

before you sit down (2 minutes)

• write one sentence goal: “today i wire open orders to home”
• open: repo, terminal, browser, education/PRD.md checkbox for that goal

---

during (50–90 minutes)

• one vertical slice: database read → controller → view → click in browser
• when stuck > 15 min, paste exact error text into ai (see AI_GUIDE.md)
• do not rewrite entire files unless you are porting to a new template

---

after (5 minutes)

• check one box in PRD.md or write a line in a scratch file:
  • what worked
  • what broke
  • next first step

---

git (if your class uses it)

• commit when a feature works, not when “it compiles”
• message: plain english, “add open orders query to home”

---

3-day rhythm

use CRITICAL_PATH_3DAY.md instead of this generic sop when time is tight.