メニュー
After making code changes, start the dev server, open the app in Cursor's built-in browser, and verify everything works — check rendering, console errors, and network health. Use proactively after any UI or API change.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Orchestrate continual learning by delegating transcript mining and AGENTS.md updates to the knowledge-synthesizer subagent. Use when asked to mine prior chats, maintain AGENTS.md, update learned preferences, or run the continual-learning loop.
Security-focused review of code diffs and PRs with surface classification and Semgrep on changed files. Use when reviewing pull requests, branch diffs, or validating security regressions before merge.
Live Notion session log (L4b) — create, incremental updates during work, finalize on CLOSE. Works on any Cursor project workspace.
Bootstrap a new project with Cursor-ready configuration: AGENTS.md, per-project .cursor/rules/project-conventions.mdc, and optional memory_bank/ scaffold. Use at project initialization, when starting a new repo, or when the user says "set up Cursor for this project" / "bootstrap this project" / "init project config".
Phase-1 repo reconnaissance as a standalone skill: stack detection, relevant files, validation commands from repo evidence, workflow hints, and risk flags. Use inside /scout, /ks-conductor pre-flight, or any read-only discovery before planning or implementation.
Validates phase outputs before advancing the SDLC. Defines expected artifacts per phase (intake, scout, plan, critic, build, test, review, document, close) and produces a clear PASS / CONDITIONAL / BLOCK verdict with gaps. Use at orchestrator or command phase boundaries, before expensive work, or when the user asks to verify a gate or "are we ready to proceed".
| name | verifying-in-browser |
| description | After making code changes, start the dev server, open the app in Cursor's built-in browser, and verify everything works — check rendering, console errors, and network health. Use proactively after any UI or API change. |
On-demand loading: Read this skill only when the task clearly matches the description above or trigger phrases below. Do not load for unrelated work.
Routing: This skill is for post-change verification of your own edits (dev server, health check, changed routes). For a broader exploratory QA sweep, use visual-qa-testing.
Use this skill proactively after making code changes to verify the app actually works. Don't just trust that the code is correct — launch it and check.
Start the dev server in the background — check if one is already running by listing terminals. If not:
npm run dev
Set block_until_ms: 0 to run it in the background. Then poll until you see the "ready" message with the localhost URL.
Open in the side browser — launch the app beside your code:
Tool: browser_navigate
Arguments: { "url": "http://localhost:3000", "position": "side", "take_screenshot_afterwards": true }
Quick health check — run these three checks:
Console errors:
Tool: browser_console_messages
Flag any errors. Warnings about deprecations can be noted but aren't blockers.
Network failures:
Tool: browser_network_requests
Flag any 4xx/5xx responses, failed fetches, or CORS errors.
Visual check: Review the screenshot. Does the page render? Is the layout correct? Are there any blank screens or loading spinners that never resolve?
Navigate to the changed page — if your changes are on a specific route, navigate there and repeat the checks.
Test interactions — if you changed a form, button, or interactive element:
browser_snapshot to get element refsposition: "side" to see code and browser at the same time.