new-design

Create repos, FakeRAMs, and platform configuration files for HighTide2 hardware designs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Eliminates the manual chaos of adding new open-source hardware designs to the HighTide2 benchmark suite by providing a complete, repeatable integration playbook that keeps every platform on-spec.

Core Features & Use Cases

  • Structured Integration Checklist: Walks through cloning the upstream repo, identifying HDL details, and creating the required dev scripts, release RTL, and FakeRAM artifacts.
  • Platform-Ready Configuration Guidance: Specifies how to author config.mk, constraint.sdc, and optional pdn/io scripts for asap7, nangate45, sky130hd, and similar stacks.
  • Testing and Release Flow: Covers dev vs. release RTL flows, Makefile registration, and Bazel/Mac build validation so each new benchmark can be exercised end-to-end.

Quick Start

Tell the skill to integrate the new design by naming it and supplying the upstream repo URL so you receive the tailored setup checklist.

Frequently Asked Questions about new-design

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

FAQPage Schema
How do I add a new open-source hardware design to a benchmark suite?

To add a new open-source hardware design to a benchmark suite, you must clone the upstream repo, identify HDL details, generate FakeRAM artifacts, and author platform configuration files like config.mk and constraint.sdc to meet project conventions.

What is needed for onboarding Verilog benchmarks across asap7 and sky130hd platforms?

Onboarding Verilog benchmarks across asap7 and sky130hd platforms requires creating release RTL, defining LEF/LIB definitions, and specifying platform configuration files including constraint.sdc and optional pdn or io scripts to match technology-specific requirements.

How does FakeRAM integration work when adding new hardware designs?

FakeRAM integration works by generating specific memory artifacts during the hardware design onboarding process, replacing external memory macros with functional simulators to validate the RTL flow without requiring full physical memory implementations.

Can I use Bazel and Makefile to validate newly integrated hardware benchmarks?

Yes, you can use Bazel and Makefile to validate newly integrated hardware benchmarks by registering the new design in the Makefile and running Bazel or Mac build validation to exercise the dev and release RTL flows end-to-end.

What is the best way to structure platform configuration files for nangate45 benchmarks?

The best way to structure platform configuration files for nangate45 benchmarks is to author a config.mk file alongside a constraint.sdc file, adding optional pdn and io scripts to ensure the design follows technology-specific requirements and passes end-to-end testing.