Use cases / Research
Research
Run an architecture decision as an evidence-table research project in Claude
To settle a disputed retrieval-design question for a large enterprise search system, the author kept one Claude Project running for several days with the constraints, past pilots and evaluation setup loaded in. Claude had to update a table of claims, sources and conflicts before writing any conclusion, and to stop and show conflicting numbers rather than average them, which produced a report the author could defend in a design review.
- Tool
- Claude (Opus, Projects and Artifacts)
- Source
- @vantage_vt on X
- Source date
Credit: this use case was shared by @vantage_vt on X. Summary written by Kitbox; see the original for full details.
Try it yourself
Our own starter prompt. Fill in the brackets, then paste it into Claude or your agent of choice.
Starter prompt
We need to decide between [option A] and [option B] for [system]. Our hard constraints are [list]. Keep an evidence table with columns claim, source, primary or secondary, confidence, and conflict flag, and update it before writing any analysis. Ignore benchmarks that don't publish their method. If two sources disagree, show the conflict and stop instead of blending them, and don't recommend anything until I approve the table.
More in Research
- OpenResearch CLI (Claude Code, Codex, OpenCode)Run a local research loop across Claude Code, Codex and OpenCode
- GPT-5.6 Sol deep research and Claude CodeFact-check a rumor with deep research and turn it into a published article
- Claude Code + FirecrawlResearch 25 apps' onboarding flows before designing your own