メニュー
How to test devctl features via the browser dashboard — always use the Playwright snapshot tool, never the screenshot tool, and always verify changes in the UI at http://127.0.0.1:4000 after deploying.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
How to write and run devctl integration tests — where tests live, how to write failing tests first (TDD), and how to run them safely inside an Incus container without touching live host data.
Full workflow for tagging and publishing a devctl release and/or a PHP binaries release — versioning, release note generation from TODO.md, clearing TODO.md completed items, and the exact git/GitHub CLI steps for each release type.
How to add a new CLI command to devctl — writing the Cmd struct, registering it with init(), adding Client methods, using output helpers, and documenting it in README.md
How to add a new dashboard screenshot for a new or existing feature — wiring up scripts/screenshots.js, seeding data into the demo container via scripts/demo.sh, and adding the image reference to the README.
How to create, update, or maintain agent skills for this project — file structure, frontmatter rules, naming constraints, and where OpenCode discovers them
Full workflow for picking up and completing a TODO item from TODO.md — read the backlog, clarify, implement, install, browser-test, update docs, and move the item to Completed.
| name | testing-dashboard |
| description | How to test devctl features via the browser dashboard — always use the Playwright snapshot tool, never the screenshot tool, and always verify changes in the UI at http://127.0.0.1:4000 after deploying. |
After building and deploying devctl (go build -o devctl . && make deploy), always verify the change works by opening the dashboard in the browser and interacting with it. Do not assume the build passing is sufficient.
Always test in the dashboard. Navigate to http://127.0.0.1:4000 after every deploy and verify the relevant page or feature visually and functionally.
Never use the screenshot tool. Use playwright_browser_snapshot instead. Screenshots are large binary blobs that fill the context window rapidly and provide no more useful information than the accessibility snapshot.
Use the snapshot tool to inspect state. playwright_browser_snapshot returns a structured accessibility tree — use it to read table values, button states, and text content before and after interactions.
Interact to confirm behaviour. Don't just check the page loads. Click buttons, trigger actions (start/stop/install), and confirm the resulting state change appears in a follow-up snapshot.
1. make deploy (or go build -o devctl . && make deploy)
2. playwright_browser_navigate → http://127.0.0.1:4000/<relevant-page>
3. playwright_browser_snapshot ← read current state
4. playwright_browser_click / interact as needed
5. playwright_browser_snapshot ← confirm state changed as expected
| Path | What to check |
|---|---|
/services | Service status, version strings, start/stop/install actions |
/sites | Site list, create/delete, HTTPS routing |
/php | PHP version selector, per-site PHP version |
/mail | Mailpit iframe |
/dumps | dd() dump stream |
/settings | TLS trust, settings toggles |