port-design

Port HighTide designs between technology platforms with Bazel or Make flows.

36|13|Updated Jun 8, 2025
One-click install
npx skills add https://github.com/VLSIDA/HighTide --skill port-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: port-design
Source: https://github.com/VLSIDA/HighTide/tree/main/.claude/skills/port-design
Command: npx skills add https://github.com/VLSIDA/HighTide --skill port-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the guesswork of porting a HighTide design from one technology platform to another by walking through the necessary configuration, constraint, and memory artifacts so the build flows stay intact.

Core Features & Use Cases

  • Platform analysis: Review source platform configs, BUILD files, and SDCs while comparing existing ports to derive clock and area scaling ratios.
  • Target environment creation: Copy and adapt config.mk, constraint.sdc, BUILD.bazel, FakeRAM LEF/LIB generators, pdn.tcl, and io.tcl to match the new platform’s naming, units, and layer conventions.
  • Validation guidance: Run Bazel or Make builds, troubleshoot utilization, halo, and timing settings, and confirm reports, DRCs, and QoR metrics on the new platform.

Quick Start

Tell port-design to port lfsr from asap7 to sky130hd.

Frequently Asked Questions about port-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I port a HighTide design from one technology node to another?

Design migration across technology platforms requires aligning config.mk, constraint.sdc, BUILD.bazel, and FakeRAM artifacts with the target node's naming and layer conventions. This ensures Bazel or Make build flows remain intact during the porting process.

What files need to be modified when migrating an ASIC design to a new platform?

ASIC design migration to a new platform requires copying and adapting config.mk, constraint.sdc, BUILD.bazel, FakeRAM LEF/LIB generators, pdn.tcl, and io.tcl. These files must be modified to match the destination platform's technical requirements.

How do I align clock and area scaling ratios during a tech node migration?

Tech node migration requires reviewing source platform configs, BUILD files, and SDCs to derive clock and area scaling ratios. Comparing existing ports helps determine the correct platform constants and scaling ratios for the destination node.

Can I use Bazel and Make build flows when porting HighTide designs between platforms?

Bazel and Make build flows are supported when porting HighTide designs between platforms. The porting process adapts Bazel references and build configurations to meet the target platform's technical requirements and naming conventions.

How do I validate a ported design and troubleshoot timing or utilization issues on the new platform?

Validate a ported design by running Bazel or Make builds and confirming reports, DRCs, and QoR metrics on the new platform. Troubleshoot utilization, halo, and timing settings to resolve any issues encountered during the validation process.

What are the limitations of porting HighTide designs across different technology nodes?

Porting HighTide designs across technology nodes faces limitations including potential mismatches in scaling ratios, platform constants, and layer conventions. The process requires careful adaptation of FakeRAM artifacts and constraints to meet target platform technical requirements.