Resources

Templates and tools from systems that already run.

Everything here comes out of something I use every day. What is ready is free to take. What is still being built is marked, and it lands in The Production Layer first.

Available now

Free to use today

• 

  Claude skillsFree28 skills

  Motion Kit

  Claude skills for branded product animations: 26 motion techniques, a brand setup skill, and an export skill. Every piece is one HTML file, in light and dark.

  What’s inside

  • 26 techniques, from page transitions to charts, type and logo reveals
  • A brand file every skill reads, so each piece matches your product
  • Export to MP4, GIF and WebM, with a quick start and a starter prompt

  Get the kit
• 

  TemplateNotionFree

  Health OS

  A health template that sets itself up by interviewing you. It is the system I actually run, with my numbers taken out and an interview left in their place.

  What’s inside

  • Six databases, a dashboard and a Get Started page, all empty on purpose
  • A thirteen-question interview that writes your protocols, phases and first check-in
  • Works with Claude or ChatGPT through their Notion connectors
  • Not medical advice

  Get the template
• 

  Open sourceMITnpm

  Zengin

  A design system you own, and a deterministic engine that checks every edit against it, whether a person or a coding agent made it.

  What’s inside

  • Thirty-nine components and eight working templates
  • The engine behind an MCP server, an edit hook and a CI check
  • Storybook, six themes and ten font pairings

  npm create zengin@latest

  Read the case study

  Open Zengin
• 

  GuideFreeOnline

  The three engines

  How I run product, content and operations, written up stage by stage, with the limits and failure modes of each.

  What’s inside

  • Product development: a problem, turned into software
  • Content and distribution: a dataset, turned into an audience
  • Operations: what the team learns, turned into owned work

  Read the process

In development

What the engines become next

Not available yet, and no dates. These are the parts of the three engines that would travel to another team: the files and the specs, not the software around them. Each one is announced in the newsletter when it is ready to use.

• In development

  Operations kit

  The loop from meetings, research and surveys to the record, as files: the vault folder structure, the ingestion and briefing specs with their must-not lists, and the governance rules.

  From the operations engine

• In development

  Decision record and story templates

  The vault templates the product engine runs on: decision records in context, decision and consequence form, and user stories tied to a persona.

  From the product development engine

• In development

  Content engine blueprint

  The generate-once pipeline written as specs: grounding against a source of facts, the content registry, and the scheduled distribution.

  From the content and distribution engine