メニュー
Verify functional correctness of the Ball named $ARGUMENTS. Use this skill when users ask to verify/test a Ball, check whether a Ball works correctly, or validate a newly created Ball.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Create a new Buckyball Ball operator named $ARGUMENTS, covering the full flow from implementation to verification.
Staticaly validate Buckyball Ball registration consistency and optionally auto-fix mismatches. Use this skill when users ask to inspect registration status, validate Ball configuration, troubleshoot registration issues, or verify consistency after registration edits.
Systematically debug Buckyball simulation failures. Use this skill when simulation returns FAILED, CTest fails, Chisel compilation errors appear, or users report abnormal Ball behavior. It covers log analysis, waveform analysis, and common failure pattern matching.
Analyze and optimize latency and area for the RTL module named $ARGUMENTS. Applies to any RTL module (Ball, MemFrontend, BBus, GlobalROB, etc.), not limited to Ball operators.
Use waveform-mcp tools to analyze VCD/FST waveforms and inspect Buckyball signal timing. Use this skill for cycle-level timing analysis, handshake debugging, FSM transition checks, or whenever waveform-level evidence is needed.
| name | verify |
| description | Verify functional correctness of the Ball named $ARGUMENTS. Use this skill when users ask to verify/test a Ball, check whether a Ball works correctly, or validate a newly created Ball. |
Important: build, simulation, and test operations must be invoked via MCP tools. Do not call bbdev CLI or nix develop directly.
Use /check logic to validate registration consistency, then ensure all required artifacts exist and fill missing pieces:
examples/balls/<name>/arch/src/main/scala/arch/src/main/scala/framework/balldomain/configs/default.jsonbb-tests/workloads/lib/bbhw/isa/bb-tests/workloads/src/CTest/toy/bbdev_workload_build to build all CTestsbbdev_verilator_run for this Ball's CTest
ctest_<name>_test_singlecore-baremetalbatch=true/debug flowAfter simulation passes, analyze PMC traces from bdb.log:
ls -t arch/log/ | head -5)[PMCTRACE] BALL entries in bdb.log and extract elapsed cycles for the target BallIf simulation fails, use waveform-mcp for precise timing analysis in addition to logs. See /waveform.
Key signal checklist:
cmdReq.valid && cmdReq.ready (command handshake)req.valid/ready and resp.valid (read/write timing)cmdResp.valid && cmdResp.fire (completion handshake)If simulation result is FAILED, run /debug for systematic troubleshooting.