Documents in; cited answers and training out.
Next.js · Supabase pgvector · Claude · Inngest · Stripe
357 × 446Restaurants have their rules written down. Staff don't read them.
I saw it working behind a bar: training was a compliance module that ticked a box, and finding an answer meant flipping through spec sheets or asking a manager again.
What it doesFor independent restaurants · built and run solo · live since June 2026






Staff ask in plain words, in the app or on WhatsApp. Every answer lists the documents it came from, so a manager can check it.
Short courses built from the restaurant's own documents, not a generic module. Each one finished is recorded, with the date it's due again.




Documents in; cited answers and training out.
Next.js · Supabase pgvector · Claude · Inngest · StripeAsk, read, sign off and train from a phone, or ask on WhatsApp. 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, and most of my skills.
e.g. 19 findings, 30 Sept reviewStore submissions with a written record of what went out.
e.g. Run 1.0, 2 Oct 2026Lays every screen of an app on one board, each with what it's for.
Sketches design options as films and stills, so the choice is made by watching.
Every big call written down: what I chose, the obvious alternative, what it costs, and what would change my mind.
How the AI works for me is written down as skills: procedures with the checks built in. Anyone can install them.
npx skills add MattKay02/skills

Screenshots every state of a feature, in order, ready to flip through.
Reviews a page on seven axes and returns a ranked punch list.
Checks a Flutter change on the Android emulator by reading the screen back.


Measures a production build on mobile and says what to fix first.


Finds failures nobody is told about, ranked by who they hurt.
Starts a CI build from the terminal and reports back when it lands.
Product engineer. I design and build polished apps, end to end.
Everything I've built, laid out the way I work on it.
Scroll for the guided tour, or click any frame to jump straight to it.
Restaurants have their rules written down. Staff don't read them.
frunt turns a restaurant's own documents into staff training and instant answers. A web app for managers; a phone app and WhatsApp for staff.
Managers bring the documents they already have.
frunt reads them, files them and turns them into courses, and a manager checks each one before staff see it. Use the tabs under the laptop to look through the screens.
Every answer shows where it came from.
Staff ask in plain words. frunt answers only from that restaurant's documents and cites each source, so a manager can check it.
Staff get answers and training on their phone.
Two screens from the staff app, on the App Store and Google Play. Staff can also ask on WhatsApp, with no app to install.
More than an app.
frunt is six parts I designed, built and run: two apps, a website, an admin console, an Instagram studio and an outreach engine.
Liftio. My first App Store app.
A gym tracker in React Native: 330+ exercises, progress charts, personal bests and cloud backup.
Then I rebuilt it as part of something bigger.
Lift is Liftio rewritten in Flutter, one app in a suite with Run. I kept the old App Store listing instead of starting fresh: its reviews and history were worth more than a tidy app ID.
Two apps that know about each other.
Log a run in Run and Lift sees it, so the coach plans around your whole week.
A suite, not two apps.
Two apps on one account and one backend, an AI coach, a website, a social pipeline and the release tooling around them.
Smaller builds, each made to learn something.
Client sites, experiments and practice projects. Hover a card to see it in colour.
I use AI to move fast. These are the checks that keep it honest.
Plan, decide, build, check, ship. Each step leaves something behind that you can look at, and under each one are the skills I built for it, loaded live from GitHub.
Install my skills: npx skills add MattKay02/skills (MattKay02/skills)
Most of my skills are checks.
Each one is tested: it has to load when it's asked for and stay out when it isn't. The pictures are real output, not mockups. Pick one to look closer.
I build things to understand them.
I run MGKCodes, the studio behind frunt and MGKFitness. Away from the desk: gym, golf and gaming.
Hiring? Let's talk.
CV (PDF) · GitHub · LinkedIn · X · MGKCodes · mattykay2002@gmail.com