Ship something. Send it back.

Why contribute

Every section of this curriculum exists because someone hit a wall, found their way around it, and wrote the path down. The first version came from people sending me what worked. This version is the same. If you spent eight hours figuring something out, you’ve already done the hard work; writing it up takes another hour and saves the next person seven of theirs. That’s the whole loop.

Submit a template

The template library in section 8 is going to grow. The way it grows is people sending in templates that worked for them.

If you build something that:

• Solved a real business problem.
• Took you longer than 8 hours to figure out.
• Could be reused by someone in a similar situation.

…it’s a candidate for the library.

Categories we want to grow:

• Spec-writing templates for specific industries.
• Project-type templates beyond websites, dashboards, and APIs (kiosks, mobile apps, hardware projects).
• Agent templates for specific workflows (legal review, HR onboarding, customer support tier 1).
• Hardware setups (specific Mac mini configurations, NVIDIA builds, multi-GPU rigs).
• Domain-specific data shapes (real estate, medical, education, manufacturing).

What we don’t want:

• Templates that hardcode secrets.
• Templates that don’t follow the verification habit.
• Templates that are just “wrappers around frontier APIs” with no real value-add.
• Templates pushing a specific paid SaaS product without disclosing the relationship.

Report a correction

Typos, broken links, outdated pricing, factual errors. File one of these and it gets read; the curriculum gets fixed in the next pass.

Suggest a glossary term

If a term in the curriculum tripped you up, it should be in the glossary. File a suggestion; if it tripped you, it’ll trip someone else.