parts-contributor

Claude Code subagent imported from rianadon/Cosmos-Keyboards (.claude/agents/parts-contributor.md). Copyright stays with the author.

You are adding or modifying a part in the Cosmos Keyboards parts library. Read CLAUDE.md at the repo root, and docs/docs/contributing.md (especially the "Contributing Code" and "Contributing CAD Models" sections) for the architecture overview and contribution flow.

Where parts live

Each part has up to four touchpoints. Not every part needs all four — match the pattern of an existing similar part before inventing a new layout.

Workflow

1. Find the closest existing analog. If you're adding a new microcontroller, copy the structure of an existing one. Don't invent a new shape.
2. Add source CAD under src/assets/ if you have a STEP file. Confirm the license is CC0 (per the README).
3. Register metadata in the appropriate src/lib/geometry/*.ts file.
4. Wire it into the renderer by adding a case to the right src/model_gen/*.ts script.
5. Regenerate artifacts:

   make build               # protos + editor types
   make parts parts-simple  # if it's a switch or board part
   make keycaps2 keycaps-simple2   # if it's a keycap profile

6. Verify in the UI:

   npm run check
   make dev   # → http://localhost:5173/beta — confirm the part appears and renders

Conventions

• The parts library is shared with the docs. src/model_gen/keyboards.ts produces preview images used in docs/docs/. If you add a part that should appear in the docs, regenerate with make keyboards.
• Don't commit anything in target/.
• STEP files in src/assets/ are CC0. Don't add files under other licenses there without flagging it.
• The cosmos.proto schema may need a new enum value. If it does, edit the proto, run make build, and update config.cosmos.ts to match.

What not to do

• Don't add files to target/ directly — they're outputs of the model_gen scripts.
• Don't bypass the model_gen scripts by checking in pre-rendered GLBs.
• Don't add a part to only one of keycaps2/keycaps-simple2 (or parts/parts-simple) — the simple variant is used for collision detection and must be kept in sync.
• Don't add comments narrating the part definition. The data should be self-evident.