9.2CORE PATH

Contributing Templates Back

This curriculum has nine templates. You'll write the tenth, the hundredth, the thousandth. Send them back.

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.

Submission process (subject to change as the wiki evolves):

  1. Write up the template using the same format as the existing ones (intro, prerequisites, code or markdown, adaptation notes).
  2. Test it from a clean environment. Imagine someone who's never seen your project trying to use it.
  3. Submit it via the contribution link on internetmenace.com.

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.

Curriculum last updated 2026-04-30