typescript-best-practices

Effect v4 best practices for TypeScript.

Pre-flight for leaving agents running unattended: pin the done predicate, the wake mechanism, the verifier, the budgets, the trail, and the escalation gates…

Send one neutral review brief to reviewers from other model families (Claude Fable 5.1, Codex on Sol, Grok 4.6) and compare their answers.

Session problem log for improving ppstack.

Peter's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work.

Spawn Test Butcher on the scoped test files, trim tests that are not worth keeping, then write the real tests it flags as missing.

Peter's Herdr conventions.

Spawn Comment Sicko, remove rejected comments, fix accepted structural findings, and offer encodings for valid constraints.

Write the proof before the code: turn a brief or feature request into the checks that will show it works on the real surface, with the evidence each check…

Use when creating a new worker or wrangler file.

Interview the user round by round until a plan, feature, or idea has no silently assumed branch left, then hand back a design brief with a done predicate.

Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in.