Docs / Features
Context Packs
Teach Reverbic your stack once, and stop re-explaining it in every prompt.
A Context Pack is the project knowledge that should travel with every task: what you are building, what it is built with, where things go, and what an agent should never do. Define it once and it is applied whenever Reverbic distills work for that project.
What goes in a pack
- Stack
- Languages, frameworks, database, hosting — the things that determine whether generated code fits.
- Architecture
- How the codebase is organized and where new code belongs.
- Conventions
- Naming, file placement, testing expectations, migration style.
- Key files
- The files that matter for orientation.
- Constraints
- Hard rules — what must not be touched, changed, or introduced.
- Key terms
- Domain vocabulary. Also primes transcription so these words come through correctly.
- Agent instructions
- Anything that should be prepended to a spec handed to a coding agent.
Multiple active packs
More than one pack can be active at a time — useful when a meeting spans a frontend and a backend, or a product area and a shared library. Packs can also be shared organization-wide so your whole team distills against the same conventions instead of each person's private version.
Binding a pack to a meeting
A pack can be attached at record time, at upload time, or on a text or Loom import. Whatever is bound is snapshotted onto the meeting, so a later edit to the pack does not silently change what an old meeting was distilled against. You can re-bind a different pack from the meeting page.
Note
Start from a template if you are not sure what to write. Settings → Context includes starter templates you can edit rather than beginning from an empty box.
Why this matters more than it sounds
Most of the correction cycle with a coding agent is not about the task — it is about the project. Without a pack, the same standup produces three different implementations depending on who prompted the agent and what they remembered to mention. With one, the handoff is consistent.
Something unclear or missing? Tell us and we'll fix the page.