> For the complete documentation index, see [llms.txt](https://rgbkb.gitbook.io/rgbkb-build-guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rgbkb.gitbook.io/rgbkb-build-guides/zen2-build-guide-wip/introduction.md).

# Introduction

## Parts list <a href="#parts-list" id="parts-list"></a>

{% hint style="warning" %}
You will need to trim your switch pins down to <2.0mm. This won't make them unusable in other boards, just a little more difficult to solder in.
{% endhint %}

* **The Zen 2 keyboard kit includes:**
  * **PCBs, FR4 plate, screws, nuts, TRRS jack and springpins**
  * If you're making your own PCBs, these are the parts:
    * **2** TRRS Jack: ([PJ-320A](https://keeb.io/products/trrs-jacks-3-5mm-one-pair))
    * **6** Springpins: ([2199248-6](https://www.arrow.com/en/products/2199248-6/te-connectivity))
    * **10** M2.5 Nuts: ([5mm wide](https://www.amazon.com/uxcell-Metric-Nylon-Hexagon-Nuts/dp/B07JCSFPWR/ref=sr_1_13?keywords=m2.5%2Bnuts\&qid=1555826714\&s=gateway\&sr=8-13\&th=1))
    * **10** M2.5 Screws: ([Wafer head](https://www.amazon.com/Laptopscrewsdirect-INSPIRON-M2-5x5MM-M2-5X5L-PM2-5X5-0/dp/B01IZ7KMTI/ref=sr_1_1?keywords=Wafer+head+screws+m2.5\&qid=1555826871\&s=gateway\&sr=8-1))

### **You will need** <a href="#you-will-need" id="you-will-need"></a>

* **2** PCBs. Top, middle, and bottom are included.
* **2** Optional type-C ([TYPE-C-31-M-12](https://lcsc.com/product-detail/USB-Type-C_Korean-Hroparts-Elec-TYPE-C-31-M-12_C165948.html)) ports (difficult to solder)
* **66** 1N4148w diodes, [thru-hole](https://lcsc.com/product-detail/Switching-Diode_1N4148_C14516.html) or [SMD](https://www.arrow.com/en/products/1n4148w/diotec-semiconductor-ag). **SMD is required for Choc switches**.
  * While most are ok, check that the SMD diode height is close to or less than 1mm.
* **66** 100NF 0805 [capacitors](https://lcsc.com/product-detail/Multilayer-Ceramic-Capacitors-MLCC-SMD-SMT_100nF-104-5-50V_C29926.html)
* **66** SK6812 or WS2812b [RGB LEDs](https://www.aliexpress.com/item/10Pcs-SK6812-similiar-WS2812B-5050-RGB-full-color-addressable-SMD-LED-Chips-5V/32623583544.html?spm=2114.search0104.3.2.3aaf16e0S9OzMj\&ws_ab_test=searchweb0_0,searchweb201602_3_10065_10130_10068_10890_10547_319_10546_317_10548_10545_10696_453_10084_454_10083_10618_10307_537_536_10902_10059_10884_10887_321_322_10103,searchweb201603_56,ppcSwitch_0\&algo_expid=31c1cb27-04df-4b57-aa54-0628b7197a7d-0\&algo_pvid=31c1cb27-04df-4b57-aa54-0628b7197a7d)
* **16** 2x1 2.54mm [Pin headers](https://lcsc.com/product-detail/PCB-Connectors-Headers-Male-Pins_Shenzhen-Cankemeng-Headers-Pins-1-2P-2-54mm-Straight-line_C124375.html)
* **2** 5V/16MHz Pro Micros with pins ([official](https://www.sparkfun.com/products/12640), [blue clone](https://smile.amazon.com/s/ref=nb_sb_ss_i_2_10?url=search-alias%3Daps\&field-keywords=pro+micro+arduino\&sprefix=pro+micro+%2Caps%2C352\&crid=3CHDJYMGX12DJ), or [black clone](https://www.aliexpress.com/item/Free-Shipping-New-Pro-Micro-for-arduino-ATmega32U4-5V-16MHz-Module-with-2-row-pin-header/2040881593.html?spm=2114.search0104.3.44.53ee128ffTej9v\&ws_ab_test=searchweb0_0,searchweb201602_2_10065_10344_10130_10068_10324_10547_10342_10325_10546_10343_10340_10548_10341_10545_10084_10083_10618_10307_10313_10059_10534_100031_10103_441_10624_442_10623_10622_10621_10620_10142-10621normal#cfs,searchweb201603_25,ppcSwitch_7\&algo_expid=0bca1abc-87c7-4374-8a15-6c883cf11749-6\&algo_pvid=0bca1abc-87c7-4374-8a15-6c883cf11749\&transAbTest=ae803_5\&priceBeautifyAB=0)), pairs are also available at RGBKB. The PM will have limited brighness compared to the Elite-C. Also compatible with the [Elite-C](https://keeb.io/products/elite-c-usb-c-pro-micro-replacement-arduino-compatible-atmega32u4) and [Proton C](https://olkb.com/parts/qmk-proton-c). **Proton-C does not have working split code yet.**
* **66** Switches, MX or Choc
* **10** [M2.5 x 5mm standoffs](https://www.digikey.com/product-detail/en/keystone-electronics/24420/36-24420-ND/1532931) for MX builds only (recommended to help assembly) Hex must be <5.2mm wide.
* (Optional) **2** Rotary encoders
* [TRRS](https://www.amazon.com/gp/product/B078JYVSLB/ref=oh_aui_detailpage_o00_s00?ie=UTF8\&psc=1) or Type C cable for interconnect
* USB cable
* [Bumper feet of your choice](https://www.amazon.com/gp/product/B01HJ64HHO/ref=oh_aui_detailpage_o00_s01?ie=UTF8\&psc=1)
* Keycaps, any Ergodox-compatible set will work.

### **Detailed parts notes:** <a href="#detailed-part-notes" id="detailed-part-notes"></a>

* The Type-C ports are difficult to solder. Screwing them up can result in damage to your controller. Only proceed if you can test the board after soldering and make sure there are no shorts.
* MX switches which support SMD LEDs will give the best backlighting effect. Almost all Kailh switches have a cutout for the LED. Kailh BOX/Choc switches will not be able to have their tops opened after soldering. Any switch with a transparent bottom housing will work great.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://rgbkb.gitbook.io/rgbkb-build-guides/zen2-build-guide-wip/introduction.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.