port-designlisted
Install: claude install-skill VLSIDA/HighTide
# Port a Design to a New Platform
You are porting the design `$0` from `$1` to `$2`.
## Prerequisites
Before starting, verify:
- The design exists at `designs/$1/$0/` with a working config.mk and BUILD.bazel
- The RTL source exists at `designs/src/$0/` (shared across platforms)
## Step-by-step Process
### 1. Analyze the source design
Read the source platform's configuration to understand:
- `designs/$1/$0/config.mk` — all ORFS parameters
- `designs/$1/$0/BUILD.bazel` — Bazel flow configuration
- `designs/$1/$0/constraint.sdc` — clock period and port names
- Whether it has FakeRAM memories (ADDITIONAL_LEFS/ADDITIONAL_LIBS)
- Whether it has custom pdn.tcl or io.tcl
- Whether it uses a macros.v wrapper (for designs that remap memory instantiations)
- Whether it's a multi-variant design with subdirectories
Also study existing designs on the target platform to understand conventions:
- Read 2-3 existing `designs/$2/*/config.mk` and `BUILD.bazel` files
- Note the metal layer names and parameter conventions
### 2. Calibrate scaling ratios from existing cross-platform designs
Compare designs that already exist on both platforms to determine scaling factors. Read the constraint.sdc and config.mk for each shared design on both `$1` and `$2`.
**Clock period scaling:** For each design on both platforms, compute the ratio `target_period / source_period`. Average these ratios to get a clock scaling factor. Be mindful of unit differences (asap7 uses picoseconds, nangate45/sky130hd