Component Package Design

Grow component packages beyond a generated wrapper when the part benefits from reusable surrounding circuitry. A good component package captures the support circuitry, default mode, key equations, layout-sensitive notes, and evidence needed to use the part confidently.

Hard Rules

1. Reuse before create. Search existing registry/workspace packages first.
2. New work lives in components/<NAME>/, never in a separate reference/ tree. Legacy reference/ packages in the registry are read-only examples — inspect them for structure and API shape, but don't copy their placement.
3. The .kicad_sym file is the source of truth for the primitive component interface and pin structure. Keep the .zen API aligned to it.
4. The .zen docstring is the canonical design document. The README is for usage examples only.
5. Review pcb build warnings, especially BOM/sourceability warnings such as bom.match_generic.
6. Don't guess ambiguous passives, straps, sequencing, or oscillator details. Get evidence or stop and ask.
7. Imitate only strong exemplars. Weak/generated packages are useful for pin lookup and starting structure, not authoring style.
8. Preserve # pcb:sch ... comments (tool-managed schematic layout metadata). When renaming a referenced component, module instance, or net, update the matching # pcb:sch names.
9. If an existing registry example conflicts with this skill, this skill wins.

Reuse Before Create