eda-research
Component research and procurement. Search JLC for components, analyze datasheets, compare options, and document selections with rationale.
What this skill does
# EDA Research Skill
Source and select components for electronics projects.
## Auto-Activation Triggers
This skill activates when:
- User asks to "find a component", "search for", "source"
- User asks about component specifications or comparisons
- User mentions LCSC, datasheets, or part numbers
- User asks "what MCU/regulator/sensor should I use"
- Project has `design-constraints.json` but missing component selections
## Context Requirements
**Requires:**
- `docs/design-constraints.json` (or prompt user for requirements)
- `docs/project-spec.md` (optional, for context)
**Produces:**
- `docs/component-selections.md` - Human-readable selection log
- `docs/bom-draft.json` - Machine-readable BOM
- `datasheets/*.pdf` - Downloaded datasheets for selected components
## Workflow
### 1. Load Context
Read existing project constraints:
```
@docs/design-constraints.json
@docs/project-spec.md
@docs/component-selections.md (if exists)
```
If constraints missing, ask user for minimum requirements:
- What does this component need to do?
- Key specifications (voltage, current, package)?
- Budget constraints?
### 2. Understand Requirements
For the target component role, identify:
- Critical specifications (must-have)
- Preferred specifications (nice-to-have)
- Package preferences (SMD size, through-hole)
- Any specific brands or series to consider/avoid
### 2.5 Check Architecture Constraints
Before searching, review `design-constraints.json` for:
- **Power topology:** LDO vs buck decision already made in architect phase
- **Thermal budget:** Max watts for this role (check `thermal.hotComponents`)
- **DFM targets:** Assembly method affects package choice
- **Board layers:** May affect component density
For power components, see `reference/REGULATOR-SELECTION.md` for selection criteria.
For passives, see `reference/PASSIVE-SELECTION.md` and `reference/DECOUPLING-STRATEGY.md`.
### 3. Research Options
Use web search to understand:
- Common solutions for this application
- Recommended parts from reference designs
- Known issues or considerations
- Alternative approaches
### 4. Search JLC
Use `mcp__jlc__component_search` to find candidates:
- Search with specific parameters
- Filter by stock availability
- Note pricing at target quantity
- Check for "Basic" parts (lower assembly fee at JLCPCB)
### 5. Analyze Candidates
For top 3-5 options:
- Download/fetch datasheets
- Extract key specifications
- Check application circuits
- Note layout requirements
- Identify any gotchas
### 5.5 Validate Against Constraints
Before presenting options, verify each candidate:
**Thermal validation:**
```
P_dissipation = (calculated from datasheet)
Thermal budget = (from design-constraints.json)
✓ P_dissipation < Thermal budget
```
**Assembly compatibility:**
- Hand assembly → 0603/0805 minimum, no fine-pitch
- Reflow → 0402+ OK
- Turnkey → Check JLCPCB availability
**Architecture compliance:**
- Meets LDO/buck decision from architect phase
- Noise specs OK for rail type (analog vs digital)
- Efficiency acceptable for battery applications
Flag any candidates that fail validation with specific concerns.
### 6. Present Comparison
Create a comparison table:
| Part | MPN | Key Specs | Price | Stock | Pros | Cons |
|------|-----|-----------|-------|-------|------|------|
| ... | ... | ... | ... | ... | ... | ... |
Include recommendation with rationale.
### 7. Confirm Selection
- Get user confirmation
- Document selection with rationale
- Update constraint file
- Save datasheet
### 8. Validate Symbol (After library_fetch)
When fetching online components with `mcp__jlc__library_fetch`, **analyze the returned `validation_data`**:
**Quick checks:**
| Check | Expected | Action if Failed |
|-------|----------|------------------|
| `pin_pad_count_match` | `true` | Check for exposed pads (EP) |
| `has_power_pins` | `true` (for ICs) | Review pin types |
| `has_ground_pins` | `true` (for ICs) | Review pin names |
**Common issues:**
- **QFN/BGA packages** often have exposed thermal pads (EP) not included in symbol
- **Pin electrical types** may be incorrect (power pins marked as passive)
- **Pin names** may not match datasheet
**Fixing with library_fix:**
Use `mcp__jlc__library_fix` to regenerate symbol with corrections:
```
mcp__jlc__library_fix lcsc_id="C#####" corrections='{
"pins": [
{ "action": "add", "number": "EP", "name": "GND", "type": "passive" },
{ "action": "modify", "number": "1", "set_type": "power_in" }
]
}'
```
**Correction actions:**
- `add` - Add missing pin (number, name, type required)
- `modify` - Rename and/or change electrical type
- `swap` - Swap positions of two pins
- `remove` - Remove incorrect pin
## Output Format
### component-selections.md Entry
```markdown
### [Role]: [Part Name] ([LCSC Number])
**Selected:** [Date]
**MPN:** [Manufacturer Part Number]
**Manufacturer:** [Name]
**Price:** $X.XX @ [quantity]
**Specifications:**
- Key spec 1: value
- Key spec 2: value
**Rationale:**
[Why this part was chosen over alternatives]
**Alternatives Considered:**
- [Part 2] - rejected because [reason]
- [Part 3] - rejected because [reason]
**Design Notes:**
- [Any layout or application notes from datasheet]
**Datasheet:** `datasheets/[filename].pdf`
```
### bom-draft.json Entry
```json
{
"role": "regulator-3v3",
"lcsc": "C6186",
"mpn": "AMS1117-3.3",
"manufacturer": "AMS",
"description": "3.3V 1A LDO Regulator",
"value": "3.3V",
"footprint": "SOT-223",
"quantity": 1,
"unitPrice": 0.04,
"extendedPrice": 0.04,
"category": "power",
"basic": true
}
```
## Component Role Categories
See `reference/COMPONENT-CATEGORIES.md` for detailed role definitions.
Common roles:
- `mcu` - Main microcontroller
- `regulator-Xv` - Voltage regulators
- `crystal` - Oscillators/crystals
- `connector-*` - Various connectors
- `esd-*` - ESD protection
- `decoupling-*` - Bypass/bulk capacitors
- `led-*` - Indicator LEDs
- `sensor-*` - Various sensors
## Guidelines
- Prefer JLCPCB "Basic" parts when suitable (lower assembly cost)
- Check stock levels - avoid parts with < 100 in stock
- Consider package size vs hand soldering capability
- Note lead times for non-stock items
- Always document why a part was chosen
- Download datasheets for all selected components
- **Identify 1-2 alternatives** for critical components (see `reference/COMPONENT-ALTERNATIVES.md`)
- **Validate thermal** before confirming power components
- **Check architecture decisions** from design-constraints.json before selecting
## Reference Documents
| Document | Use For |
|----------|---------|
| `REGULATOR-SELECTION.md` | LDO vs Buck selection criteria |
| `DECOUPLING-STRATEGY.md` | Capacitor values for ICs |
| `PASSIVE-SELECTION.md` | Resistor/capacitor fundamentals |
| `COMPONENT-ALTERNATIVES.md` | Finding equivalent parts |
| `DATASHEET-ANALYSIS.md` | Extracting key specs |
| `COMPONENT-CATEGORIES.md` | Role naming conventions |
| `JLC-SEARCH-TIPS.md` | Search strategies |
## Next Steps
After component selection is complete:
1. Run `/eda-source` for remaining components
2. When all components selected, run `/eda-schematic`
3. Update `design-constraints.json` stage to "schematic"
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.