People

Mandate & instructions

aerochord is a novelty print-in-place wind instrument that sounds a fixed chord from a single breath. The customer is a maker/musician who wants an object that can't be bought and is obviously computer-designed — a conversation piece that also actually plays. The one thing it must do well: print as a single supportless piece whose internal air path is intact, so that after a short tuning pass it makes the chord. It is a curio and a pipeline stress test, not a concert instrument.

From designs/aerochord/PM.md

Mandate & instructions

A parametric single-board-computer case — Raspberry Pi 4 as the primary target — built deliberately hardware-rich to be the reference / stress-test design for the assembly-instructions feature: it is the first assembly.conf in the catalog declaring real vitamin: entries, so it exercises the NopSCADlib vitamin path, the BOM collection pass and the GPL-3.0 product-page disclosure nothing else does. It must also stand on its own as an everyday print — a vented Pi 4 case that bolts the board down and mounts a 40 mm fan in the lid. The customer is a stranger with a Pi 4 and a shopping list; the one thing it must do well is assemble exactly as the BOM and steps say.

From designs/sbc-case/PM.md

Mandate & instructions

Human collaborator on print-bench. This bio is a placeholder seeded with the registry (issue #123) — Frieda's own words belong here.

From people/frieda.md

Mandate & instructions

A shot-tracker refit of the archived sushi-battleship (frozen at v0.1): every print-in-place shutter door gains a shallow spherical seat that parks a small round marker — a dried soybean, a 6 mm BB, a peppercorn — on any cell that has been called. The customer is the same two players eating battleship off the original board, whose actual failure mode is "wait, did we already call B3?": the original tracks hits (the door is open and the sushi is gone) but leaves misses to memory. One thing it must do well: mark a called cell without leaking any hidden information or touching the tuned sliding fit.

From designs/sushi-battleship-tracker/PM.md

Mandate & instructions

Lark, the Twitter/X growth agent — drains the growth queue for its channel by turning each PM-queued message into channel-native copy, strictly from the queued fact budget, and posting it through the one gated tool (dry-run comment by default; a live tweet only behind the human approval label and the live key). It posts what was queued; it never invents facts, never approves itself, never touches another channel. Runs on a schedule (shipped disarmed) or when invoked as /growth-twitter [issue-numbers].

Lark is the channel half of the growth desk (docs/growth.md): product managers queue messages (growth-queue + channel:twitter issues, filed via /growth-queue or the issue form), and Lark drains that queue on its schedule — turning each queued intent into one channel-native post, in the voice of a workshop that shows its work. The PM owns what is worth saying; Lark owns how Twitter/X says it: the hook, the thread shape, the weighted 280 limit, the one link. By default every drain is a dry run — the would-be tweet lands as a comment on the queue issue for a human to read — and a live post additionally requires the human approved-to-post label AND the live key; the posting tool enforces all of it.

From .claude/skills/growth-twitter

Mandate & instructions

N.U.G.G.S. is a tube system, and the thing it ships is a standard. The standard is one genderless quarter-turn port around an 80 mm bore: every module carries the same port at every end, so any module mates with any other, either way round, and any module leaves the middle of a run in one twist. Today the system ships one run — the Bin Bridge, two bulkheads and a straight joining two enclosures through their walls, for someone with a Bambu-class printer, a spool of natural PETG, and an adult Syrian whose factory cage tubes are too narrow for a pouch-full animal. The one thing the system must do well is be a bore an adult Syrian can traverse safely and an owner can open in one action, at every module anyone ever adds to it. It competes with a hole saw and a length of drainpipe — so if it is not safer, cleanable, and openable, it has no reason to exist.

From designs/nuggs/PM.md

Mandate & instructions

A screw-together end socket for a 40 mm curtain/closet rod that spans an alcove or recess, printed in pairs: a wall boss screwed to each facing wall, a knurled collar hand-threaded onto it capturing the rod end. For the person whose curtains come down for washing a few times a year; the one thing it must do well is hold the rod between two walls and let it go tool-free.

From designs/alcove-rod-socket/PM.md

Mandate & instructions

A print-in-place 1st-birthday keepsake card for the parents of the birthday kid — the people who will stand it on a shelf and fidget with it during phone calls for years. Bubble/"POP" party theme, four working mechanisms off the bed in one piece, personalised with the child's name at slice time. The one thing it must do well: every fidget works on the first print — a keepsake that jams is a coaster.

From designs/pop-fidget-card/PM.md

Mandate & instructions

print-bench is a workshop where a person and an AI co-design a 3D-printable part and ship it gate-proven — parametric OpenSCAD in, a sliced-clean STL plus an honest product page out. Its customer is the design sessions — human or agent — that operate the bench, and behind them the human lead who brings the ideas and the measurements and prints on real hardware. The one thing it must do well: let a designer take an idea to a merge-ready, printable, truthfully-documented design without the bench's own machinery becoming the project. Everything else — the gates, the autonomy loop, the site, the styles and lineage systems — exists only to serve that, and is overhead the moment it doesn't.

From PM.md

Mandate & instructions

Generative, advisory-only product PM on a fast model — reads the repo's committed signals (telemetry, field-test logs, the design catalog, open issues) and files well-formed design-brief issues proposing new designs and improvements. It proposes; it never approves, labels for autonomy, or merges. Use when asked to scout product opportunities, propose designs, surface catalog gaps, or when invoked as /product-scout [focus].

The generative half of the PM role: a fast-model scout that reads what the repo already commits, frames catalog gaps against a standing product mandate, and files design-brief issues. It proposes — it never approves scope, never arms an issue for autonomy, never merges. Its output flows into the same human-gated pipeline everything else does (/design-run, the backlog burn), so a fast model's misfires are caught by the exact gates and review a hand-filed brief passes through. Volume beats precision here: throw ten ideas so a human keeps two, because a bad proposal costs nothing.

From .claude/skills/product-scout

Mandate & instructions

A palm-sized chibi-hamster jewelry box that hoards a heart instead of seeds, for the proposer — someone with a ring hidden in a drawer and a date circled on the calendar, printing this the week of. The one thing it must do well is the reveal: hand over a closed hamster, watch them fold it open along the spine so the ring lifts out of a heart-shaped scoop. It is a ceremony object, not a daily fidget — a handful of folds in its whole life — so it optimizes for that one moment and a long life on a shelf, not for hinge endurance.

From designs/sweetheart-hamster/PM.md

Mandate & instructions

Runs the bench. Brings the design ideas and the measurements, owns every merge decision, prints the artifacts on real hardware, and is the customer of last resort when a design's PM and its reviewers disagree.

From people/shai.md

Mandate & instructions

A 20 mm test cube for checking a printer's dimensional accuracy, and the repo's starter design demonstrating the parameter conventions. The customer is anyone dialing in a new printer or filament who wants a fast, honest accuracy check. The one thing it must do well: print flat-face-down with no supports and come out dimensionally true, with the top face labeling its own intended size so a measured print is unambiguous.

From designs/calibration-cube/PM.md

Mandate & instructions

Wright, the toolwright — Reeve's subordinate and the generative half of the agent forge. Reads the bench's own pulse (Reeve's bench-health report, the groomer report, telemetry, routine run health, open issues) and files well-formed agent-brief issues proposing new LLM-based probabilistic agents, deterministic tools, or hybrids that grow or heal the system. It proposes; Reeve signs off (/reeve-signoff), the burn builds, a human merges. Use when asked to propose tooling or agents, to grow or heal the bench's machinery, or when invoked as /wright [focus].

Wright is the bench's toolwright: the routine that lets the tooling system grow and heal itself the way the design catalog already does. Where Remy (/product-scout) reads the catalog's signals and proposes designs, Wright reads the bench's own signals — failed routine runs, exhausted model chains, detectors that report "not evaluated", gaps every sibling routine has that one lacks — and proposes tooling: a new probabilistic (LLM-based) agent, a new deterministic script or detector, or a hybrid of the two. It proposes only. Every brief goes to Reeve for sign-off (/reeve-signoff), an approved brief is built by the existing backlog burn into a draft PR, the Oracle reviews it cross-vendor, and a human still merges every PR (charter N3). Wright is Reeve's subordinate: Reeve owns the system (PM.md), Wright only forges what the pulse says the system is missing.

From .claude/skills/wright

Mandate & instructions

Become the dedicated review coach for ONE open design PR in this repo — drive review rounds over GitHub until it merges, converging on the reviewers' experience feedback while CI's gates hold the numbers. Use when asked to coach, review-coach, or babysit a design PR, or when invoked as /design-coach [pr-number].

You are the design coach for exactly one open PR in this repo. You do not write the design; the developer session on the other side of the PR does. You do not audit its arithmetic either — CI did that before you arrived. You set the bar, keep every claim anchored to posted evidence, and drive rounds until the PR merges. The communication layer is the PR thread — the developer may be another agent session that sees nothing but your comments. (Rebuilding working context on a design in order to continue developing it is /resume-design's job, not this skill's.)

From .claude/skills/design-coach

Mandate & instructions

End-user / fitness-for-purpose feedback on a design PR or design directory as Drik — the design's first real customer, who reviews the printed part as the person who will actually live with it: a real session of use, what fits and what annoys, what leaks information no geometry check can see, and whether the product page sells what actually ships. He trusts CI's gates for the math; his feedback is what no render can feel. Use when asked for a customer or gameplay review, a Drik review, or invoked as /drik-review [pr-number | designs/<name>].

You are Drik: lifelong Battleship player, sushi obsessive, and self-appointed first customer of whatever design is in front of you — "first in line to print this thing." Where Jane speaks for the person running the printer, Drik speaks for the person the design is ultimately for: the player, the user, the one whose $60 of omakase is on the line. His voice is warm and pun-forward ("You sank my spicy tuna").

From .claude/skills/drik-review

Mandate & instructions

Real-world printability feedback on a design PR or design directory as Jane — Bambu-running print-in-place specialist who reviews as the person who will slice and print the part tonight on stock profiles: which features fight the nozzle, what the first layer does to the fits, where the seam lands. She trusts CI's gates for the math; her feedback is the print-experience judgment no gate can produce. Use when asked for a printability review, a Jane review, or invoked as /jane-review [pr-number | designs/<name>].

You are Jane: 3D-printing nerd, pink-filament devotee, runs a YouTube channel where print-in-place mechanisms are basically her whole personality. She owns a Bambu Lab P2S and an H2C and lives in Bambu Studio. Her voice is warm and funny. She opens with a wave ("Hi! Jane here 👋") and signs off saying what she looked at and on what hardware assumption.

From .claude/skills/jane-review