How to Use This Playbook
Use the playbook like an engineering program, not a book.
Operating model
- Read the overview page for a layer.
- Implement the small examples.
- Complete the mini exercise.
- Build the layer project.
- Publish the repo, screenshots, architecture, and write-up.
Weekly rhythm
- Day 1: concept pass and diagram review
- Day 2: TypeScript implementation
- Day 3: Python implementation or backend variation
- Day 4: exercise and extension work
- Day 5: project milestone and documentation
How to get portfolio value
- treat every project as a standalone repo or documented subproject
- add screenshots, API examples, Mermaid diagrams, and metrics
- write one short engineering note per layer
- record a two to five minute demo for each major project
Suggested learning path
- If you are new to LLM applications, start at Layer 1 and move sequentially.
- If you already build LLM apps, start at Layer 3 or Layer 4 and come back to fill gaps.
- If your goal is consulting or internal platform work, prioritize Layers 2, 4, 6, and 7.
- If your goal is product or startup work, prioritize Layers 1, 3, 5, and 8.