|
| 1 | +# AI-DDTK Preflight Checklist |
| 2 | + |
| 3 | +A diagnostic checklist for AI agents working in **any WordPress project** where AI-DDTK has been installed locally. This is not specific to the AI-DDTK repo itself — it's designed for agents operating in theme, plugin, or site workspaces where the user has AI-DDTK available as an external toolkit. |
| 4 | + |
| 5 | +AI-DDTK is typically installed at `~/bin/ai-ddtk`. If the user has it, the MCP server may already be wired into their editor, giving you access to tools like `wpcc_*`, `local_wp_*`, `pw_auth_*`, `qm_*`, and `tmux_*` without any shell commands. |
| 6 | + |
| 7 | +--- |
| 8 | + |
| 9 | +## When to use this |
| 10 | + |
| 11 | +Run through this checklist at the start of a session when: |
| 12 | +- You're in a WordPress project and want to know what toolkit support is available |
| 13 | +- The user mentions AI-DDTK, WPCC, or scanning/profiling tools |
| 14 | +- You see MCP tools with `ai-ddtk` prefixes in your tool list and want to confirm they work |
| 15 | + |
| 16 | +If none of the above apply, skip this entirely. |
| 17 | + |
| 18 | +--- |
| 19 | + |
| 20 | +## Steps |
| 21 | + |
| 22 | +### 1. Check if AI-DDTK is installed |
| 23 | + |
| 24 | +```bash |
| 25 | +ls -d ~/bin/ai-ddtk 2>/dev/null && echo "installed" || echo "not installed" |
| 26 | +``` |
| 27 | + |
| 28 | +If installed, the user has access to WPCC (static analysis), LocalWP helpers, Playwright auth, Query Monitor profiling, and more. Reference docs are at `~/bin/ai-ddtk/AGENTS.md`. |
| 29 | + |
| 30 | +If not installed, none of the below applies — proceed with standard tools. |
| 31 | + |
| 32 | +### 2. Check for MCP tools in the current session |
| 33 | + |
| 34 | +Look at your available tool list. If you see tools prefixed with `ai-ddtk` (e.g., `wpcc_list_features`, `local_wp_list_sites`), the MCP server is connected and you can use them directly. |
| 35 | + |
| 36 | +If MCP tools are not visible: |
| 37 | +- The user may need to run `~/bin/ai-ddtk/install.sh setup-mcp` to build the server |
| 38 | +- Or the editor may need a `.mcp.json` pointing to the server — check `~/bin/ai-ddtk/AGENTS.md` for setup instructions |
| 39 | +- This is not a blocker — you can still use the shell CLI tools (`wpcc`, `pw-auth`, `local-wp`, `aiddtk-tmux`) if they're in PATH |
| 40 | + |
| 41 | +### 3. Check shell tools |
| 42 | + |
| 43 | +```bash |
| 44 | +command -v wpcc pw-auth local-wp aiddtk-tmux rg php node python3 git tmux |
| 45 | +``` |
| 46 | + |
| 47 | +AI-DDTK CLI tools (`wpcc`, `pw-auth`, `local-wp`, `aiddtk-tmux`) are added to PATH by the installer. The rest (`rg`, `php`, `node`, etc.) are general dependencies — optional but recommended. |
| 48 | + |
| 49 | +Report what's available. Missing items are worth noting to the user but are not blockers for most tasks. |
| 50 | + |
| 51 | +### 4. Establish WordPress site context (if relevant) |
| 52 | + |
| 53 | +If the current task involves a WordPress site: |
| 54 | +- MCP available: call `local_wp_list_sites` then `local_wp_get_site_info` for the target site |
| 55 | +- Shell only: `local-wp --list` or `wp option get siteurl` |
| 56 | +- Optionally check Playwright auth: `pw_auth_status` (MCP) or `pw-auth status` (shell) |
| 57 | + |
| 58 | +Skip this step if the task doesn't involve a live WordPress site. |
| 59 | + |
| 60 | +### 5. Summarise what's available |
| 61 | + |
| 62 | +Give the user a brief summary of what you found. Example: |
| 63 | + |
| 64 | +``` |
| 65 | +AI-DDTK: installed at ~/bin/ai-ddtk |
| 66 | +MCP tools: 21 tools connected (wpcc, local_wp, pw_auth, qm, tmux) |
| 67 | +WPCC: available, 54 patterns |
| 68 | +Site: my-site.local (WP 6.7, PHP 8.2) |
| 69 | +Auth: admin session valid |
| 70 | +Shell: rg, php, node, python3, git, tmux — all available |
| 71 | +``` |
| 72 | + |
| 73 | +Only include sections for things that are actually present. If MCP isn't connected, just say so and list the shell tools that are available instead. |
| 74 | + |
| 75 | +--- |
| 76 | + |
| 77 | +## Notes |
| 78 | + |
| 79 | +- This checklist helps you discover what's available — it does not change how you should behave. Tool usage guidance is in `~/bin/ai-ddtk/AGENTS.md`, which the user can add to their project's CLAUDE.md if they want it applied. |
| 80 | +- If AI-DDTK is not installed, disregard this checklist entirely and work with whatever tools are available in the current environment. |
0 commit comments