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
| Chapter | Build | Printed address |
|---|---|---|
| 0 | 00-reading-code | /ch00 |
| 2 | 02-what-an-agent-does | /ch02 |
| 4 | 04-first-session | /ch04 |
| 6 | 06-prompting-like-a-reviewer | /ch06 |
| 7 | 07-verification-gates | /ch07 |
| 8 | 08-git-and-environments | /ch08 |
| 9 | 09-literature-triage | /ch09 |
| 10 | 10-statistics-assumption-checks | /ch10 |
| 11 | 11-survival-and-dose-response | /ch11 |
| 12 | 12-publication-figures | /ch12 |
| 13 | 13-sequence-and-omics | /ch13 |
| 14 | 14-docking-prep | /ch14 |
| 15 | 15-image-and-plate-reader | /ch15 |
| 16 | 16-lab-data-management | /ch16 |
| 17 | 17-manuscript-assembly | /ch17 |
| 18 | 18-deposition | /ch18 |
| 19 | 19-grant-and-thesis-drafting | /ch19 |
| 21 | 21-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.
science.nexagenlabs.com/ch00science.nexagenlabs.com/ch02science.nexagenlabs.com/ch04science.nexagenlabs.com/ch06science.nexagenlabs.com/ch07science.nexagenlabs.com/ch08science.nexagenlabs.com/ch09science.nexagenlabs.com/ch10science.nexagenlabs.com/ch11science.nexagenlabs.com/ch12science.nexagenlabs.com/ch13science.nexagenlabs.com/ch14science.nexagenlabs.com/ch15science.nexagenlabs.com/ch16science.nexagenlabs.com/ch17science.nexagenlabs.com/ch18science.nexagenlabs.com/ch19science.nexagenlabs.com/ch21Every 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.
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.
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
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.