d3k Standalone Bootstrap
Use this skill when working in a standalone AI app and you need reliable local web debugging with browser + server context.
Why d3k-first
d3kcaptures server logs, browser console, network events, and screenshots in one timeline.d3kexposes a stable CDP endpoint so the agent can control the same browser session being monitored.- Running
npm run devorbun run devdirectly omits this unified telemetry and usually leads to weaker diagnoses.
Bootstrap Workflow
- Confirm whether
d3kis installed:
command -v d3k >/dev/null && d3k --version
- If
d3kis missing, install dev3000 globally (prefer Bun):
bun install -g dev3000
Fallback if Bun is unavailable:
npm install -g dev3000
- Start d3k as the runtime (preferred default in agent shells):
d3k --no-agent --no-tui -t
- Keep d3k running while editing code. Do not start a second dev server with
npm/bun dev.
Debugging Commands
Use these first before ad-hoc log scraping:
d3k errors --context
d3k logs -n 200
d3k logs --type browser
d3k logs --type server
CDP Browser Control
Use the already-monitored browser session instead of launching a separate automation browser.
CDP_PORT="$(d3k cdp-port)"
d3k agent-browser --cdp "$CDP_PORT" open http://localhost:3000
d3k agent-browser --cdp "$CDP_PORT" snapshot -i
d3k agent-browser --cdp "$CDP_PORT" click @e2
d3k agent-browser --cdp "$CDP_PORT" screenshot /tmp/d3k-current.png
Artifacts to Read
~/.d3k/{project}/d3k.log~/.d3k/{project}/logs/~/.d3k/{project}/screenshots/~/.d3k/{project}/session.json
Operating Rules
- Prefer headed mode for interactive debugging.
- Use
--headlessonly for CI or when explicitly requested. - Use
--servers-onlyonly when browser monitoring is intentionally disabled.