Technology in the Galley: Claude Code Is Your Operating System

The Problem with Chef Apps

Paprika. Mela. Notion templates. Recipe managers built by developers who've never worked a service. They all share the same flaw: they force your workflow into someone else's structure.

You don't need an app that stores recipes in its format. You need a system that generates menus the way you think, tracks guests the way you work, and produces provision lists that match how you actually shop. You need tools built by you, for you.

That's what Claude Code does.

What Is Claude Code

Claude Code is Anthropic's command-line tool. You talk to it in plain English. It builds things. Not mockups — real, working tools that live on your laptop, work offline, and do exactly what you tell them to.

No coding experience needed. You describe what you want. Claude Code writes the code, creates the files, and tests everything. You review, adjust, iterate. Think of it as a developer who works for you, understands food, and never sleeps.

Case Study: The Menu Agent

Here's a real system built entirely with Claude Code, running on a working superyacht right now.

The Problem

Every charter: new guests, new restrictions, new preferences. You're writing menus by hand, formatting them in Word, printing PDFs that look amateur. Repeat guests get served the same dishes because you can't remember what you made six months ago. The preference sheet is a mess of notes in three different apps.

The Solution: A Complete Menu System

Built with Claude Code over a few sessions. No developer hired. No subscription. Here's what it does:

Cultural Touchstone Naming

The system enforces a rule: no generic cuisine names. Ever. Every menu gets a "Cultural Touchstone" — a name that triggers a place, a memory, a vibe.

Generic (Rejected)	Cultural Touchstone (Used)
Italian Dinner	Notte a Napoli
Mediterranean Lunch	Mediterranean White Night
Spanish Night	San Sebastian Pintxos Bar
Fried Chicken	Better-Than-KFC Night
Nordic Dinner	Noma Forest Kitchen

The system generates these automatically based on your ingredients and cuisine direction. You give it "sashimi-grade tuna, yuzu, shiso" and it comes back with "Tokyo Night Market" — not "Japanese Dinner."

What the Output Looks Like

This is what guests see. Clean, ingredient-first, no clutter. Two real examples from service:

Every protein sourced. Not "branzino" — "Wild sea bass." Not "chicken" — "Free-range chicken." The system enforces this. Guests see where their food comes from. Transparency built into the menu card.

The Nobu menu got the feedback: "Love Nobu lunch" — logged by the system, flagged as a favourite for that guest's next charter. That's the loop: generate, serve, capture, improve.

Production-Ready Output

The system generates LaTeX files that compile to print-ready PDFs. Each cuisine gets its own visual theme:

• Italian — Palatino font, terracotta and gold
• Greek/Mediterranean — Optima font, azure and white
• Asian — Avenir Bold, obsidian and red
• French — Didot font, noir and rouge
• Kids — playful typography, rainbow colors, emojis

File naming is automatic: 2026-01-26_Guests-Dinner_Notte-a-Napoli.pdf. Every menu archived, searchable, never lost.

The Guest Archive Agent

Built with Claude Code. Solves the repeat-guest problem permanently.

At the end of every charter, you run one command: close-trip. The system:

1. Archives every menu served during the trip
2. Updates guest preference profiles with what they loved, what they left
3. Builds an aggregated favorites index across all trips
4. Flags dishes to avoid for returning guests

Next time repeat guests book? Pull their profile. The system knows she loved the Santorini Cliffside Dinner, didn't touch the octopus, asked for seconds on the lamb. It generates a new menu that respects history without repeating it.

The Menu Prompt: How It Actually Works

The Menu Agent isn't magic. It's a carefully written set of instructions — a prompt — that tells Claude exactly how to think about menus. Here's what's inside it, and why every rule exists.

Eight Service Formats

The agent recognises eight distinct formats, each with different tone, structure, and composition:

• Guests Breakfast — a la carte suggestions with health benefits
• Guests Lunch — family style by default: proteins, vegetables, starch, salad
• Guests Dinner (Family Style) — generous sharing, elevated
• Guests Dinner (Plated) — 1 starter, 1 main, 1 dessert per person
• Guests Dinner (Tasting) — canapes through mignardises, 5-8 courses
• Guest Theme Night — specific cuisine or ingredient focus
• Crew Lunch & Dinner — efficient, satisfying, distinct from guests
• Kids Menu — adult-inspired but playful

Say "dinner" and the system defaults to family style. Say "tasting menu" and it switches to the classic multi-course progression: canapes, amuse-bouche, starter, fish, meat, pre-dessert, dessert, mignardises. No ambiguity. No guessing.

The Sacred Menu Card

One rule governs everything: nothing operational touches the printed card. No dates, no "crew" or "guests" labels, no section headers like "Proteins" or "Vegetables." The card shows only the Cultural Touchstone title, dishes flowing with dividers, dietary footnotes if needed, and sourcing footer.

Metadata lives in the filename: 2026-01-26_Guests-Lunch_Dolce-Vita.tex. The menu reads like a poem, not a grocery list.

Guest Preference Integration

Before composing any menu, the agent reads the active guest preference files. Hard restrictions — allergies, intolerances, strong dislikes — are absolute. If a guest can't do onions, no onions appear anywhere, in any form, in any dish.

When a dish conflicts with a specific guest's dietary requirement, the agent adds a subtle footnote: a tiny superscript gf or v on the dish, with "Gluten-free alternative available" at the bottom. Light enough that guests eating normally don't notice. Clear enough that the guest with the requirement knows they're covered.

The Confirm-Before-Build Workflow

The system never goes straight to PDF. Always this sequence:

1. Read active guest preference sheet
2. Present menu in plain text — Cultural Touchstone title, all dishes, dietary footnotes
3. Wait for chef to validate
4. Ask: "Wine pairing card?"
5. Once confirmed, automatically generate .tex, compile to PDF, open it

You validate the creative decisions. The machine handles the production.

Ten Cuisine-Specific Design Themes

Each theme captures the soul of its cuisine — not just colours, but typography, spacing, ornaments, and rhythm:

Theme	Font	Character
French	Didot	Diamond ornaments, Parisian restraint
Japanese	Optima	Extreme negative space, zen minimalism
Italian	Palatino	Terracotta warmth, generous spirit
Nordic	Avenir Next	Sans-serif rawness, ingredient poetry
Mexican	Hoefler Text	Gold and terracotta, earth and fire
Levantine	Palatino	Geometric arabesque ornaments, warm ochre
Spanish	Didot	Bold lines, deep burgundy, Basque confidence
Greek	Optima	Azure accents, Cycladic light
Asian Fusion	Avenir	Obsidian sophistication, asymmetric modern
Modern	Avenir	Ultra-clean, no ornament, democratic luxury

The French theme uses Didot typography with diamond ornaments because that's what Le Bernardin's menu card evokes. The Japanese theme uses extreme negative space because in kaiseki, the emptiness is the design. Every theme was designed to trigger a feeling, not just apply a colour.

CloseTrip: Finishing a Charter Right

The most valuable data in your career is what happened at the table. Who loved what. Who left what. What worked, what didn't. Most chefs lose this data forever — it lives in their head until it doesn't.

The CloseTrip agent runs at the end of every trip. One command. Seven steps. Here's what it does:

Every trip produces four outputs: a trip summary, a change log, updated guest preference files, and archived menu files. Same format every time. No improvisation in documentation.

The principle behind it: guest preferences are living documents. Favourites, dislikes, and corrections are updated after every trip — not left as mental notes that fade. When the same family books again in eight months, everything is there. What they loved in St. Barths. What didn't work in Sardinia. The fact that one guest switched from oat milk to almond in March.

What a Real CloseTrip Looks Like

At the end of a charter, you say something like:

The agent creates the trip summary, updates every preference file, archives all menus with correct filenames, and produces a change log. Five minutes of your time. A permanent record that makes every future charter better.

What Else Claude Code Builds

Once you understand the principle — describe what you need, Claude Code builds it — the possibilities open up:

Every tool lives on your laptop. No subscriptions. No cloud dependencies. No app that gets acquired, pivots, and kills the feature you relied on.

AI as Brainstorming Partner

Beyond building tools, Claude is the sous chef that never sleeps. Real use cases:

The Blank Page Problem

Preference sheet lands at midnight: "Mediterranean-inspired, pescatarian, one guest celiac, loves wine pairing." You're staring at nothing.

Three options in 30 seconds. You pick elements from each, combine, make them yours. The AI solves the blank page. You make every creative decision.

Flavor Compound Matching

The AI draws from flavor databases and suggests saffron (shares safranal with fennel, limonene with blood orange), or black olive (oleic acid bridge, Mediterranean context). Connections you wouldn't make at 1am. You apply judgment. It expands possibilities.

Dietary Cross-Referencing

"Keto, allergic to tree nuts, doesn't like cilantro, loves Asian food." Instead of mentally filtering for 20 minutes, ask Claude to cross-reference restrictions against your planned menu and flag conflicts. It catches what you miss when you're exhausted.

The Only Other Tech Worth Your Space

Three pieces of hardware. Everything else is noise.

1. Bluetooth thermometer (ThermoWorks Signals) — Monitor proteins from the bridge deck. Alerts on your phone. Never overcook a $200 wagyu because the captain called you to the bridge.
2. Vacuum sealer + sous vide — Prep ahead, cook precisely, hold safely. The most important tech in any yacht galley.
3. Waterproof tablet — Mounted in galley. Recipe reference, provision lists, timers, preference sheets. Replace paper chaos.

What AI Can't Do

• Taste. No algorithm knows your salt level is right.
• Read the room. The owner's mood, the guest's energy, the timing of the next course. Human work.
• Handle chaos. Sea state changes, guest count doubles, freezer dies. Experience solves that.
• Source quality. No AI picks a better fish than a chef who knows what to look for.
• Replace relationships. Your fishmonger at Haulover knows your standards. No app replaces that.

The Workflow

Phase	Claude Code / AI	You
Preference sheet arrives	Parser extracts restrictions, flags conflicts	Read between the lines
Menu planning	Menu Agent generates themed options with pairings	Choose, refine, make it yours
Menu production	LaTeX compiles print-ready PDF menu cards	Review, approve, print
Provisioning	Calculator generates quantities & cost breakdown	Select quality at market
Cooking	Bluetooth thermometer monitors	Adjust by feel, taste, instinct
Service	Nothing. Put the phone away.	Everything. This is your moment.
Post-charter	Close-trip agent archives menus, updates guest profiles	Learn, adapt, improve

The Hard Truth

You're paying $5/month for Paprika to store recipes in a format you can't export. You're paying $10/month for Notion to build databases that don't talk to your menu planning. You're doing admin work that a machine should handle while your prep suffers.

Claude Code replaces all of it. Not with someone else's vision of what a chef needs — with yours. Your system, your rules, your workflow. Built in plain English. Running on your laptop. No internet required once it's built.

The best chefs in the world use every advantage available. The galley isn't a monastery. Build your tools. Save your brain for the craft.