Menu Scout
Researches menu gaps and proposes new dishes.
It cannot publish. Candidates land hidden and tagged until a person promotes them.
- Menu rules live in the MCP, not the prompt.
- Slack is the review surface.
My stack & tools
I connect the tools, then build the things that operate them.
Code is the source of truth now. The tools that stay are the ones I can connect, script, and operate from code. Past a point, using the tools stopped being the interesting part. Now I build on top of them: agents, skills, MCP servers, and shared libraries.
Highest leverage
Agents I've shipped
The useful part is not that a model answers. It is what starts it, what it can touch, and where a person still makes the call.
Valet Concierge
An iMessage client for the Valet backend.
The prompt is not a security boundary. Product reads and writes run as the user.
- Vendor code stays behind a transport wall.
- Unknown senders never reach the model.
Slack agents
Internal agents for sales, content, and job-search loops.
They handle repeatable legwork. A person still decides what gets sent or pursued.
- Each lane keeps its own context.
- Clear review moments matter more than autonomy.
Model work
Working with models
The interesting problems are permissions, validation, routing, and review.
- Give the model a narrow job.
- Check the answer before the product uses it.
- Keep product rules in tools, not prompts.
Built for the stack
Things I built around the tools
These are the reusable parts: skill kits, libraries, MCP servers, and public repos that turn repeated work into systems.
The Mobile Kit
Six Claude Code skills for React Native and Expo apps.
The fix is not a style guide. It is an enforcement system.
- Stops token drift, one-off spacing, and missing states.
- Includes a token linter that can fail the build.
The /mk-* Marketing Stack
Eight skills and a router for shipping marketing sites.
Each skill owns one decision and passes one named artifact downstream.
- Strategy survives the handoff to code.
- Downstream skills do not re-decide upstream calls.
Interest graph
A TypeScript library for turning taste signals into a profile.
Product logic became a reusable primitive instead of copied app code.
- Runs in React Native, Next, scripts, or edge functions.
- Public link stays coming soon until verified.
Menu Builder MCP
An MCP server for creating dishes under menu rules.
It is the interface agents, Claude Code, and scripts call.
- Dish creation is server-enforced.
- No caller gets a shortcut around nutrition rules.
Supporting evidence
The tools
The tool list matters less than the interfaces around it. These are the ones that keep earning a place.
Build & code
Preview deployments are part of the review loop.
Types catch what a confident diff can hide.
Design
Knowledge & ops
How I work
Moves I run
The skills I write are the ones that fix a mistake I watched a model make more than twice.
Mine
/fable-briefFable briefOne brief: inputs, architecture, build order, acceptance checks, and verification.
/brand-analystBrand analystFiles decisions, not adjectives, into a searchable library.
/mobile-auditMobile auditCatches raw tokens, missing states, odd spacing, and broken patterns.
/direction-proofDirection proof setKeeps visual direction tied to receipts instead of moodboard language.
Adopted
/code-reviewMulti-agent code reviewCatches what one pass misses.
- Marketing skills
Keeps product and distribution in the same loop.
- Compound engineering
The operating layer for turning vague work into shipped work.
What shaped the thinking
Reading
A short shelf of things that changed how I design, ship, or reason about systems.
- LinkDive Club
Sharp design conversations with a guest list worth studying.
- LinkFonts In Use
Where I go to study type in the wild, especially older references.