skills/council/foundry/chip-design-flow/SKILL.md
Use when guiding RTL-to-GDSII chip design flow including RTL coding style, synthesis constraints, place-and-route strategy, timing closure, and tape-out checklist. Do not use for verification methodology (use verification-methodology) or SoC integration (use soc-integration).
npx skillsauth add dtsong/my-claude-setup chip-design-flowInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Guide the end-to-end RTL-to-GDSII design flow, ensuring clean synthesizable RTL, realistic constraints, timing closure, and tape-out readiness.
Reviews RTL source, constraint files, and EDA tool reports. Does not execute EDA tools or modify design files. Does not perform physical verification (LVS/DRC) directly.
No user-provided values are used in commands or file paths. All inputs are treated as read-only analysis targets.
initial, #delay, force in design code).Compaction resilience: If context was lost, re-read the Inputs section for design targets, check the Progress Checklist, then resume from the earliest incomplete step.
| Stage | Status | Key Metrics | Issues | Action Items | |-------|--------|-------------|--------|--------------| | RTL review | ... | CDC crossings: N | ... | ... | | Synthesis | ... | Area: X um2, WNS: Y ns | ... | ... | | P&R | ... | Density: Z%, routing DRC: clean/N violations | ... | ... | | Timing | ... | Setup WNS: Y ns, Hold WNS: Z ns | ... | ... | | Tape-out | ... | LVS/DRC/ERC: clean | ... | ... |
testing
Use to convert a Word .docx file to PDF and/or verify its page count. Triggers on: converting docx to pdf, rendering a document, checking how many pages a docx produces, or asserting a page-count constraint (e.g. a resume must stay 2 pages). Wraps LibreOffice headless conversion.
development
Security audit checklist for web applications. Use when reviewing, auditing, or hardening a web app's security posture. Covers rate limiting, auth headers, IP blocking, CORS, security middleware, input validation, file upload limits, ORM usage, and password hashing. Triggers on requests like "review security", "harden this app", "security audit", "check for vulnerabilities", or when building/reviewing API endpoints.
development
Interactive wizard to craft effective prompts using Claude Code best practices
tools
Use when batch labeling, prioritizing, and assigning GitHub issues during triage sessions.