jlcpcb
JLCPCB PCB fabrication and assembly — BOM/CPL generation, basic vs extended parts, assembly constraints, design rules, ordering workflow. Use with KiCad for JLCPCB manufacturing. Use this skill when the user mentions JLCPCB, wants to order PCBs or assembled boards, needs prototype bare PCBs and stencils, wants to know JLCPCB design rules and capabilities, or is asking about PCB manufacturing costs or turnaround times. For gerber/CPL export, stencil ordering, and BOM management, see the `bom` skill.
What this skill does
# JLCPCB — PCB Fabrication & Assembly JLCPCB is a PCB fabrication and assembly service based in Shenzhen, China. It is a sister company to LCSC Electronics (common ownership) — they share the same parts library. **Typical usage**: Order bare prototype PCBs + framed stencil from JLCPCB during prototyping (parts sourced separately from DigiKey/Mouser, hand-assembled in lab). For production runs (100s qty), order fully assembled boards from JLCPCB using LCSC parts. PCBWay is an alternative assembler. For component searching, see the `lcsc` skill. For BOM management, gerber/CPL export, and stencil ordering, see the `bom` skill. ## Related Skills | Skill | Purpose | |-------|---------| | `kicad` | Read/analyze KiCad project files, DFM scoring against JLCPCB capabilities | | `bom` | BOM management, gerber/CPL export, stencil ordering | | `digikey` | Search DigiKey (prototype sourcing, primary — also preferred for datasheet downloads via API) | | `mouser` | Search Mouser (prototype sourcing, secondary) | | `lcsc` | Search LCSC (production sourcing — JLCPCB uses LCSC parts library) | | `pcbway` | Alternative PCB fabrication & assembly | | `emc` | EMC pre-compliance risk analysis — run before fab to catch EMC issues | | `spice` | SPICE simulation — verify analog subcircuits before committing to fab | ## Assembly Parts Library ### Part Categories | Category | Description | Assembly Fee | |----------|-------------|--------------| | **Basic** | ~698 common parts (resistors, caps, diodes, etc.) pre-loaded on pick-and-place machines | No extra fee | | **Preferred Extended** | Frequently used extended parts | No feeder loading fee (Economic assembly) | | **Extended** | 300k+ less common parts loaded on demand | $3 per unique extended part | ### LCSC Part Numbers Every assembly component is identified by an **LCSC Part Number** (`Cxxxxx`, e.g., `C14663`). This is the definitive identifier for BOM matching. See the `lcsc` skill for searching parts. ### Parts Search (JLCPCB-Specific) - Parts library: `https://jlcpcb.com/parts/componentSearch?searchTxt=<query>` - Basic parts only: `https://jlcpcb.com/parts/basic_parts` ## BOM Format for Assembly JLCPCB accepts CSV, XLS, or XLSX BOMs with these columns: | Column | Required | Description | |--------|----------|-------------| | `Comment` / `Value` | Yes | Component value (e.g., 100nF, 10k) | | `Designator` | Yes | Reference designators, comma-separated (e.g., C1,C2,C5) | | `Footprint` | Yes | Package/footprint name | | `LCSC Part #` | Recommended | LCSC part number (Cxxxxx) — guarantees exact match | The column header for LCSC numbers must be exactly **"LCSC Part #"** or **"LCSC Part Number"** — typos cause upload failures. ### KiCad BOM Export for JLCPCB 1. In KiCad schematic editor, add an `LCSC` field to each symbol with the LCSC part number 2. Export BOM as CSV with columns: Reference, Value, Footprint, LCSC 3. Rename columns to match JLCPCB's expected format: - `Reference` -> `Designator` - `Value` -> `Comment` - `Footprint` -> `Footprint` - `LCSC` -> `LCSC Part #` For gerber export settings, CPL format, and stencil ordering, see the `bom` skill. ## JLCPCB Official API (Approval Required) Apply at `https://api.jlcpcb.com`. Access is gated — requires review based on order history and business profile. Available APIs (once approved): - **Components API** — real-time pricing, inventory, component specs - **PCB API** — upload gerbers, get quotes, place orders, track status - **Stencil API** — stencil quoting and ordering - **3D Printing API** — SLA/MJF/SLM/FDM ordering ## PCB Design Rules (JLCPCB Capabilities) ### Standard PCB (1-2 layers) | Parameter | Minimum | |-----------|---------| | Trace width | 0.127mm (5mil) | | Trace spacing | 0.127mm (5mil) | | Via diameter | 0.45mm | | Via drill | 0.2mm | | Annular ring | 0.125mm | | Min hole size | 0.2mm | | Board thickness | 0.4-2.4mm (default 1.6mm) | | Min board size | 6x6mm | | Max board size | 500x400mm (2-layer) | ### Multi-layer (4+ layers) | Parameter | Minimum | |-----------|---------| | Trace width | 0.09mm (3.5mil) | | Trace spacing | 0.09mm (3.5mil) | | Via diameter | 0.25mm | | Via drill | 0.15mm | | Board thickness | 0.6-2.4mm | ### Importing DRU into KiCad If you have a JLCPCB `.kicad_dru` design rules file, import it in KiCad Board Editor > Board Setup > Design Rules > Import Settings. ## Assembly Constraints ### Economic vs Standard Assembly | Feature | Economic | Standard | |---------|----------|----------| | Sides | Top only | Top + Bottom | | Component types | SMD only | SMD + through-hole | | Min component size | 0201 | 01005 | | Fine-pitch BGA/QFP | Down to 0.5mm pitch | Down to 0.4mm pitch | | Turnaround | ~3-5 days | ~3-5 days | | Extended part fee | $3 per unique part | $3 per unique part | ### General Constraints - **Minimum order**: 5 PCBs for assembly - **Unique parts limit**: No hard limit, but each extended part adds $3 - **Basic parts**: No extra fee, pre-loaded on machines ## Rotation Offsets JLCPCB's pick-and-place uses different rotation conventions than KiCad for some footprints. Common offsets: | Footprint Family | Typical Offset | |-----------------|----------------| | SOT-23, SOT-23-5, SOT-23-6 | +180° | | SOT-223 | +180° | | SOIC-8, SOIC-16 | +90° or +270° | | QFN (all sizes) | +90° | | SMA/SMB/SMC diodes | +180° | | USB-C connectors | Varies — check datasheet | To fix rotation issues: 1. Add rotation corrections directly in the CPL file before uploading (adjust the Rotation column) 2. For custom footprints, verify pin 1 orientation matches JLCPCB expectations 3. JLCPCB's review step catches major errors, but subtle 180° rotations on symmetric parts (caps, resistors) may slip through 4. After first assembly order, note any rotation corrections needed and apply them to future CPL exports ## Ordering Workflow ### Prototype Order (Bare PCB + Stencil) 1. **Export gerbers** from KiCad (see `bom` skill for export settings) 2. Upload gerbers to `https://cart.jlcpcb.com/quote` — configure layers, thickness, color, qty 3. Add a **framed stencil** to the cart (uses paste layers from your gerbers) 4. Order — PCBs and stencil typically arrive in ~1 week ### Production Order (Assembled Boards) 1. **Export gerbers** from KiCad (see `bom` skill for export settings) 2. **Export BOM** as CSV with LCSC part numbers (format above) 3. **Export CPL** (placement file) as CSV (see `bom` skill for format) 4. Upload gerbers to `https://cart.jlcpcb.com/quote` — configure layers, thickness, color, qty 5. Enable "PCB Assembly", select Economic or Standard 6. Upload BOM and CPL files 7. Review part matching — fix any unmatched parts by searching LCSC numbers 8. Confirm and order ## Tips - **Prefer Basic parts** — no extra fee, always in stock, faster assembly - **Check stock before ordering** — extended parts can go out of stock; use the `lcsc` skill to search - **Panel by JLCPCB** — for small boards, let JLCPCB panelize (cheaper) vs custom panels - **Lead-free solder** — default is leaded (HASL); select lead-free HASL or ENIG if needed - **Impedance control** — available for multi-layer boards, specify stackup in order notes - **Castellated holes** — supported, enable in order options - **V-cuts and mouse bites** — supported for panel separation - **Silkscreen minimum** — 0.8mm height, 0.15mm line width for readable text - **Edge clearance** — keep copper >=0.3mm from board edge (0.5mm recommended)
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.