What problem does it solve?
Users working with Chipyard hardware design workflows must manually configure their backend execution environment (local or Docker), leading to setup errors, inconsistent results, and wasted time switching between development setups.
Core Features & Use Cases
- Automatic Backend Detection: Scans the system for local Chipyard, ORFS, Java, sbt installations and Docker availability to determine the optimal execution environment without user input.
- Unified Workflow Routing: Automatically directs to the correct pre-defined Chipyard workflow skill (local or Docker) based on the detected backend mode, eliminating manual skill selection and configuration steps.
- Use Case: A hardware engineer can run Chipyard flows on both their local development machine and a shared Docker environment without adjusting commands or reconfiguring tools for each setup.
Quick Start
Use the chipyard skill to automatically detect your system's Chipyard backend configuration and run the appropriate hardware workflow without manual setup.