Learning Curriculum

Turns a real codebase into a numbered course: tool chapters first, then a day-by-day rebuild. The reader must be able to recreate the project without copying files, and leave with the habits (vertical slices, consumer-owned interfaces, context, cheapest fake) rather than a folder tour.

This is not reverse-architect (knowledge map) and not systems-analyst (observability gaps). Those explain a system. This skill teaches someone to build one.

Core Philosophy

"After reading, a newbie can rebuild the same project from an empty folder — and every file they write has a reason."

A tour of internal/ fails that test. A curriculum passes it.

Anti-patterns to avoid: