eda-pcb
PCB layout and routing. Component placement, trace routing, copper pours, design rule configuration, and layout optimization for manufacturability.
What this skill does
# EDA PCB Skill
PCB layout, component placement, and routing.
## Auto-Activation Triggers
This skill activates when:
- User asks to "layout PCB", "place components", "route traces"
- User is working with `.kicad_pcb` files
- User asks about placement, routing, copper pours, vias
- Project has schematic but no PCB layout
- User mentions DFM, trace width, or clearance
## Context Requirements
**Requires:**
- `hardware/*.kicad_sch` - Completed schematic with netlist
- `docs/component-selections.md` - Component details
- `docs/design-constraints.json` - Board size, layer count, etc.
- `datasheets/` - For placement/routing recommendations
**Produces:**
- `hardware/*.kicad_pcb` - KiCad PCB file
- `docs/pcb-status.md` - Layout progress tracking
## Workflow
### 1. Load Context
```
@docs/design-constraints.json
@docs/component-selections.md
@docs/schematic-status.md
@datasheets/ (for placement guidance)
```
### 1.5 Pre-Layout Validation
**Before starting layout, verify:**
| Check | Source | Action if Missing |
|-------|--------|-------------------|
| Schematic ERC clean | schematic-status.md | Complete schematic first |
| Layer count decided | design-constraints.json | See `LAYER-COUNT-DECISION.md` |
| Stackup selected | design-constraints.json | See `STACKUP-DECISION.md` |
| Board dimensions | design-constraints.json | Define constraints |
| Critical interfaces | design-constraints.json | USB, SPI speeds, etc. |
| Thermal budget | design-constraints.json | Power dissipation known |
**Extract key constraints:**
```json
{
"board": {
"layers": 4,
"thickness": 1.6,
"dimensions": {"width": 50, "height": 40}
},
"dfmTargets": {
"manufacturer": "JLCPCB",
"minTraceWidth": 0.15,
"minClearance": 0.15,
"impedanceControl": true
},
"interfaces": {
"usb": true,
"highSpeedSpi": false
},
"thermal": {
"maxPowerDissipation": 2.5
}
}
```
**Architecture Validation Warnings:**
| Condition | Warning |
|-----------|---------|
| USB + 2-layer board | Cannot achieve 90Ω impedance |
| Buck converter + no ground plane | EMI issues likely |
| WiFi/BLE + 2-layer | Antenna performance degraded |
| High-speed SPI (>20MHz) + long traces | Signal integrity risk |
| No thermal plan + >1W dissipation | Thermal issues likely |
### 2. Initialize PCB
1. Create PCB file or open existing
2. Import netlist from schematic
3. Set board outline per constraints
4. Configure layer stackup
5. Set design rules
### 3. Configure Design Rules
Set rules appropriate for manufacturer:
```
JLCPCB standard:
- Min trace width: 0.127mm (5mil)
- Min clearance: 0.127mm (5mil)
- Min via drill: 0.3mm
- Min via annular ring: 0.13mm
```
### 4. Place Components
**Priority order:**
1. **Fixed position items** - Connectors (edge), mounting holes
2. **MCU/Main IC** - Central location
3. **Crystal/oscillator** - Within 5mm of MCU
4. **Power components** - Near input, thermal considerations
5. **Decoupling capacitors** - Adjacent to IC power pins
6. **Sensitive analog** - Away from noisy digital
7. **Remaining components** - Grouped by function
See `reference/PLACEMENT-STRATEGY.md` for detailed guidelines.
### 5. Route Critical Signals First
**Priority:**
1. Power delivery (wide traces, pours)
2. Crystal/oscillator (short, guarded)
3. USB differential pairs (90Ω impedance)
4. High-speed signals (length matching)
5. Sensitive analog (away from digital)
6. General signals
See `reference/ROUTING-RULES.md` for trace width and clearance guidelines.
### 6. Create Copper Pours
- GND pour on bottom layer (2-layer)
- Or GND on layer 2, power on layer 3 (4-layer)
- Thermal relief on pads
- Stitch vias for plane continuity
### 7. Route Remaining Signals
- Follow schematic groupings
- Minimize vias
- Avoid acute angles (use 45°)
- Keep trace lengths reasonable
### 8. DRC Check
- Run design rule check
- Fix violations
- Document intentional exceptions
### 9. Visual Review
- Generate board images
- Check silkscreen readability
- Verify component orientation marks
- Review for manufacturing issues
### 10. Pre-Manufacturing Review
**Validation checklist before ordering:**
| Category | Check | Reference |
|----------|-------|-----------|
| DRC | 0 errors, 0 warnings | `DRC-VIOLATIONS-GUIDE.md` |
| Clearances | Meet manufacturer minimums | `DFM-RULES.md` |
| Via sizes | Drill ≥ 0.3mm (JLCPCB std) | `DFM-RULES.md` |
| Annular rings | ≥ 0.13mm (1oz copper) | `DFM-RULES.md` |
| Trace widths | Power traces sized for current | `ROUTING-RULES.md` |
| USB traces | 90Ω impedance, length matched | `HIGH-SPEED-ROUTING.md` |
| Silkscreen | Not on pads, readable | Visual check |
| Board outline | Closed shape, proper clearance | `DFM-RULES.md` |
**Thermal verification:**
- [ ] Power components have thermal relief
- [ ] Thermal vias under QFN/thermal pads
- [ ] Heat sink areas connected to copper pour
- [ ] No thermal bottlenecks (narrow traces for high current)
**Signal integrity verification:**
- [ ] High-speed signals over solid ground
- [ ] Return paths not broken by splits
- [ ] Crystal area guarded, no traces crossing
- [ ] Antenna keep-out respected (if applicable)
## Output Format
### pcb-status.md
```markdown
# PCB Layout Status
Project: [name]
Updated: [date]
## Board Specifications
- Size: X × Y mm
- Layers: N
- Thickness: 1.6mm
## Progress
- [x] Board outline defined
- [x] Mounting holes placed
- [x] Critical components placed
- [x] All components placed
- [ ] Power routing complete
- [ ] Signal routing complete
- [ ] Copper pours added
- [ ] DRC clean
## Layer Usage
| Layer | Usage |
|-------|-------|
| F.Cu | Signals, components |
| B.Cu | GND pour, some signals |
## DRC Status
- Errors: X
- Warnings: Y
- Unrouted nets: Z
## Design Rules
- Trace width: 0.2mm (signals), 0.5mm (power)
- Clearance: 0.2mm
- Via: 0.3mm drill, 0.6mm pad
## Notes
- [Any special considerations]
## Next Steps
- [What remains to be done]
```
## Guidelines
- Always check datasheets for recommended layouts
- Keep high-current paths short and wide
- Maintain ground plane integrity under sensitive signals
- Consider thermal management early
- Use the DRC frequently during layout
## Reference Documents
| Document | Purpose |
|----------|---------|
| `reference/PLACEMENT-STRATEGY.md` | Component placement guidelines |
| `reference/ROUTING-RULES.md` | Trace width and routing rules |
| `reference/EMI-CONSIDERATIONS.md` | EMI/EMC best practices |
| `reference/DFM-RULES.md` | Design for manufacturing rules |
| `reference/DRC-VIOLATIONS-GUIDE.md` | Common DRC errors and fixes |
| `reference/STACKUP-DECISION.md` | Layer stackup selection |
| `reference/HIGH-SPEED-ROUTING.md` | USB, SPI, I2C, antenna routing |
**Upstream documents:**
| Document | What to Extract |
|----------|-----------------|
| `LAYER-COUNT-DECISION.md` (eda-architect) | Layer count rationale |
| `THERMAL-BUDGET.md` (eda-architect) | Power dissipation limits |
| `DECOUPLING-STRATEGY.md` (eda-research) | Cap values and placement |
| `SCHEMATIC-REVIEW-CHECKLIST.md` (eda-schematics) | Pre-layout verification |
## Next Steps
After PCB layout is complete:
1. Run `/eda-check` for comprehensive validation
2. Update `design-constraints.json` stage to "validation"
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.