Path 01 — Simple website

Your first (or next) simple website: one app, one primary language/stack, one deploy target, a README that tells the truth. The room may still be on fire — keep the coffee and refuse machinery you don’t need.

What “simple website” means here

• Marketing site, docs site, small product UI, or personal project on Pages/Vercel/Netlify/etc.
• One repo (or one obvious package). Not a polyglot monorepo.
• Success = a visitor can load the page and you can ship a change without heroics.

What to ignore (for now)

Skip	Why
Monorepo tooling, affected graphs	One deployable — kiss says keep it
Multi-env promote theater	One target is enough; add staging when pain is real
Agent swarms / subagents	One writer; parent stays in charge
Heavy observability platforms	A working deploy + basic errors first
Org-wide ESC sprawl	One site’s secrets can wait until CI needs cloud keys

If you’re reaching for those, either you graduated early — jump to Path 04 — or you’re rearranging smoke. Run kiss audit.

Reading order

1. Lifecycle: know you’re in Discover / Deliver (or later) — How work flows
2. Architecture: Architecture · Language (usually TypeScript) · Framework · What runs where if hosting is unclear
3. Concepts: This is Fine · Smallest Next Step · Vision-Tied Goals · Evidence over Vibes
4. Orientation: Vision · Situation
5. Strategies: Orient → Craft and Harden → Ship (light) → Tidy as needed
6. Practices (draw these first): IDK Now · KISS · Repos (status, thin ci) · Impeccable · Document It · Pulls · Merge It / Ship It · Tidy Up

Companion: Impeccable for UI craft; DocSlime only if you want a tiny docs/PRODUCT.md — don’t scaffold the whole product org tree.

Starter DAG

flowchart TD
  A[idk-now or recon] --> B[Name vision in README]
  B --> C[Build the thinnest page that proves the promise]
  C --> D[repos ci: lint/build on PR]
  D --> E[pulls + merge-it]
  E --> F[Deploy once - ship-it or host default]
  F --> G[document-it: how to run and deploy]

Right-sized tasks (Goldilocks):

1. One sentence: who is this site for and what should they feel/do.
2. One vertical slice live (hero + real content, not a component zoo).
3. CI that fails on broken build.
4. A merge path you trust.
5. README: install, run, deploy.

Skills cheat sheet

Moment	Skill
Lost	idk-now
“Is this too much?”	kiss
Repo/CI basics	repos status · repos ci
UI craft	Impeccable
Docs	document-it
Land the change	pulls · merge-it · ship-it
Agent thrash	agents slap then stop

Graduate when

• You need a second installable artifact (CLI) → Path 02
• You need a Python library others import → Path 03
• You need multiple apps/packages or deploy targets with shared code → Path 04
• You need a specific runtime host (Lambda, Fly, Vercel, …) → Compute
• Staging vs prod gates are saving you from real incidents → keep ship/stage; still not automatically a monorepo

Follow-Up Prompt

Want to run idk-now quick on this website repo, or kiss on the current plan before writing code?