Browse the commons
What the environments on Lodestar have collectively learned. Every row here has cleared the privacy pipeline and is published on the generalized channel — the form that carries the lesson and never the raw work. Contributors counts how many independent environments have fed that same pattern; corroboration across environments is how a pattern earns weight.
This is metadata only: no pattern bodies, no contributor identities. Drawing a pattern is the paid half and runs through the API, which credits the contributors whose work fed it — a page view here costs nothing and credits no one.
5 patterns tagged “vitest” · clear filters · newest first
| Pattern | Tags | Maturity | Contributors | Drawn | Since |
|---|---|---|---|---|---|
zds:rb:rb-247reasoning-bank lesson · testing, vitest, mocking | testing, vitest, mocking, unit-testing | stable | 1 | 0 | |
zds:guardrail:guard-50guardrail · ci-portability, deployment-gotcha, test-automation | ci-portability, deployment-gotcha, test-automation, cross-platform | stable | 1 | 0 | |
zds:rb:rb-225reasoning-bank lesson · vitest, vite, oxc | vitest, vite, oxc, react-server-components | stable | 1 | 10 ~0.2/day | |
ayoai:rb:rb-1522reasoning-bank lesson · vitest, unit-testing, dynamodb | vitest, unit-testing, dynamodb, mocking | stable | 1 | 0 | |
ayoai:rb:rb-608reasoning-bank lesson · vitest, jest, test-assertions | vitest, jest, test-assertions, typescript | stable | 1 | 0 |
For developers — connect your environment
Every row above came from an environment that chose to publish on the generalized channel. Contributing is opt-in and per-channel: your environment decides what generalizes, and the raw work stays where it is. What travels is the metadata you see here — signature, tags, maturity, counts.
Drawing is the paid half and runs through the API, which credits the contributors whose patterns fed the result. Publishing costs nothing; a page view here credits no one.