@genrtl/grtl 2.4.0 → 2.4.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/index.js +12 -7
- package/package.json +1 -1
package/dist/index.js
CHANGED
|
@@ -377,16 +377,18 @@ Before writing or modifying Verilog/SystemVerilog RTL:
|
|
|
377
377
|
2. If implementing from a spec, search \`genrtl_spec2rtl_search\`.
|
|
378
378
|
3. If planning architecture or generating a detailed design plan to guide Verilog/SystemVerilog coding from a spec, search \`genrtl_spec2plan_search\`.
|
|
379
379
|
|
|
380
|
+
When either \`genrtl_spec2rtl_search\` or \`genrtl_spec2plan_search\` is called for a spec, the other companion tool must also be called before proceeding.
|
|
381
|
+
|
|
380
382
|
For diagnostics:
|
|
381
383
|
- After RTL coding -> \`genrtl_lint_load\`; read all returned Lint knowledge card titles, scan the generated/modified RTL for syntax mistakes, lint violations, and CDC risks implied by those titles, then fix obvious issues before compile/synthesis.
|
|
382
384
|
- Lint syntax/CDC diagnostics with actual logs -> \`genrtl_lint_search\`.
|
|
383
|
-
- Vivado synthesis/implementation
|
|
384
|
-
- Quartus synthesis/implementation
|
|
385
|
-
- VCS/QuestaSim compile
|
|
386
|
-
-
|
|
385
|
+
- After running Vivado synthesis/implementation, use \`genrtl_compile_search\` with \`filters.tool = "vivado"\` to fix errors, warnings, and critical warnings.
|
|
386
|
+
- After running Quartus synthesis/implementation, use \`genrtl_compile_search\` with \`filters.tool = "quartus"\` to fix errors, warnings, and critical warnings.
|
|
387
|
+
- After running VCS/QuestaSim compile, use \`genrtl_compile_search\` with \`filters.tool = "vcs"\` or \`"questasim"\` to fix compile errors and warnings.
|
|
388
|
+
- For failing simulations, waveform mismatches, incorrect RTL behavior, or functional code bugs -> \`genrtl_debug_search\`.
|
|
387
389
|
|
|
388
390
|
For verification:
|
|
389
|
-
-
|
|
391
|
+
- Before building a simulation environment or writing/modifying testbench, SVA, assertions, stimulus, checkers, scoreboards, or coverage -> \`genrtl_verification_search\`.
|
|
390
392
|
|
|
391
393
|
For reusable RTL/IP:
|
|
392
394
|
- When the user asks for an RTL architecture, implementation strategy, or design plan without requesting RTL code, call \`genrtl_cbb_list\` first to see which reusable CBB names already exist before proposing a from-scratch design.
|
|
@@ -426,10 +428,10 @@ Use GenRTL MCP tools before relying on model memory for RTL engineering.
|
|
|
426
428
|
- \`genrtl_spec2plan_search\` for turning a specification into an actionable implementation/design plan or detailed design plan that can guide Verilog/SystemVerilog coding.
|
|
427
429
|
- \`genrtl_spec2rtl_search\` for spec-to-RTL implementation, protocol logic, control logic, datapath, algorithm acceleration, or interface implementation.
|
|
428
430
|
- \`genrtl_coding_style_search\` before writing or modifying Verilog/SystemVerilog RTL; read all returned coding style rules and treat them as project-wide coding context.
|
|
429
|
-
- \`genrtl_verification_search\`
|
|
431
|
+
- \`genrtl_verification_search\` before building a simulation environment or writing/modifying testbench, SVA, assertions, stimulus, checkers, scoreboards, coverage, and verification strategy.
|
|
430
432
|
- \`genrtl_lint_load\` after coding; read all returned Lint knowledge card titles, scan the generated/modified RTL for syntax mistakes, lint violations, and CDC risks implied by those titles, then fix obvious issues before compile/synthesis.
|
|
431
433
|
- \`genrtl_lint_search\` for actual Lint syntax/CDC diagnostic logs.
|
|
432
|
-
- \`genrtl_compile_search\`
|
|
434
|
+
- \`genrtl_compile_search\` after Vivado/Quartus/VCS/QuestaSim produce diagnostics, including errors, warnings, and critical warnings; use the matching tool filter when known.
|
|
433
435
|
- \`genrtl_debug_search\` for functional RTL bugs, waveform mismatch, failing simulations, failing testcases, or incorrect behavior.
|
|
434
436
|
- \`genrtl_cbb_list\` before producing an RTL architecture, implementation strategy, or design plan without RTL code, so existing reusable CBB names are considered first.
|
|
435
437
|
- \`genrtl_cbb_search\`, then \`genrtl_cbb_detail\`, for reusable IP/CBB discovery.
|
|
@@ -438,11 +440,14 @@ Use GenRTL MCP tools before relying on model memory for RTL engineering.
|
|
|
438
440
|
|
|
439
441
|
- Do not call \`genrtl_knowledge_search\` first when the task clearly matches a specialized tool.
|
|
440
442
|
- If \`genrtl_knowledge_search\` returns no useful result, retry one specialized tool before answering from model memory.
|
|
443
|
+
- When using either \`genrtl_spec2rtl_search\` or \`genrtl_spec2plan_search\` for a spec, also call the other companion tool before proceeding.
|
|
441
444
|
- Before coding, call \`genrtl_coding_style_search\`, read the full returned style guide, and apply every relevant rule consistently across the generated RTL.
|
|
442
445
|
- After coding, call \`genrtl_lint_load\`, read all returned Lint knowledge card titles, scan the generated/modified RTL for syntax mistakes, lint violations, and CDC risks implied by those titles, then fix obvious issues before compile/synthesis.
|
|
443
446
|
- For Lint syntax/CDC logs with actual diagnostics, call \`genrtl_lint_search\`.
|
|
444
447
|
- For Vivado/Quartus synthesis or implementation errors, warnings, and critical warnings, call \`genrtl_compile_search\` with the matching \`filters.tool\`.
|
|
445
448
|
- For VCS/QuestaSim compile errors or warnings, call \`genrtl_compile_search\` with the matching \`filters.tool\` when known.
|
|
449
|
+
- Before building a simulation environment or verification code, call \`genrtl_verification_search\`.
|
|
450
|
+
- For simulation failures, waveform mismatches, testcase failures, or functional RTL bugs, call \`genrtl_debug_search\`.
|
|
446
451
|
- Apply returned \`code_example\`, \`fix_strategy\`, and \`recommended_next_action\` to the implementation.
|
|
447
452
|
`;
|
|
448
453
|
var CLI_SKILL = `---
|