Use cases
The daily engineering activities — understanding a codebase, building and changing it, shipping and operating it, running infrastructure, and planning and deciding — and how Vörr AI and CodeZero change each one. Every page covers the operations involved, copyable prompts, step-by-step workflows, what Claude Code or ChatGPT can already do on their own, and what the products add.
CodeZero for work inside VS CodeVörr for system context in Claude, ChatGPT or another MCP assistant
Start here
Where AI-assisted engineering gets stuck, how the two products divide the work, and what the research says.
01 · Use caseWhere AI engineering gets stuckWhat Claude Code and ChatGPT already do well, the nine places they recurrently get stuck and why, and which use case covers each one.02 · Use caseHow Vörr AI and CodeZero work togetherVörr knows the running system; CodeZero knows the code and carries the change. What each does, where it runs, and how findings move between them.03 · Use caseWhat the research says about AI and engineering contextPublished figures on AI-generated duplication, trust, delivery stability and tool sprawl, what each one points to, and where that problem is handled.
Understand the system
Learn a codebase, map the architecture across code and cloud, and answer questions about the system.
04 · Use caseUnderstand and onboard to a codebaseLearn an unfamiliar codebase, including the repositories you haven't cloned, how a feature runs end to end and where it runs.05 · Use caseUnderstand system architectureMap how services, data and infrastructure connect across code and cloud, with evidence for every edge.06 · Use caseAnswer system questions without the IDEAsk Vörr from Claude or ChatGPT where something lives, what it depends on, whether it's healthy, what shipped and who owns it, and get sources with every answer.
Build and change
Build features, change code across repositories, refactor, test, review and hand off approved work.
07 · Use caseBuild a featureFind existing patterns and helpers, reuse instead of re-create, find where config is really set, plan, implement, test and check it in production.08 · Use caseShip a cross-repository changeFind every consumer in every repository, agree how old and new coexist, plan per repository and check each service after release.09 · Use caseRefactor or upgrade safelyRename, change a signature, move or delete code, or upgrade a dependency, with every caller in every repository found first.10 · Use caseWrite and run testsFind the tests that protect a behaviour, close gaps for callers in other repositories and turn production errors and CI failures into tests.11 · Use caseReview a pull requestReview what a change affects beyond its diff: the plan behind it, consumers in other repositories, contracts, config, tests, owners and the services it lands in.12 · Use caseDelegate approved workGet a plan into a state the agent can finish on its own, run it task by task or in Coffee Mode, and review what it did when you return.
Ship and operate
Deploy, debug production, run incidents and keep watch on service health.
13 · Use caseInvestigate deployments and CI failuresDiagnose a failed build or rollout, find the change behind it, fix it through a plan and check what actually shipped.14 · Use caseDebug a production errorGo from an error or latency signal to the deploy, the service, the code path and a verified fix.15 · Use caseFrom incident to fixTriage, size the blast radius, build the timeline, decide a mitigation, confirm recovery and ship the permanent fix.16 · Use caseMonitor service healthHealth, SLOs, alerts, dashboards and baselines across every connected observability tool, with sources and coverage on each answer.
Infrastructure, security and cost
Understand cloud infrastructure, review exposure and reduce spend.
17 · Use caseExplore cloud infrastructureInventory, mapping gaps, Terraform coverage, Kubernetes usage and blast radius across your cloud accounts.18 · Use caseReview security and exposureFind what is internet-facing, follow each exposure path end to end, and back every zero with scan coverage.19 · Use caseReduce cloud costFind AWS spend, waste, savings and rightsizing candidates, and tie them back to owners, dependents and code.
Plan and decide
Plan product work, make engineering decisions with evidence, and keep context shared across the team.
20 · Use casePlan product workScope product work against the real system: how a feature works today, what a change touches, whether it shipped and how healthy it is.21 · Use caseMake engineering decisionsTech debt, build versus reuse, ownership, change risk and deprecation, decided with evidence from code and production.22 · Use caseKeep context across the teamKeep engineering context in the organisation's index, feature names, verified dependencies and service map, so every assistant reads the same system.