Skill tree Β· mind map Β· course curriculum
36 skills, 6 tiers β from how the model works to shipping AI in production. Each skill has why it matters, a mastery check, the pitfall to dodge, and hand-picked resources. Every tier ends in a project you actually build.
Tier I Β· Foundations (7 skills)
Analogies before mechanics β skip token math and architecture diagrams; "training" explained as practice, not programming.
Predict-the-next-word by hand, then compare to what the model does.
Tier II Β· Prompting (5 skills)
Full depth β the highest-leverage skill for this audience. Structured output taught as plain-English templates, not JSON schemas.
Iterate a prompt for one real work task five times, logging what changed.
Tier III Β· Code with AI (6 skills)
Reframed from "coding" to "directing" β read the diff, catch obvious wrongness, learn what you don't understand yet.
Build one small real thing end-to-end, described entirely in English.
Tier IV Β· Extend your agent (6 skills)
Conceptual only for MCP, agents, hooks β "build a plugin" becomes a guided walkthrough, not a build.
Install one existing MCP server; describe in plain English what Claude could newly do.
Tier V Β· Build into products (7 skills)
Skip the API/streaming/fine-tuning labs. RAG and evals stay conceptual: why the AI needs your docs, how you'd know it's working.
Use a hosted no-code RAG builder to make a small Q&A bot over a real document set.
Tier VI Β· Production & frontier (5 skills)
Full depth on security and responsible AI β matters regardless of coding skill. "Cost & scaling" becomes "why AI answers aren't free."
Write a one-page AI usage policy: what never to paste into a prompt.
Ship one small, real, personally useful AI-assisted tool β built with heavy AI assistance, presented as what it does, what you directed, and what you checked before trusting it.
Tier I Β· Foundations (7 skills)
Read the tier's curated resources β Karpathy, 3Blue1Brown, the attention paper. Conceptual grounding only, no lab.
Explain training vs. inference and why hallucination isn't a bug β unaided, one paragraph.
Tier II Β· Prompting (5 skills)
Build a versioned prompt library for a real repeated task in your own work, with structured output specs.
Peer-review another learner's library for the context-engineering pitfall.
Tier III Β· Code with AI (6 skills)
A full week shipping a real feature exclusively through an AI coding assistant β every diff read before accepting.
Submit the PR; a reviewer checks specifically for signs you didn't read your own AI-generated code.
Tier IV Β· Extend your agent (6 skills)
Build and ship one actual plugin or MCP server β the tree's own tier project.
Someone else installs and uses it without your help.
Tier V Β· Build into products (7 skills)
Build a small RAG-backed feature against the raw API β no framework β covering streaming, tool use, and a basic eval harness.
Present the eval results: what the harness catches, what it misses.
Tier VI Β· Production & frontier (5 skills)
Security pass (OWASP-style) on the Module 5 project, plus a cost estimate at 10x current usage.
Red-team someone else's Module 5 project for prompt injection.
Ship a real MCP server or Claude Code plugin, published even privately, with a security review and a cost/scaling note. Strong capstones are candidates for actual inclusion in the Plugboard directory.
This syllabus wraps the skill tree's own resources β these are separate, complete courses worth doing alongside it, one pick per track.