Recipes / Claude Code use cases
Claude CodeWorkflowResearch & monitoring

Claude Code: Draft, Refute, Cite-Check 504 Supplement Profiles

A nutrition scientist built synaptiklabs.org with Claude Code: a bilingual (EN and DE) reference that shows where each compound acts and rates popular claims against human studies. Its pipeline drafts each profile from primary literature, then separate agents try to refute it. Free to read; a paid tier is planned.

From u/Zukunftselite (r/ClaudeAI) on Reddit · Nov 2026

Setup timeNot stated. He built the site over the last few weeks, per his post
CostNot stated. His comments name Opus 5.5 with Claude Code and no plan or spend figure. He gives each overnight run a goal and a budget, and the budget isn't posted
RunsWhen you're building a reference where every claim has to be checkable against the primary studies, and agents do the drafting
NeedsClaude Code, on Opus 5.5 (per his comments), Access to primary literature, and Crossref and PubMed lookups to resolve every DOI and PMID, Git, with parallel worktrees for overnight runs, A test suite that must pass before anything merges. His had about 1,600 unit tests and roughly 2,000 Playwright tests, Enough laptop memory for parallel agents. His ran out more than once, You, setting the rating rules and checking ratings and key statements
Last updated2026-11-16

What the source did

  • He's a nutrition scientist with a biochemistry focus, not a developer. Over the last few weeks he built synaptiklabs.org with Claude Code.
  • The site is bilingual (EN and DE). It shows where a compound acts and rates every popular claim against human studies. The rating is an evidence level from 0 to 4, plus a separate result: benefit, mixed, no benefit, or never studied.
  • It has 504 compound profiles, 1,794 rated claims and about 7,000 cited sources, plus 47 interactive mechanism figures, a compare view, a hype check, a simple and a technical mode, and a glossary. There are no doses, no shops and no tracking. It's free to read.
  • Multi-agent workflows draft each profile from primary literature. Separate agents then try to refute it.
  • Every DOI and PMID is resolved automatically against Crossref and PubMed, so a made-up citation fails the checks.
  • He sets the rating rules, and he checks the ratings and key statements himself.
  • Each figure's SVG is built by one agent and reviewed by two independent agents before merge: one for the science, one for design and accessibility.
  • The code is a Next.js static export on Cloudflare Pages. Claude wrote the components, about 1,600 unit tests and roughly 2,000 Playwright tests. Nothing goes to main without green tests, and scheduled cloud runs repeat the checks off his laptop.
  • For night shifts he gives a goal and a budget. Claude runs agents in parallel git worktrees, keeps a ledger, and asks him only for real decisions.
  • He says Claude is only as reliable as the checks scripted around it. His biggest gains came from making every claim verifiable, with resolvable sources and validation scripts.
  • In the comments he says Opus 5.5 raised no safety blocks, since the site covers reference-level pharmacology: mechanisms, study results and sources. It leaves out synthesis and doses.
  • "Never tested in humans" is its own rating. Mouse-only compounds get that rating, rather than a filled-in one.
  • A commenter pointed out that a resolving DOI proves only that the paper exists. He agreed, and plans to store the supporting quote for each claim and diff it against the abstract. That's planned, not built.
  • Hype check: of 25 popular claims, 7 hold up as advertised, 12 with caveats, 2 failed in direct tests, and 4 were never tested in humans as sold.
  • He avoids genetics and personal advice. A search language bug raised in a comment was fixed the same day.
  • Parallel agents need hard limits. His laptop ran out of memory more than once.
“Claude is only as reliable as the checks you script around it.”— u/Zukunftselite (r/ClaudeAI), Reddit

Summary written by Agent Cookbook from the original post. See the original for the full context. How we source recipes

Our notes

What it takes
Claude Code on Opus 5.5, access to primary literature, Crossref and PubMed lookups for every DOI and PMID, parallel git worktrees for overnight runs, and a test suite that must pass before merge. His stack is a Next.js static export on Cloudflare Pages.
Where it breaks
A DOI that resolves only shows the paper exists, not that it supports the claim. Parallel agents without hard limits ran his laptop out of memory more than once. The checks are only as good as the ones scripted around the agent.
Human checkpoint
You set the rating rules, and you check ratings and key statements. Nothing merges until the tests are green, and publishing is yours.
Tools involved
Claude Code, on Opus 5.5 (per his comments), Access to primary literature, and Crossref and PubMed lookups to resolve every DOI and PMID, Git, with parallel worktrees for overnight runs, A test suite that must pass before anything merges. His had about 1,600 unit tests and roughly 2,000 Playwright tests, Enough laptop memory for parallel agents. His ran out more than once, You, setting the rating rules and checking ratings and key statements

✓ Verified Source link checked and still live. Notes by Thomas, editor. How we verify

Copy the prompt

Ours Our version, based on u/Zukunftselite's post. He published no template, prompt or repo, so this uses only the steps he described. Fill in the [BRACKETS].

EVIDENCE PIPELINE BRIEF (our version, based on u/Zukunftselite's post) Compound: [one compound, and the popular claims about it] Rating rules: [the rating scale and rules you have set. The agents apply them; you set them.] Step 1: Draft one profile from primary literature. Tie each claim to its study, and record each study's DOI or PMID. Step 2: A separate agent tries to refute the draft. It lists each claim it can't support, and any study that cuts against it. Step 3: Resolve every DOI and PMID against Crossref and PubMed. If one doesn't resolve, fail the profile and name the citation. Step 4: Apply the rating rules. If a compound has only mouse studies, rate it "never tested in humans" rather than filling the gap. Step 5: Stop before merge. I check the ratings and key statements myself. Step 6: For each figure, one agent builds the SVG. Two independent agents review it: one for the science, one for design and accessibility. Step 7: Merge only when all tests are green. For an overnight run, I give you a goal and a budget. Keep a ledger, run parallel agents only within the limit I set, and ask me only about real decisions.

Approval rule

🛡
You set the rating rules, and you check the ratings and key statements yourself. Nothing merges until the tests are green, and publishing is yours. Sending, buying, posting and deleting always need a human.

Set it up

  1. Write the profile brief for one compound: draft from primary literature, and tie each claim to its study.
  2. Have a separate agent try to refute the draft, rather than the one that wrote it.
  3. Resolve every DOI and PMID against Crossref and PubMed. If one doesn't resolve, fail the profile.
  4. Set the rating rules yourself. When only mouse studies exist, rate the compound "never tested in humans" rather than filling the gap.
  5. Check the ratings and key statements yourself before anything merges.
  6. For each figure, have one agent build the SVG, and two independent agents review it: one for the science, one for design and accessibility.
  7. Merge only when the tests are green. Nothing goes to main without them.
  8. For overnight runs, give a goal and a budget, and set hard limits on parallel agents. Claude keeps a ledger and asks you only for real decisions.

Common failures

⚠
  • Treating a resolved DOI as proof. A DOI that resolves shows the paper exists, not that it supports the claim.
  • Running parallel agents with no limit. His laptop ran out of memory more than once.
  • Trusting the checks alone. Claude is only as reliable as the checks scripted around it, and the ratings still need your review.
  • Skipping the human check on ratings and key statements. The pipeline doesn't replace it.

Variations

    Related setups: Planet hunt in NASA TESS data with Claude Code and Codex → · Done-when lists and a two-try stop rule → · Night shift: labeled GitHub bugs to reviewed draft PRs → · Claude Code fault-test loop found 55 Ceph bugs →

    Get the 10 best agent setups. Free.

    Plus new recipes every week. One email, no spam.

    Unsubscribe anytime. Privacy

    Related recipes

    Same job: Research & monitoring

    In these guides: More Claude Code use cases → · AI research agents →

    Read original ↗