luckiday/vibe-hardware / skills/vibe-plm
vibe-plm
VerifiedThe integration / product-lifecycle layer ABOVE vibe-firmware · vibe-pcb · vibe-cad: turn a small embedded product into a single PRODUCT MANIFEST plus the INTERFACE CONTRACTS the three domains must agree on, keep them in sync across a revision, and gate a release/fab on all three being green at once. Use when STARTING a new product (scaffold the firmware/pcb/cad dirs + manifest), CHANGING something that crosses a domain boundary (a pin move, a board-outline change, a shared fit number), CUTTING a revision, or wiring up a fab/release. Key facts this skill encodes: the product is one `product.yaml` — identity + per-domain status + the interface contracts — and it is the single source of truth (the architecture's "fit numbers + net map" box made concrete); there are exactly three contracts — `pinmap.yaml` (pcb -> firmware), `board.step` (pcb -> cad, a GENERATED artifact), `constraints.yaml` (cad <-> pcb, the shared fit numbers) — direction is producer -> consumer; `revision` (vYYYY-MM-DD) bumps on ANY cross-domain change so all three move together; the release gate is cross-domain (pcb ERC/DRC 0/0/0 + belly, cad 0 mm^3 fit, firmware hardware-tested) and must be green at ONE revision before fab. Critically, vibe-plm is self-contained: its scripts read the contract FILES and never import/call another skill's code — cross-skill coupling is DATA (the manifest + the contracts) and PROSE hand-offs, never a runtime dependency. Validate with `scripts/plm_check.py` (manifest sanity + interface-drift gate). Worked reference: `examples/pager-buddy/product.yaml`. Siblings: vibe-firmware/pcb/cad.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.3 KB |
| references/manifest-and-interfaces.md | markdown | 10.0 KB |
| references/release-checklist.md | markdown | 2.8 KB |
| scripts/plm_check.pyexecutable | script | 21.7 KB |
references/release-checklist.md
View on GitHub# Cross-domain release gate
A release/fab is the one moment all three domains must be green **at the same
revision**. Each domain runs its **own** gate (with its own skill's scripts — vibe-plm
does not run them); this checklist is the cross-domain wrapper that says "ship it".
Run from the product dir. Pin everything to one `revision:` in `product.yaml`.
## 0. Manifest + contracts consistent
- [ ] `python3 …/skills/vibe-plm/scripts/plm_check.py product.yaml` → **no errors**
(artifact-pending warnings are OK *until* you need that artifact below).
- [ ] `revision:` is today (or the intended tag) and reflects the latest cross-domain
change. Every domain below is built against **this** revision.
## 1. PCB gate (vibe-pcb)
- [ ] `scripts/pcb_check.sh <proj>` → ERC clean + DRC **0 errors / 0 unconnected**
(silk warnings are cosmetic, don't conflate).
- [ ] `BELLY_BOX=… scripts/pcb_check.sh <proj>` → no front copper/vias under a flush
module's belly.
- [ ] Power is **live out of the fab** (default solder-jumpers closed).
- [ ] `board.step` exported (the `board_step` contract) so cad can fit-check it.
- [ ] Physical-verify-before-ordering checklist walked (pull-ups, VIN, header order,
land pattern, mount-hole spacing, I²C address).
## 2. CAD gate (vibe-cad)
- [ ] `python check_fit.py` → board ↔ shell interference **0 mm³**, against the
**current** `board.step`.
- [ ] The shell's cutouts (display window, USB exit, button/LED) match
`cad/constraints.yaml` — and that file matches the board the pcb actually built.
- [ ] Print orientation + tooling caveats noted; mechanical BOM listed (screws,
inserts, light pipe, feet).
## 3. Firmware gate (vibe-firmware)
- [ ] Pinned/reproducible build (image tag / locked SDK), not a host toolchain.
- [ ] Pins/bus/addresses match `pcb/pinmap.yaml` (config-as-code in sync).
- [ ] **Real-hardware test** — flashes, runs, no crashloop/heap-leak over a sustained
run; failure paths exercised (peripheral unplugged, network loss). A clean
compile is **not** enough.
- [ ] Secrets out of the repo (gitignored creds + a committed `.example`).
## 4. Cut the release
- [ ] All three gates green **at this one revision** — not "pcb from last week".
- [ ] Tag/record the revision; note what changed since the last (changelog).
- [ ] Fab via gerber upload (never an EasyEDA import); print the shell; flash firmware.
- [ ] Only **after** the real-hardware test, trigger any OTA/fleet publish.
## The failure this gate exists to stop
Fabbing the board, *then* finding the shell was modeled to an older outline, or the
firmware pinned to pins the board moved. The fix is cheap and boring: one `revision`,
one `plm_check`, three green gates, in that order. Don't order on a partial gate.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |