Action guide

Setting Up AI Projects in Python

Your AI repo outgrew the demo script. Env files, pyproject, src layout, and a clean split between HTTP surfaces and agent code.

Get the full guide

Free newsletter unlocks the full guide and subscriber links. Same library working engineers use. No pedigree bingo.

Free. No spam. Unsubscribe anytime.

Why subscribe

The repo that worked Saturday dies by Wednesday. You need a folder tree you can explain at 3 a.m. Env files. Packaging. Obvious homes for HTTP code versus agent code so nobody asks where the bodies are buried.

For: Engineers building Python AI services who still own the repo after the demo glow fades. Structure beats pedigree.

  • A repo layout that scales past the first happy path
  • Clear seams between API routes, domain logic, and agent code
  • A setup that makes iteration and handoff less bruising
  • Full project walkthrough with a concrete tree
  • Config and environment patterns that do not rot on M1 and Linux
  • A template you can clone for the next product
  • Optimizes for the problems that show up in review, not tutorial minimalism
Terminal-style project tree: .env and .env.example, pyproject.toml, src package with api routes and agents folder for LangGraph or LangChain

What you’ll learn

How to organize a repo so it stays shippable: .env vs .env.example, what belongs in pyproject.toml, a src/ importable package, and why api/ (FastAPI app, routers, health) stays separate from agents/ (graphs, executors) so HTTP concerns do not tangle with model logic.

When you subscribe to the newsletter, you get access to the full online guide alongside course and issue updates.

Explore the other action guides

Each guide kills one sharp problem. You leave with steps you can type, not inspiration quotes.

Unlock the library

Free subscription. Full guide access. Future drops included. Same files I email to people who ship.

Free. No spam. Unsubscribe anytime.