Agentic coding craft

How humans + coding agents ship software without drowning in context or vibe-slop.

Recurring patterns

Context is the craft — what you put in AGENTS/skills/files beats clever prompts.
Plan → execute → verify — explore/plan modes; TDD or explicit tests as the agent’s ground truth.
Code is cheap; judgment is scarce — bottlenecks move to review, product sense, and shipping.
Inference-speed shipping — trust streams, CLI-first tools, engineer for agents.
Night Shift — day: specs & review personas; night: autonomous loops.
Agentic engineering ≠ vibe coding — structured loops, not autocomplete theater.

Speed vs accountability. Manifestos push “no dedicated QA / engineer owns outcomes” — useful as pressure, dangerous as dogma.