skills/council/foundry/soc-integration/SKILL.md
Use when planning SoC integration including bus fabric architecture, memory map allocation, IP qualification, interrupt routing, and design-for-test strategy. Covers AMBA/AXI protocols, register map design, DFT insertion, and production test planning. Do not use for RTL design flow (use chip-design-flow) or block-level verification (use verification-methodology).
npx skillsauth add dtsong/my-claude-setup soc-integrationInstall 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.
Plan and review SoC-level integration covering bus fabric topology, memory map allocation, IP block qualification, interrupt routing, DFT strategy, and production test readiness.
Reviews SoC architecture documents, IP datasheets, register maps, and DFT specifications. Does not modify design files or execute EDA tools. Does not perform physical design.
No user-provided values are used in commands or file paths. All inputs are treated as read-only analysis targets.
Compaction resilience: If context was lost, re-read the Inputs section for the SoC under integration, check the Progress Checklist, then resume from the earliest incomplete step.
| IP Block | Bus Interface | Address Range | Clock Domain | DFT | Status | |----------|--------------|---------------|-------------|-----|--------| | CPU core | AXI4 master | N/A | clk_core | Scan | ... | | UART | APB slave | 0x4000_0000 | clk_periph | Scan+BIST | ... | | SRAM | AXI4 slave | 0x2000_0000 | clk_core | MBIST | ... |
development
Use when the council needs to surface organizational knowledge buried across multiple internal sources (wikis, design docs, ADRs, past tickets, postmortems, chat archives, code repos). Plans where to look, what to cross-reference, and how to synthesize findings into evidence the council can act on. Do not use for external market research (use competitive-analysis), library evaluation (use library-evaluation), or technology trend assessment (use technology-radar).
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