メニュー
Diagnose runtime errors by connecting to dev server via MCP.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Build, test, push, deploy, and verify with rollback through Git on failure.
Build and run AI apps and agents with Veryfront CLI
Development flywheel - autonomous cycle of run, observe, fix, verify. Use for continuous development with browser automation.
Build Veryfront apps. Use for real-time errors, route preview, HMR control, and scaffolding pages/APIs/components/AI tools.
Onboard to veryfront-code architecture, testing, conventions, and PR process.
Diagnose and fix build failures using structured error output.
| name | debug-runtime |
| description | Diagnose runtime errors by connecting to dev server via MCP. |
| metadata | {"version":"1.0.0"} |
Diagnose runtime errors by connecting to the dev server via MCP.
Ensure dev server is running
veryfront dev
MCP is available on the dev server port plus 2. The default URL is
http://localhost:3002/mcp.
Check for errors (via MCP)
Use vf_get_errors to get current runtime errors.
Get debug context (via MCP)
Use vf_get_debug_context for stack traces and request context.
Read server logs (via MCP resource)
Read veryfront://logs for recent server log entries.
Trace the issue
Fix and verify
Apply the fix. HMR will auto-reload.
Use vf_get_errors to confirm the error is resolved.
veryfront devveryfront clean, restart dev