ps-new-projectlisted

# ps-new-project — new client day-1 scaffold Runs the repetitive setup that's still manual after clone + `lando-setup`: **child theme → CSS build → CLAUDE.md**. Pure orchestration over skills that already exist. Server/repo/PS-core stay out of scope (manual / PM-owned). ## Universal rule: always a child theme Every project gets a child theme, on **both** tracks — you never edit the parent (`panda`/`classic`) directly. The child is the safe override layer; parent files stay untouched so parent updates don't wipe your work. Creating the child is not optional. ## Tracks - `panda` — legacy majority: child of the Panda theme (`parent: panda`). Storefront work (templates + CSS) happens in the child. - `elementflow` — emerging default: child of `classic`, relies on the `stsitebuilder` module. The child is still **mandatory** (same rule). What differs is *where the visual work goes*: in ElementFlow the site layout/content is built in the **builder** (stsitebuilder), so the child's hand-work concentrates on the **checkout and my-account pages** (building those with the builder causes compatibility issues). Don't build the whole site in the child — but you still always have one. **EF child — prefer the official download over generating.** The canonical EF child theme is downloaded from the store itself so it **preserves existing image types** (installing a theme on PS 1.7/8 erases image types; the BO download re-adds them): - PS 1.7 / 8: **BO → Element Flow → Settings → Child theme