Documents in; training, a rota and sourced answers out.
Next.js · Supabase pgvector · Claude · Inngest · Stripe
357 × 446Restaurants have their rules written down. Staff don't read them.











Documents in; training, a rota and sourced answers out.
Next.js · Supabase pgvector · Claude · Inngest · StripeAsk, read, sign off and train from a phone. On the App Store and Google Play.
Flutter · Firebase messagingMarketing site, pricing and ten UK-law guides, built to be found.
Next.js · structured data · llms.txtHow I run the business: customers, revenue, AI cost per feature, health checks.
Stripe · PostHog · Sentry · GitHub + Vercel APIsClaude proposes posts and I approve them; they render, schedule, publish and report back.
Instagram API · Inngest · SatoriSourcing, email, calls and visits, with PostHog and Search Console showing what works.
Notion · Gmail · Vercel cron · Search Console













Liftio is replaced, not relaunched.
"Retiring a live record to avoid an untidy string is paying a real cost for a cosmetic one."

Running tracker with an AI training coach.
Flutter · GPS · shared design systemStrength log with a coach of its own. The rebuild of Liftio.
Flutter · shared design systemOne account across both apps. The coach plans around your whole week.
Supabase · Edge Functions · OpenRouter · RevenueCatScroll film, waiting list, support and legal pages. No tracking, by design.
Next.js 16 · Replicate clipsPosts drawn in Remotion from the site's own words, published through the Instagram API.
Remotion · Instagram APIStore listings and submissions run from Claude Code; builds on Codemagic.
App Store Connect · Google Play · Codemagic






Building things has always been how I think. Before I knew what programming was, I was pulling things apart to see how they worked.
I run MGKCodes, the studio behind frunt and MGKFitness.



Every screen laid out on one board, each with what it's for.
e.g. Lift screen board, v11Big calls written down with the reasoning, so they can be checked.
e.g. Decision 0001AI does the typing. My own skills library sets how it works.
e.g. github.com/MattKay02/skillsScreens checked by eye, design reviews, a build check on every PR.
e.g. 19 findings, 30 Sept reviewStore submissions with a written record of what went out.
e.g. Run 1.0, 2 Oct 2026