Monitored Development

CAPTURE THEN DIAGNOSE. Never guess at the cause — capture the full timeline first, then read it. d3k unifies server, browser, and network events into one log that makes root causes visible.

Rules

• Never diagnose without context — always d3k errors --context before forming a hypothesis
• Let d3k own the dev server — don't run your server separately, d3k wraps it
• Read the timeline, don't grep for errors — surrounding events reveal the chain of causation
• Classify errors before fixing — the source tag determines where to investigate
• Always use long-form flags (--context, --type) to avoid collision with d3k's -c (command) flag

Startup

Always compose the full stack when starting a monitored dev session.

1. Check prerequisites: which d3k || npm install -g dev3000, which portless || npm install -g portless
2. Read package.json scripts to find the dev command and determine the runner
3. Start with CDP browser monitoring: