Claude Code for Scientists

Companion code for Claude Code for Scientists: Turn Your Data, Papers and Lab Workflows into Reproducible Pipelines with AI Coding Agents, by Suryaprakash Tripathy.

18 builds, one folder each, in one repository. Clone it once and you have everything in the book. Each build stands alone: open its folder, read its README, run it, then run its gate.

Start here. Chapter 3 sets up the clone, the environment and the requirements, and ends with a script that tells you whether you are ready: science.nexagenlabs.com/setup

Which build belongs to which chapter

ChapterBuildPrinted address
000-reading-code/ch00
202-what-an-agent-does/ch02
404-first-session/ch04
606-prompting-like-a-reviewer/ch06
707-verification-gates/ch07
808-git-and-environments/ch08
909-literature-triage/ch09
1010-statistics-assumption-checks/ch10
1111-survival-and-dose-response/ch11
1212-publication-figures/ch12
1313-sequence-and-omics/ch13
1414-docking-prep/ch14
1515-image-and-plate-reader/ch15
1616-lab-data-management/ch16
1717-manuscript-assembly/ch17
1818-deposition/ch18
1919-grant-and-thesis-drafting/ch19
2121-error-hunt/ch21

Chapters 1, 3, 5, 20, 22 ship no build, so there is no address for them. If you typed one, you are in the right place already.

The builds

Gates

Every build ships the gate that checks its output. A gate exits 0 when it passes and 1 when it fails, which is the convention at a command line. A hook only blocks on exit 2, so a gate wired into one goes through tools/as_hook.py. Chapter 20 explains why, and the gates page points at the list that gives the exact path and both commands for every one.

Tooling

Version numbers, command names and configuration shapes change faster than books do, so no chapter depends on one. TOOLING.md records what each chapter was verified against, with the date. Where the book and that file disagree, the file is right.

References

Appendix D as machine-readable data, with a DOI on every entry that has one and the verification status of each: science.nexagenlabs.com/references

Errata

Corrections to the printed book are listed on the errata page. If you have found an error in the book or the code, please report it: the page says how.