hraness

reference

the architecture behind the projects, organized into categories that will grow into lessons and courses.

each category maps one theme to the projects that already implement it and lists the lessons planned for it. lessons land under their category as they are written.

  1. prompting100 sessions · techniques, metrics, and examples
  2. agent infrastructuredurable sessions, orchestration, and review for coding agents.5 planned lessons
  3. local-first softwareowning state on the device, syncing on the owner's terms.4 planned lessons
  4. knowledge systemsmarkdown vaults, retrieval, and evidence beside the code.4 planned lessons
  5. web deliverymetadata, sitemaps, social images, and honest public surfaces.4 planned lessons
  6. design systemsprimitives, tokens, and brand catalogs shared across products.4 planned lessons
  7. browser mediaaudio, midi, and generative media in the browser.4 planned lessons
  8. accounts and commerceshared identity, billing, and marketplaces without leaking trust.4 planned lessons
  9. the factoryone engineer, many products: monorepo operations and agent workflow.4 planned lessons

AI-drafted at Ben Guo's direct request as category seeds; each planned lesson is unpublished until it is written.