@genrtl/grtl 2.0.0 → 2.2.0

package/dist/index.js

@@ -374,7 +374,7 @@ var GITHUB_RAW_URLS = ["https://raw.githubusercontent.com/xroting/grtl/main/rule
 var FALLBACK_MCP = `Use GenRTL MCP as the primary grounding source for RTL engineering tasks.
 
 Before writing or modifying Verilog/SystemVerilog RTL:
-1. Search coding style with \`genrtl_coding_style_search\`.
+1. Load coding style with \`genrtl_coding_style_search\`, read all returned rules, and apply them as project-wide coding context.
 2. If implementing from a spec, search \`genrtl_spec2rtl_search\`.
 3. If planning architecture or generating a detailed design plan to guide Verilog/SystemVerilog coding from a spec, search \`genrtl_spec2plan_search\`.
 
@@ -389,6 +389,7 @@ For verification:
 - Testbench, SVA, assertions, stimulus, checkers, scoreboards, coverage -> \`genrtl_verification_search\`.
 
 For reusable RTL/IP:
+- 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.
 - Discover with \`genrtl_cbb_search\`, then inspect with \`genrtl_cbb_detail\`.
 - Use \`genrtl_cbb_acquire\` only when the selected CBB should be installed or re-delivered.
 
@@ -424,16 +425,18 @@ Use GenRTL MCP tools before relying on model memory for RTL engineering.
 
 - \`genrtl_spec2plan_search\` for turning a specification into an actionable implementation/design plan or detailed design plan that can guide Verilog/SystemVerilog coding.
 - \`genrtl_spec2rtl_search\` for spec-to-RTL implementation, protocol logic, control logic, datapath, algorithm acceleration, or interface implementation.
-- \`genrtl_coding_style_search\` before writing or modifying Verilog/SystemVerilog RTL.
+- \`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.
 - \`genrtl_verification_search\` for testbench, SVA, assertions, stimulus, checkers, scoreboards, coverage, and verification strategy.
 - \`genrtl_compile_search\` for SpyGlass lint/CDC after coding and for Vivado/Quartus/VCS/QuestaSim diagnostics, including errors, warnings, and critical warnings.
 - \`genrtl_debug_search\` for functional RTL bugs, waveform mismatch, failing simulations, failing testcases, or incorrect behavior.
+- \`genrtl_cbb_list\` before producing an RTL architecture, implementation strategy, or design plan without RTL code, so existing reusable CBB names are considered first.
 - \`genrtl_cbb_search\`, then \`genrtl_cbb_detail\`, for reusable IP/CBB discovery.
 
 ## Required Behavior
 
 - Do not call \`genrtl_knowledge_search\` first when the task clearly matches a specialized tool.
 - If \`genrtl_knowledge_search\` returns no useful result, retry one specialized tool before answering from model memory.
+- Before coding, call \`genrtl_coding_style_search\`, read the full returned style guide, and apply every relevant rule consistently across the generated RTL.
 - For SpyGlass lint/CDC logs after RTL coding and before Vivado/Quartus/VCS/QuestaSim compile/synthesis, call \`genrtl_compile_search\` with \`filters.tool = "spyglass"\`.
 - For Vivado/Quartus synthesis or implementation errors, warnings, and critical warnings, call \`genrtl_compile_search\` with the matching \`filters.tool\`.
 - For VCS/QuestaSim compile errors or warnings, call \`genrtl_compile_search\` with the matching \`filters.tool\` when known.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@genrtl/grtl",
-  "version": "2.0.0",
+  "version": "2.2.0",
   "description": "CLI, MCP, and coding-agent Skills for GenRTL RTL engineering knowledge",
   "type": "module",
   "bin": {