The pattern in one sentence
Vibe-coding = AI removes the expert barrier from a domain that traditionally requires craft knowledge, by accepting whatever the user already has (a photo, a voice memo, a screenshot) and returning whatever the domain needs (an STL, an HTML site, a print-ready 3MF, a tax return).
Capture
iPhone photo, voice memo, calendar event, screenshot — whatever the user already has
Bias
Local LLM + agent stack with domain-specific knowledge baked in
Output
Production-ready artifact in the domain — STL, HTML, code, brief, contract, scene file
Delivery
Returned in seconds, ready to ship, zero token cost
🏗️ The stack (same for every domain)
┌─────────────────────────────────────────────────┐ │ USER CAPTURE LAYER — iPhone / voice / chat │ │ • photo of object • voice memo of need │ │ • screenshot • calendar event │ └────────────────────────┬────────────────────────┘ ▼ ┌─────────────────────────────────────────────────┐ │ ORCHESTRATION LAYER — Aria (Claude on M4) │ │ parse intent → route to right backend │ │ apply lane context + user preferences │ └────────────────────────┬────────────────────────┘ ▼ ┌─────────────────────────────────────────────────┐ │ GENERATION LAYER — Hermes on M3 (qwen3.6 / │ │ llama4:scout) OR Vegas (Claude Code on M4) │ │ • domain-specific skill │ │ • multi-model challenge (plan → critique) │ └────────────────────────┬────────────────────────┘ ▼ ┌─────────────────────────────────────────────────┐ │ OUTPUT LAYER — domain-native artifact │ │ STL · 3MF · Astro site · YAML scene · brief MD │ │ pushed to NAS / CC / Pages / printer / app │ └─────────────────────────────────────────────────┘
The genius of this architecture is that the capture and orchestration layers stay constant across every domain. Only the generation layer needs domain-specific knowledge. Adding a new domain = adding one skill, not rebuilding the stack.
🎯 Eight examples — from shipped to concept
🌐 Websites
Vibe-code your website
Capture
Voice memo describing the business + screenshot of inspiration site
Backend
Vegas (Claude Code on M4) — Astro + Tailwind + Aspire design system
Output
Deployable Astro site, pushed to Cloudflare Pages
Proof: 10+ client sites built this way (b-clean-carpet, modern-maid, delaware-lanes, etc.)
🖨️ 3D Printing
Vibe-code your 3D print
Capture
iPhone photo of object + 3D-printed measurement board for scale
Backend
Hermes (Ollama llama4:scout on M3) — image-to-3D + slicer config
Output
STL + Bambu Studio 3MF, printer-ready
Proof: OPS-50 — research from 2026-05-17, dog collar holder for AirTag-like chip is the first real demo
🏠 Home Automation
Vibe-code your home
Capture
Voice memo describing what you want to happen
Backend
M3 hosts Homey Pro Bridge or Home Assistant; Aria sits above as the natural-language orchestrator
Output
Working automation flow, locally executed, no cloud round-trip
Proof: See /info/home-automation-strategy (drafted 2026-05-17 alongside this page)
📞 Sales Outreach
Vibe-code your prospect list
Capture
A single contextual prompt — vertical, geography, ICP signal
Backend
Hermes lead-hunt skills (nrx-lead-hunt, voice-ai-lead-hunt) on M3
Output
Scored prospect list with verified GBP data + research, in Notion
Proof: Tex (NRX Asphalt) and the HVAC voice-AI run from 5/2 are the live proofs
📅 Meeting Prep
Vibe-code your meeting brief
Capture
Calendar event (attendees, title)
Backend
Hermes presales-brief skill, triggered 1 hr before each event
Output
One-pager with attendee research, prior context, agenda draft
Proof: Skill exists, scheduling pending
🧒 Kids
Vibe-code the college essay (or birthday card, or eulogy)
Capture
Voice memo or chat transcript reflecting on the person
Backend
Claude or local model with a "in their voice" prompt
Output
First-draft essay/note in the parent's voice, not generic AI prose
Proof: Personal — high emotional ROI, low technical lift
✈️ Travel
Vibe-code your Vegas trip
Capture
Voice memo of preferences + must-do list
Backend
Aria + Google Calendar MCP + external booking APIs
Output
Itinerary, reservations, confirmations — booked, not just researched
Proof: The Vegas May 7-15 trip prep could have been one voice memo
🧾 Taxes
Vibe-code your tax filing
Capture
Photos of W2/1099/receipts
Backend
OCR + categorize + cross-check against prior year
Output
Pre-filled return ready for human review
Proof: The Finance PDF dump (OPS-10) is the prerequisite that unlocks this
💰 The productization angle (for the personal brand)
The phrase "vibe-coding" is already in the air for websites (Cursor, Vercel v0, etc.) but no one has named the broader pattern. Topher could claim it.
Thesis to publish:
"Vibe-coding isn't a website thing. It's the shape of every consumer-AI product worth building in 2026: take the input the user already has, return the artifact the domain actually needs, run it on the hardware they already own. The websites are just the obvious first case."
Three places this lands well:
- • LinkedIn — fits the existing positioning track (the "AI for ordinary work" angle from the 4/25–4/27 voice work)
- • Personal brand site (madebyotten.com/chris) — add a "Vibe-Code Library" section linking each domain's working demo
- • Aspire Digital — the agency's narrative is "we build AI for SMBs"; vibe-coding is the *how*
🎯 Next moves (decision-ready)
1. Pick which domain to ship next as a public demo. 3D printing has overnight research running; home automation has a strategy drafted; meeting prep has the skill installed. Topher's call on which becomes the *second* shipped demo (websites is the first).
2. Write the LinkedIn post. Aria can draft it from this page once Topher signs off on the framing. 150–200 words, claims the pattern, links to a working demo.
3. Add "Vibe-Code Library" to madebyotten.com/chris. One card per domain, status badge, link to working demo. Aria + Vegas tomorrow.
4. Build the multi-model challenge layer. Topher specifically asked for this in the 3D printing voice memo (plan with Opus, challenge with Sonnet/GPT). It generalizes — every vibe-code domain benefits. Use the new kanban-orchestrator + kanban-worker Hermes skills (bundled in v0.14) to implement.