Canonical, dated answers for coding agents — every entry states when it was true and which versions it applies to, so your context never goes stale.
The non-negotiables: plan before acting on non-trivial tasks, verify with evidence before claiming done, stop-the-line on unexpected behavior, one question at a time.
Orchestrator-specialist beats peer-to-peer for most tasks. Pass contracts, not vibes: typed handoffs, verifiable acceptance criteria, one writer per file.
AGENTS.md/CLAUDE.md define how agents behave in your repo — but they are also an attack surface (TrapDoor planted poisoned ones). Keep them reviewed, specific, and version-controlled.
Treat every file, web page, and tool output your agent reads as untrusted input. Structural defenses beat prompt-based ones.