MonoMind Hi Ted, Meet Lisa

Hi Ted,
Meet Lisa


When Ted meets Lisa,
ideas come to life in HTML

Describe a deck. Answer a short visual intake. Your agent hands back one standalone HTML file — open it, present it, print it, email it. No build step. Nothing to install.

Choose your path
Line illustration of Ted and Lisa standing together inside a white frame, over a blurred poppy photograph.

@monomind ai labfig. 01 — the frame

New here?

Three ways to your first deck.

Pick what fits. Every path ends the same way: one finished HTML file, handed to you by your own agent.

The thorough way

Open the intake panel — the same one agents use. Pick a template, answer the questions, and it hands you a complete, paste-ready prompt.

  1. 01Describe it Answer the panel — nine to sixteen questions, every one with a default.
  2. 02Copy the prompt The last screen says “Prompt is ready.” One click copies everything.
  3. 03Paste it to your agent It reads the skill from GitHub, builds the deck, and hands you the file.
or keep it to one line

The quick way

Skip the panel. Copy the prompt on the right, replace the two placeholders, and let the agent ask you the rest.

Build me a deck using https://github.com/monomind-ai-lab/hi-ted-meet-lisa. Read and follow `SKILL.md`, starting with its intake panel. The deck is about [YOUR SUBJECT], for [AUDIENCE].

Works with any coding agent that can read a public URL:

Claude CodeCodexPiOpenCodeHermesGemini CLIclaude.ai…and yours
01Clone it into your skills directory

One clone, available in every project. Other agents have their own skills directory — the layout is the same.

git clone --recurse-submodules \ https://github.com/monomind-ai-lab/hi-ted-meet-lisa.git \ ~/.claude/skills/tedandlisa
02Link the two companion skills

They ride along in the clone — the links just make them commands of their own.

ln -s ~/.claude/skills/tedandlisa/skills/tedandlisa-design \ ~/.claude/skills/tedandlisa-design ln -s ~/.claude/skills/tedandlisa/skills/tedandlisa-new-template \ ~/.claude/skills/tedandlisa-new-template
03Use it, whenever
/tedandlisa a 12-slide deck on our Q3 roadmap, for the exec team
04Teach it your own look

This is the part people miss: hand it any finished HTML deck you like, and its visual system becomes a reusable template — extracted, stripped of its content, registered, thumbnailed. It's then one of your choices in the gallery, permanently.

/tedandlisa-new-template ./that-deck-i-like.html

What installing gets you

  • The intake panel, served locally. Your agent opens it in your browser and picks the answers up itself — no copying.
  • Your own templates. Hand /tedandlisa-new-template a deck you like and its look becomes a permanent choice in the gallery.
  • The design pipeline. /tedandlisa-design for twelve style presets and animated slides — still one HTML file.
  • Every agent you use. The skill is plain Markdown and HTML — Claude Code, Codex, Pi, OpenCode, Hermes all read the same files.

Prefer no terminal at all? Packaged skill zips for claude.ai (Settings → Capabilities → Skills) are coming soon.

FIRST · MINUTE 0

Send the prompt

Open the intake panel, answer it, and paste the finished prompt to your agent. Your first deck starts building immediately.

WHILE IT BUILDS

Install in parallel

The deck takes a few minutes to arrive. That's exactly how long the install takes — run the clone from Path 02 while you wait.

EVER AFTER

It's a command now

/tedandlisa from any project, the panel opens itself, and your own templates join the gallery. Ted and Lisa live here now.

Browse the templates

The two paths don't conflict — the prompt reads the skill from GitHub, the install puts the same skill on your machine. Decks made either way look identical.

Inside every file

Small file. Big machinery.

A deck from Ted and Lisa is not a static export — it carries its own navigation, its own languages, and in some shapes, a working prototype.

◐ LANGUAGE

Two languages, one file

English plus Korean or Traditional Chinese in the same deck, switched in place. Filenames, commands, and product names are protected — they never get machine-translated into nonsense.

→ NAVIGATION

It presents itself

Scroll-snap slides, arrow keys, touch swipe, and a deck menu with contents — plus optional PDF and HTML download entries, right in the deck's own chrome.

◑ THEMES

Light and dark, measured

Both themes ship in one file with a switch. A design review pass measures contrast in each — and behaviour at phone width — before the file is handed over.

▣ PROTOTYPES

Clickable website mockups

The Sitemap & IA shape doesn't just draw a site structure — it ends in a navigation prototype you can actually click through, at desktop and phone breakpoints.

✎ RESEARCH

Decks that argue

Some shapes are guided research, not slideware: information architecture proposals, system diagrams where colour means something, documents with decision records.

⧉ DIAGRAMS

Diagrams that translate

Diagram-first shapes carry inline SVG — no CDN, works offline, and the labels inside the drawings switch language along with the rest of the deck.

The medium

The beauty of one standalone HTML file.

Everything Ted and Lisa make ships the same way — a single .html file. It sounds humble. It's the whole point.

  • It opens anywhere. Double-click it, email it, drop it on any static host. Your audience installs nothing, signs into nothing.
  • It's three deliverables at once. Present it as a talk, print it as a handout, read it as a document — the same file.
  • Nothing in it can rot. No build step, no framework, no dependencies that expire. The file that works today opens the same way in ten years.
  • It's yours to change. Plain, human-readable HTML and CSS — open it in any editor, or hand it back to any agent, and change what you like.

The whole idea

Ted has the idea.
Lisa gives it a frame.

You bring the brief; the agent does the building. What comes back is one file that opens anywhere and looks like it came from one studio.