eda-drc
Design validation and review. Run DRC/ERC checks, verify against constraints, check component availability, and prepare comprehensive validation reports.
What this skill does
# EDA DRC Skill Design validation, rule checking, and pre-manufacturing review. ## Auto-Activation Triggers This skill activates when: - User asks to "check design", "validate", "run DRC" - User asks about design errors or warnings - User mentions manufacturing readiness - Project is approaching completion - User asks "is this ready for fabrication?" ## Context Requirements **Requires:** - `hardware/*.kicad_sch` - Schematic files - `hardware/*.kicad_pcb` - PCB layout - `docs/design-constraints.json` - Project constraints - `docs/component-selections.md` - Selected components **Produces:** - `docs/validation-report.md` - Comprehensive validation report ## Validation Scopes ### `/eda-check schematic` - Run ERC (Electrical Rules Check) - Verify power connections - Check decoupling capacitors - Validate against datasheet requirements - Check component values ### `/eda-check pcb` - Run DRC (Design Rules Check) - Verify placement guidelines - Check routing rules - Validate copper pours - Review silkscreen ### `/eda-check components` - Verify stock availability on LCSC - Check current pricing - Identify lifecycle issues - Suggest alternatives if needed ### `/eda-check manufacturing` - Generate and review Gerbers - Verify BOM completeness - Check position file accuracy - Validate against manufacturer specs ### `/eda-check full` - Run all above checks - Comprehensive pre-manufacturing validation ## Workflow ### 1. Load Context ``` @docs/design-constraints.json @docs/component-selections.md @docs/schematic-status.md @docs/pcb-status.md ``` ### 2. Run Automated Checks - Execute DRC/ERC via KiCad MCP - Capture all violations and warnings ### 3. Manual Review Checklist Use reference documents to verify: - Common issues are addressed - Manufacturer constraints are met - Design guidelines followed ### 4. Component Verification For each selected component: - Check LCSC stock status - Verify pricing - Check for lifecycle warnings ### 5. Generate Report Create comprehensive validation report documenting: - Pass/fail status for each check - List of issues found - Recommended actions - Sign-off status ## Output Format ### validation-report.md ```markdown # Validation Report Project: [name] Generated: [timestamp] Scope: [schematic|pcb|components|manufacturing|full] ## Summary | Check | Status | Issues | |-------|--------|--------| | ERC | PASS/FAIL | X errors, Y warnings | | DRC | PASS/FAIL | X errors, Y warnings | | Components | PASS/FAIL | X issues | | Manufacturing | PASS/FAIL | X issues | | **Overall** | **PASS/FAIL** | | ## Critical Issues Items that MUST be fixed before manufacturing: 1. [Issue description] - [Location] - [Fix] 2. ... ## Warnings Items that SHOULD be reviewed: 1. [Warning description] - [Location] - [Recommendation] 2. ... ## Notes Items for information only: 1. [Note] 2. ... --- ## Detailed Results ### Schematic (ERC) **Status:** PASS/FAIL **Errors:** - [ ] [Error type]: [Details] **Warnings:** - [ ] [Warning type]: [Details] **Checks Passed:** - [x] All power pins connected - [x] All ICs have decoupling - [x] No unconnected pins (except intentional NC) - [x] Net names consistent ### PCB (DRC) **Status:** PASS/FAIL **Errors:** - [ ] [Error type]: [Details] **Warnings:** - [ ] [Warning type]: [Details] **Checks Passed:** - [x] Trace width meets minimum - [x] Clearances meet minimum - [x] Via drill meets minimum - [x] Silkscreen not on pads ### Components | Component | LCSC | Stock | Price | Status | |-----------|------|-------|-------|--------| | [name] | C#### | #### | $X.XX | OK/LOW/OOS | **Issues:** - [Component]: [Issue] ### Manufacturing **Target:** [JLCPCB/PCBWay/etc.] **Checks:** - [ ] Board size within limits - [ ] Layer count supported - [ ] Minimum features met - [ ] BOM complete - [ ] Position file accurate --- ## Action Items ### Before Manufacturing 1. [ ] [Action required] 2. [ ] [Action required] ### Recommendations 1. [ ] [Optional improvement] --- ## Sign-off - [ ] Schematic review complete - [ ] PCB review complete - [ ] Components verified - [ ] Ready for manufacturing Reviewed by: [name/date] ``` ## Guidelines - Run DRC frequently during layout, not just at the end - Address all errors before manufacturing - Document intentional rule violations - Verify component availability before finalizing design - Keep validation report updated as issues are fixed ## Reference Documents - `reference/COMMON-ISSUES.md` - Frequent problems and solutions - `reference/MANUFACTURER-SPECS.md` - Manufacturer capabilities - `reference/VALIDATION-CHECKLIST.md` - Pre-manufacturing checklist ## Next Steps After validation passes: 1. Run `/eda-export [format]` to generate manufacturing files 2. Update `design-constraints.json` stage to "complete"
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.