Curate A Team Library

It enforces a five shelf system (frontend, backend, mobile, workflow, agent-engineering), makes you browse before curating, and won't let you skip the whyHere field that explains why each skill actually belongs. The workflow keeps libraries small at first, uses explicit curator metadata on every mutation, and builds toward a starter pack collection once you have solid picks. It's opinionated about not hand-editing JSON files and about writing branch names that mean something. Use this when you're setting up a shared library for a real stack and want someone else to trust what's in it.