<Purpose> Generate an RTL wrapper module that instantiates a third-party IP with correct port connections, parameter settings, and tie-offs. Outputs: rtl/ip_wrappers/{ip_name}_wrapper.sv. </Purpose>

<Use_When>

Integrating a new third-party IP (memory, PLL, PHY, DSP block)
IP has an IP-XACT descriptor or datasheet with port list
Wrapper with standard AXI/APB/custom interface adapter is needed </Use_When>

<Do_Not_Use_When>

IP is already instantiated and only parameter changes needed (edit directly)
IP is first-party RTL developed in this project (no wrapper needed)
Full IP integration with verification needed (use rtl-p5s-func-verify after this skill) </Do_Not_Use_When>

<Why_This_Exists> IP instantiation is error-prone: wrong port widths, missing tie-offs, and parameter mismatches cause subtle bugs. Automated wrapper generation from the authoritative IP descriptor eliminates transcription errors and documents all connections explicitly. </Why_This_Exists>

<Execution_Policy>

rtl-explorer reads existing project structure and interface conventions
rtl-architect designs the wrapper interface and connection strategy
rtl-coder writes the wrapper RTL using skills/rtl-ip-instantiate/templates/ip-wrapper-template.sv as scaffold

<Steps> 1. rtl-explorer reads project structure: existing wrappers in rtl/ip_wrappers/, interface conventions, coding style 2. rtl-architect reads IP descriptor (IP-XACT or datasheet): lists all ports, parameters, tie-off requirements 3. rtl-architect designs wrapper interface — adapts IP vendor port names to project conventions: - Vendor `clk_i` → project `clk` or `{domain}_clk` (e.g., `sys_clk`) - Vendor `rst_ni` → project `rst_n` or `{domain}_rst_n` (e.g., `sys_rst_n`) - Vendor ports → project `i_`/`o_`/`io_` prefix convention 4. rtl-coder writes rtl/ip_wrappers/{ip_name}_wrapper.sv: - Module declaration with `i_`/`o_`/`io_` prefixed ports, `logic` types only - IP instantiation with `u_` prefix (e.g., `u_{ip_name}`) - All ports connected or explicitly tied off with `// TIED: reason` comments - Parameter mapping with `// PARAM: description` comments - No `reg`/`wire` — `logic` only 5. lint-checker runs Verible + slang on generated wrapper via Bash CLI </Steps> <Examples> <Good> rtl-explorer finds project uses AXI4-Lite for register interfaces with i_/o_ port prefixes; rtl-architect reads SRAM IP-XACT, maps 32 vendor ports to project convention (vendor clk→sys_clk, vendor rst_n→sys_rst_n, vendor din→i_sram_din); rtl-coder writes wrapper instantiating as u_sram with logic types only; rtl-lint-check passes. </Good> <Bad> Writing wrapper without reading existing project conventions — creates inconsistent port naming that breaks downstream integration. </Bad> </Examples>

<Purpose> Generate an RTL wrapper module that instantiates a third-party IP with correct port connections, parameter settings, and tie-offs. Outputs: rtl/ip_wrappers/{ip_name}_wrapper.sv. </Purpose>

<Use_When>

Integrating a new third-party IP (memory, PLL, PHY, DSP block)
IP has an IP-XACT descriptor or datasheet with port list
Wrapper with standard AXI/APB/custom interface adapter is needed </Use_When>

<Do_Not_Use_When>

IP is already instantiated and only parameter changes needed (edit directly)
IP is first-party RTL developed in this project (no wrapper needed)
Full IP integration with verification needed (use rtl-p5s-func-verify after this skill) </Do_Not_Use_When>

<Execution_Policy>

rtl-explorer reads existing project structure and interface conventions
rtl-architect designs the wrapper interface and connection strategy
rtl-coder writes the wrapper RTL using skills/rtl-ip-instantiate/templates/ip-wrapper-template.sv as scaffold

Rtl Ip Instantiate

Rtl Ip Instantiate

Xurl

Acp Router

Coding Standards

Api Design

Mcp Server Patterns

Backend Patterns