/TEMPLATES — FORK FREELY
STARTER FILES
WE ACTUALLY USE.
MCP server starters, n8n workflows, Claude Code skills, prompt templates, and MVP scaffolds — the same files the studio uses on client builds. Apache 2.0 / MIT. Fork freely. Some are live now, most are being published as we ship them.
For workshops that teach how each of these is built → Express Intent
/MCP SERVER STARTERS
/01
in-progressTypeScript MCP Server
Minimal TS MCP with tools, resources, prompts. OAuth, audit logging, Docker deploy.
/02
in-progressPython MCP Server
FastAPI + MCP SDK. Production-ready Python starter.
/03
plannedPostgres MCP Server
Read-only Postgres MCP with row-level security and audit logs.
/04
plannedHubSpot MCP Server
OAuth-flow HubSpot MCP exposing contacts, deals, companies with scoped permissions.
/n8n WORKFLOWS
/01
plannedLead → CRM → Email
Form submission → CRM contact creation → personalized followup email sequence.
/02
plannedInvoice → Stripe → Slack
Invoice paid event → Slack notification + bookkeeping entry + customer welcome.
/03
plannedDaily Reports → Email
Aggregate yesterday's data from Postgres → format → email-ready summary.
/CLAUDE CODE SKILLS
/01
plannedService Page Generator
Generate a full service detail page from a 1-line description. Used to ship 10 service pages in 1 hour on this site.
/02
plannedBlog Post Scaffolder
Create a new blog post route with JSON-LD, OG image, breadcrumb, and starter copy.
/03
plannedSitemap Auto-Updater
Detect new routes in the app/ dir and add them to sitemap.ts on save.
/PROMPT TEMPLATES
/01
plannedScoping Doc Generator
Turn a discovery call transcript into a 1-page scoping doc.
/02
plannedService Page Writer
Generate honest, anti-hype service page copy in the studio's voice.
/03
plannedCode Review Reviewer
Adversarially review PR diffs, flagging real bugs vs surface-level nits.
/MVP SCAFFOLDS
/01
plannedNext.js + Supabase SaaS
Full SaaS starter: auth, Stripe billing, multi-tenant, admin dashboard, dark mode.
/02
plannediOS App + Backend
SwiftUI app + Next.js backend + Postgres. Shared types via OpenAPI.
/HOW THESE GET PUBLISHED
These templates come from real client work. We extract the reusable bits, sanitize the client-specific parts, document them, and publish under Apache 2.0 / MIT. Most live in github.com/enochodu1.
If you're looking for a template that doesn't exist yet, mention it on a discovery call. Sometimes we'll prioritize publishing it as part of the engagement.
NEED IT BUILT FOR YOUR STACK?
Templates are starting points. Production custom builds are scoped on a discovery call.