pcbway
PCBWay PCB fabrication and assembly — turnkey/consigned assembly, design rules, ordering workflow. Alternative to JLCPCB for manufacturing. Use with KiCad. Use this skill when the user mentions PCBWay, needs turnkey assembly (PCBWay sources parts by MPN), has parts not available on LCSC, needs assembled boards with non-LCSC components, wants to compare PCBWay vs JLCPCB, or needs assembly with parts sourced globally rather than from LCSC only. For gerber/CPL export, stencil ordering, and BOM management, see the `bom` skill.
What this skill does
# PCBWay — PCB Fabrication & Assembly PCBWay is a PCB fabrication and assembly service based in Shenzhen, China. It is an alternative to JLCPCB with similar capabilities and pricing. **Typical usage**: Order bare prototype PCBs + framed stencil from PCBWay during prototyping (parts sourced separately from DigiKey/Mouser, hand-assembled in lab). For production runs (100s qty), order fully assembled boards from PCBWay using turnkey component sourcing (PCBWay sources parts by MPN). JLCPCB is the primary alternative. 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 | | `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 parts) | | `jlcpcb` | JLCPCB PCB fabrication & assembly (primary alternative) | | `emc` | EMC pre-compliance risk analysis — run before fab to catch EMC issues | | `spice` | SPICE simulation — verify analog subcircuits before committing to fab | ## Key Differences from JLCPCB | Feature | PCBWay | JLCPCB | |---------|--------|--------| | Component sourcing | Turnkey (PCBWay sources by MPN) | LCSC parts library (you provide LCSC PNs) | | Parts library | No fixed library — sources globally | LCSC library (basic/extended parts) | | Assembly fee model | Quote-based per project | Per-part fees (basic free, extended $3 each) | | BOM format | MPN-based (manufacturer part numbers) | LCSC PN-based | **When to use PCBWay over JLCPCB:** - Parts not available on LCSC — PCBWay sources globally by MPN - Need turnkey sourcing — provide MPNs, PCBWay handles procurement - Prefer quote-based pricing over per-part fee model - Need consigned/kitted assembly (you ship parts to PCBWay) ## Assembly Options | Option | Description | |--------|-------------| | **Turnkey** | PCBWay sources all parts by MPN — you just provide the BOM | | **Partial turnkey** | PCBWay sources some parts, you supply others | | **Consigned/Kitted** | You supply all parts, PCBWay assembles | ## BOM Format for Assembly PCBWay accepts XLS, XLSX, or CSV BOMs. ### Turnkey / Partial Turnkey BOM ```csv Line#,Qty,Designator,MPN,Manufacturer,Description,Package,Type 1,3,"C1,C2,C5",GRM155R71C104KA88D,Murata,100nF 16V X7R MLCC,0402,SMD 2,1,U1,ESP32-S3-WROOM-1-N16R8,Espressif,ESP32-S3 WiFi/BT module,ESP32-S3-WROOM-1,SMD ``` Required columns: | Column | Description | |--------|-------------| | `Line#` | Row number | | `Qty` | Quantity per board | | `Designator` | Reference designators (comma-separated) | | `MPN` | Manufacturer Part Number — PCBWay sources by this | | `Manufacturer` | Manufacturer name | | `Description` | Part description | | `Package` | Footprint/package name | | `Type` | `SMD`, `THT` (through-hole), or `Hybrid` | For turnkey, the **MPN** is the critical field — PCBWay uses it to source parts from their global supply chain. ### KiCad BOM Export for PCBWay 1. In KiCad, ensure MPN and Manufacturer fields are populated in symbol properties 2. Export via Edit Symbol Fields > Export CSV 3. Reformat columns to match PCBWay's expected format (add Line#, Qty, Type columns) For gerber export settings and CPL format, see the `bom` skill — both JLCPCB and PCBWay use the same formats. ## PCB Design Rules (PCBWay Capabilities) ### Standard PCB (1-2 layers) | Parameter | Minimum | |-----------|---------| | Trace width | 0.1mm (4mil) | | Trace spacing | 0.1mm (4mil) | | Via diameter | 0.3mm | | Via drill | 0.15mm | | Annular ring | 0.15mm (6mil) | | Min hole size | 0.15mm | | Board thickness | 0.2-3.2mm (default 1.6mm) | | Min board size | 3x3mm | | Max board size | 600x1200mm (1-2 layer) | ### Multi-layer (4+ layers) | Parameter | Minimum | |-----------|---------| | Trace width | 0.09mm (3.5mil) | | Trace spacing | 0.09mm (3.5mil) | | Via drill | 0.15mm | | Layer count | Up to 14 layers (standard), 24+ (advanced) | | Max board size | 560x1150mm | ### Additional Capabilities | Feature | Specification | |---------|---------------| | Copper weight (outer) | 1oz-8oz | | Copper weight (inner) | 1oz-4oz | | Solder mask colors | Green, Red, Yellow, Blue, White, Black, Matt Green, Matte Black, Purple | | Silkscreen colors | White, Black, Yellow | | Surface finishes | HASL (leaded/lead-free), ENIG, OSP, Hard Gold, Immersion Silver/Tin, ENEPIG | | Impedance control | +/-10% tolerance | | Castellated holes | >=0.4mm diameter | ### Importing DRU into KiCad If you have a PCBWay `.kicad_dru` design rules file, import it in KiCad Board Editor > Board Setup > Design Rules > Import Settings. ## Assembly Constraints - **Minimum order**: 5 PCBs - **Sides**: Top, bottom, or both - **Component types**: SMD, through-hole, or mixed - **Fine-pitch**: BGA and QFP supported - **Assembly drawings**: recommended (photos/diagrams of special placement) - **Special instructions**: add notes for polarity, orientation, or non-standard placement ## PCBWay Partner API (Approval Required) Contact PCBWay for partner API access. Partner API at `https://api-partner.pcbway.com`. Available endpoints: - **PCB Quotation** — `POST api/Pcb/PcbQuotation` — get PCB price - **Place Order** — `POST api/Pcb/PlaceOrder` — add to cart - **Confirm Order** — `POST api/Pcb/ConfirmOrder` — finalize and pay - **Query Order** — `POST api/Pcb/QueryOrderProcess` — track order status Documentation: `https://api-partner.pcbway.com/Help` ## Ordering Workflow ### Prototype Order (Bare PCB + Stencil) 1. **Export gerbers** from KiCad (see `bom` skill for export settings) 2. Upload gerbers to `https://www.pcbway.com/orderonline.aspx` — configure layers, thickness, color, qty 3. Order a **framed stencil** separately at `https://www.pcbway.com/stencil.aspx` 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 MPN, Manufacturer, Description, Package, Type columns 3. **Export CPL** (centroid/placement file) as CSV (see `bom` skill for format) 4. Upload gerbers to PCBWay — configure PCB specs 5. Select "PCB Assembly" — choose Turnkey, Partial Turnkey, or Consigned 6. Upload BOM and centroid files 7. Add assembly drawings/photos if needed (recommended for complex boards) 8. PCBWay reviews files and provides quote 9. Confirm and order ## Tips - **MPN is what matters** — unlike JLCPCB (LCSC PNs), PCBWay sources globally by Manufacturer Part Number - **Turnkey is easiest** — just provide MPNs in BOM, PCBWay handles sourcing - **Assembly requires manual quoting** — unlike JLCPCB's instant pricing, PCBWay reviews your files and provides a custom quote (typically 1-2 business days). Factor this into your timeline. - **Assembly drawings help** — submit photos or annotated PDFs for complex placement - **Lead time varies** — turnkey assembly depends on component sourcing time; check with PCBWay - **Rotation offsets** — PCBWay may have different rotation conventions than KiCad; verify with assembly drawings - **Solder mask colors** — more options than JLCPCB (includes purple, matt variants) - **Edge clearance** — keep copper >=0.3mm from board edge
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.