원클릭으로
chipyard
Unified Chipyard flow: automatically routes to local or Docker workflow based on backend_mode setting.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Unified Chipyard flow: automatically routes to local or Docker workflow based on backend_mode setting.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
Run full Chipyard-to-ORFS PnR flow for large designs (SmallBOOM etc.) using All-Mock memory blackboxing in Docker: generate RTL, preprocess nosram, run multi-round ORFS synth->finish with mock SRAMs to avoid OOM.
Docker Chipyard flow: generate RTL from a Chipyard config via Docker, run SRAM mapping, stage artifacts into MyDesign, and hand off to PnR.
Run full Chipyard-to-ORFS PnR flow with multi-round parameter iteration in Docker: generate RTL from Chipyard Docker, preprocess nosram+SRAM override, run 3 rounds of ORFS synth→finish on sky130hd with progressive clock/utilization/density tuning for optimal PPA.
Run full Chipyard-to-ORFS PnR flow with multi-round parameter iteration: generate RTL from Chipyard with ENABLE_YOSYS_FLOW, preprocess nosram+SRAM override, run 3 rounds of ORFS synth→finish on sky130hd with progressive clock/utilization/density tuning for optimal PPA.
Unified Chipyard PnR flow: automatically routes to local or Docker workflow based on backend_mode setting.
Sync modified files from a ChipAgent local project (e.g. ChipAgent-Test) back to the ChipAgent source repo. Scans all mapped directories, diffs each file, presents a summary table, and asks user which items to copy back.
SOC 직업 분류 기준
| name | chipyard |
| description | Unified Chipyard flow: automatically routes to local or Docker workflow based on backend_mode setting. |
| allowed-tools | ["Bash","Read","AskUserQuestion"] |
Unified entry point. Routes to the appropriate workflow based on .chipagent/env.json configuration.
PROJECT_ROOT="<project-root>"
BACKEND_MODE=$(grep -o '"backend_mode": *"[^"]*"' "$PROJECT_ROOT/.chipagent/env.json" | cut -d'"' -f4)
If backend_mode is missing or empty:
Run /chip-agent:initialize to detect installed tools and determine best backend mode
backend_mode to .chipagent/env.jsonRe-read backend_mode after initialization completes:
BACKEND_MODE=$(grep -o '"backend_mode": *"[^"]*"' "$PROJECT_ROOT/.chipagent/env.json" | cut -d'"' -f4)
Continue with routing using the newly detected backend_mode
If still empty after initialization, default to local.
| backend_mode | Skill to read | Description |
|---|---|---|
local | skills/chipyard-local/SKILL.md | Local Chipyard installation via MCP tools |
docker | skills/chipyard-docker/SKILL.md | Docker containers (ucbbar/chipyard-image) |
Execution: Read the appropriate skill file and follow its pipeline.
Use either local or Docker MCP servers:
mcp__chipagent-backend__* tools → run Chipyard locallymcp__chipagent-backend-docker__* tools → run Chipyard in Docker containersThen invoke this skill again.