skills.rest
xsw632
xsw632COMMUNITY
Explore all skills by this author →
GitHub

chipyard-pnr

Automate backend detection and workflow routing for Chipyard place-and-route tasks.

2|Updated Mar 16, 2026
Search Tags:#docker#workflow-routing#hardware-design#pnr#place-and-route#chipyard
One-click install
npx skills add https://github.com/xsw632/ChipAgent --skill chipyard-pnr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: chipyard-pnr
Source: https://github.com/xsw632/ChipAgent/tree/main/skills/chipyard-pnr
Command: npx skills add https://github.com/xsw632/ChipAgent --skill chipyard-pnr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the manual effort of configuring and selecting the correct Chipyard place-and-route workflow for your hardware project, removing setup friction and reducing configuration errors for both local and containerized execution environments.

Core Features & Use Cases

  • Automatic Backend Detection: Scans your project environment for local installations of Chipyard, ORFS, Java, and sbt, as well as Docker availability, to determine the optimal execution backend.
  • Unified Workflow Routing: Automatically directs you to the appropriate local or Docker-based PnR workflow based on your .chipagent/env.json configuration, with a fallback to run initialization if no backend mode is set.
  • Use Case: Hardware engineers working on Chipyard-based ASIC or FPGA projects can run place-and-route tasks without manually managing toolchain setup or switching between execution environments.

Quick Start

Use the chipyard-pnr skill to run the Chipyard place-and-route workflow for your current hardware project, automatically using your pre-configured local or Docker backend.

Frequently Asked Questions about chipyard-pnr

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

FAQPage Schema
How do I automate Chipyard place-and-route workflow selection between local and Docker environments?▼

Automating Chipyard place-and-route workflow selection is handled by scanning your project for local ORFS toolchains or Docker availability, then routing execution based on your .chipagent configuration. This eliminates manual backend setup overhead.

What does automatic backend detection look for in a Chipyard hardware design project?▼

Automatic backend detection scans your Chipyard hardware design project for local installations of ORFS, Java, and sbt, alongside Docker availability. This determines the optimal execution environment for your physical implementation tasks.

Do I need a .chipagent configuration file to run Chipyard PnR tasks?▼

You need a .chipagent configuration file to specify your preferred backend mode for Chipyard PnR tasks. If no backend mode is set, the workflow routing automatically falls back to run initialization to configure the environment.

Can I use Docker for Chipyard ASIC physical implementation without manually configuring the toolchain?▼

You can use Docker for Chipyard ASIC physical implementation without manual toolchain configuration. The unified workflow routing automatically directs your PnR tasks to a containerized execution environment if Docker is detected.

What happens if no backend mode is configured for my Chipyard place-and-route workflow?▼

If no backend mode is configured for your Chipyard place-and-route workflow, the routing mechanism falls back to run initialization. This ensures your .chipagent environment is properly set up before executing PnR tasks.

Related Skills

Explore More Software Engineering Skills→
alexanderopalexanderop

using-git-worktrees

Create isolated git worktrees for feature branches with safety checks.

Community
Advanced
chuanseng-ngchuanseng-ng
180

fpga-emulation

Automate ASIC RTL adaptation, synthesis, and bring-up for FPGA prototypes.

Community
Advanced
xsw632xsw632
2

chipyard-local

Automate Chipyard Verilog generation and sky130hd SRAM mapping for OpenROAD.

Community
Advanced
xsw632xsw632
2

chipyard

Detect local Chipyard installations and Docker availability to route hardware workflows.

Community
Intermediate