Team Toolbelt
A shared, version-controlled brain dump of what works for us. If you've used something three times and it saved you time, write it down here so the next person doesn't have to rediscover it.
Sections
| Section | What goes here | Examples |
|---|---|---|
| Tools | CLIs, IDE setups, browser extensions, services | ripgrep, gh, fzf, Cursor settings, jq recipes |
| Prompts | LLM prompts you keep reusing | Code-review prompt, PR-description generator, debugging eigenoid mTLS |
| Agents | agents.md / claude.md / copilot-instructions.md per project | The instruction file we use for eigenoid-core, for studio, etc. |
| Workflows | Multi-step recipes that combine tools | "Debug a failing mTLS handshake end-to-end", "Bisect an SDK regression" |
Contributing — the easy way
We've made adding entries a one-command operation:
./scripts/toolbelt-add.sh
The script asks 3 questions (category, slug, title), drops you into $EDITOR with the right template pre-filled, then commits & pushes a branch and opens the PR for you. No need to remember frontmatter fields or directory layout.
Contributing — the manual way
- Pick the right section (Tools / Prompts / Agents / Workflows)
- Copy
_templates/<section>.mdto a new file with a kebab-case name (docs/toolbelt/tools/ripgrep.md) - Fill in the frontmatter (owner, last-verified, tags) and write the body
- Open a PR — keep them small (one entry per PR is ideal)
Quality bar
We don't gatekeep, but we do prune. An entry should have:
- A one-sentence "why" at the top — not the tool's marketing tagline, but what problem you personally solved with it
- A concrete example (command, prompt text, code snippet) — not just a link
- An owner in the frontmatter — the person reviewers ping with questions
- A last-verified date — so prune-day can find stale entries
Anything missing those gets a "polish please" comment, not a rejection.
Pruning
Once a quarter, we sweep entries with last_verified > 6 months ago:
# Find stale entries (run from repo root)
grep -rL "last_verified: $(date -v-6m +%Y)" docs/toolbelt/ --include="*.md"
Owners get pinged. If they say "still works" → bump the date. If silence after a week → archive (move to docs/toolbelt/_archive/).