Preflight Checklist Prompt

[noelsaw1]

AI-DDTK Daily Preflight (run once at session start)

1. Probe MCP tools: call wpcc_list_features + local_wp_list_sites

   • If either fails: run ./install.sh setup-mcp && ./install.sh status, retry
   • If MCP works: skip shell probing for covered tools

2. Probe shell-only tools: command -v rg php node python3 git tmux

3. Establish context: local_wp_list_sites → select active site → pw_auth_status

4. Print preflight report in this format:
   MCP: connected | 21 tools available
   Site: mysite.local (selected)
   Auth: admin — valid 6h | expired | none
   Shell: rg ✓ php ✓ tmux ✓ (list missing as ✗)

5. Session rules (repeat these to yourself before every tool call):

   • ALWAYS use AI-DDTK MCP tools (wpcc_, local_wp_, pw_auth_,
     qm_, wp_ajax_test, tmux_*) instead of ad-hoc shell equivalents
   • ALWAYS use wpcc for code scanning, never ad-hoc grep/rg patterns
   • ALWAYS use tmux_* for long-running commands, never raw background jobs
   • Keep runtime artifacts in ./temp
   • If you catch yourself writing an ad-hoc script for something
     AI-DDTK already does, stop and use the toolkit instead

[noelsaw1]

AI-DDTK PREFLIGHT (run once at session start): Probe MCP first — call wpcc_list_features and local_wp_list_sites; if either fails run ./install.sh setup-mcp && ./install.sh status then retry. Probe shell-only: command -v rg php node python3 git tmux. Establish context: select active site from list, run pw_auth_status. Print one-line report: MCP status, site selected, auth state, missing shell tools. SESSION RULES: ALWAYS use AI-DDTK MCP tools (wpcc_, local_wp_, pw_auth_, qm_, wp_ajax_test, tmux_) instead of ad-hoc shell equivalents. NEVER use grep/rg patterns for code scanning — use wpcc_run_scan. NEVER use raw background jobs — use tmux_ tools. NEVER write ad-hoc scripts for tasks AI-DDTK already covers. Keep all runtime artifacts in ./temp. If you are about to run a shell command, check whether an MCP tool exists for it first.