The flows
Same discipline, different jobs — pick a flow and follow the arc. Click any node for detail.
◇ validated plan·
runnable gate before each commit·
report + pause every phase·
never runs dark
The catalog
Search, filter, and open any skill for what it does, when to trigger it, and what it composes.
/
No skills match — try a different term.
How it works
The discipline a one-off prompt forgets — made first-class.
01
Compose, don't reinvent
Every skill invokes the real tools — ce-plan, ie-validate-plan, layered-rails — not a hand-rolled imitation.
02
Plan, then validate
Real work is planned with compound-engineering and validated with intent-engineering before a line is written.
03
Verify, don't trust
A plan's load-bearing claims are checked against the code, not assumed — the misclassification you catch is the file you'd have moved wrong.
04
Gate + report every step
A runnable gate before every commit; a report and a pause after every phase. No dark loops, no silent failures.
05
Loop at scale
A massive task decomposes into many small validated plans, completed one by one.
06
Degrade gracefully
Optional tools are used if present and their absence is stated — never silently skipped.