u/Ok-Run-659

I do a lot of design work with Claude Code landing pages, dashboards, the usual. Every few prompts it asks me to choose between three or four directions, and the choices come through as terminal text:

Which hero layout should I build?

1. Hero variant A
2. Hero variant B
3. Hero variant C
4. Type something.

"Hero variant B" tells me nothing. Claude knows what it means; I'm guessing. After enough wrong guesses I got annoyed enough to fix it.

What it does

You type `/visual` into the "Type something." box. A page opens in your browser with each option rendered as a real card — built using **your project's** colors, typography, and corner radii (it scans your Tailwind config). You click one. The terminal continues as if you'd picked it the boring way.

I do a lot of design work with Claude Code landing pages, dashboards, the usual. Every few prompts it asks me to choose between three or four directions, and the choices come through as terminal text:

Which hero layout should I build?

1. Hero variant A
2. Hero variant B
3. Hero variant C
4. Type something.

"Hero variant B" tells me nothing. Claude knows what it means; I'm guessing. After enough wrong guesses I got annoyed enough to fix it.

What it does

You type `/visual` into the "Type something." box. A page opens in your browser with each option rendered as a real card — built using **your project's** colors, typography, and corner radii (it scans your Tailwind config). You click one. The terminal continues as if you'd picked it the boring way.

I do a lot of design work with Claude Code landing pages, dashboards, the usual. Every few prompts it asks me to choose between three or four directions, and the choices come through as terminal text:

Which hero layout should I build?

1. Hero variant A
2. Hero variant B
3. Hero variant C
4. Type something.

"Hero variant B" tells me nothing. Claude knows what it means; I'm guessing. After enough wrong guesses I got annoyed enough to fix it.

What it does

You type `/visual` into the "Type something." box. A page opens in your browser with each option rendered as a real card — built using **your project's** colors, typography, and corner radii (it scans your Tailwind config). You click one. The terminal continues as if you'd picked it the boring way.

Bit of a technical confession. Last few months I've been building a small thing where you write a deck in Markdown, push it, and get a hosted URL — basically the inverse of Gamma's flow (Gamma generates, mine publishes).

The interesting bit (or the rabbit hole, depending on how you look at it) was the MCP integration. I wanted my own server to show up in claude.ai's connector list. To do that properly you need:

- RFC 7591 (Dynamic Client Registration) — so claude. ai can register itself without me preconfiguring credentials.

- RFC 9728 (OAuth Protected Resource Metadata) — so the MCP endpoint can advertise its own auth server via WWW-Authenticate.

- A proper /.well-known/oauth-authorization-server discovery document.

Total time: ~4 days, all on Next.js 14 App Router. The middleware allowlist for the MCP route was the subtlest bug — generic 401s eat the WWW-Authenticate header and break claude.ai's auth-server discovery.

Stack, for the curious:

- Next.js 14 App Router, server components where possible

- Tailwind v4 with u/theme inline and u/custom-variant dark (just finished a brand redesign — single Inter Tight family + JetBrains Mono captions, light/dark via next-themes)

- Postgres + Drizzle, JWT sessions

- MCP server on /api/mcp

- Vercel for hosting + Vercel Analytics/Speed Insights (shipped this morning)

The thing I'm chewing on:

1. Is anyone else building MCP servers? It still feels early — I'd love to know what auth/UX patterns are settling out.
2. For Tailwind v4 + next-themes, did you also fight disableTransitionOnChange vs FOUC? Curious how others solved the SSR flash.

Code's not public yet but happy to share snippets in the comments if anything above is useful. Not pitching — genuinely want the technical conversation.

I've been watching this AI-deck gold rush for the last year and it's been bizarre. Gamma, Tome, Decktopus, Beautiful.ai-every one ended up doing the exact same thing. You type in a prompt and an AI generates a deck for you. They're good at it. Gamma especially. That "type a sentence, get 12 slides" demo always wows everyone in the room.

But here's what I noticed, as I watched this wave roll in:

AI is fine at generating the deck. It's actually really bad at the mundane shit that comes afterwards. Publishing the deck. Sharing a URL. Knowing who actually opened the thing. Republishing it automatically if the content changes.Generating from within your existing editor and not their presentation editor.

And so I built the mundane half of the problem. Markdown in, published deck out with a live URL and a history. This also includes analytics. The big differentiator that I’m willing to bet money on: MCP servers, which let ANY agent (claude, cursor, codex, claude .ai connector) publish a deck without needing to switch context.

Thesis: in 12 months, no one will even open a "presentation app." Your agent will publish it for you and all value will go towards whoever owns the destination URL and the content of that URL.

I've been building this solo for about 4 months, 2 active users outside of myself, and have a re done branding that I'm finally proud of.

I have two questions for the sub:

1. Is "agent publishes, human only sends a link" the real future or am I living in a fantasy? If you were using Gamma last week, what felt redundant about your workflow?

2. If you were positioning this against Gamma (an incredibly well-funded company I'd be stupid to take head-on) what's the "niched down" wedge that I'd carve out? I was thinking "the deck tool that lives inside your AI tools, not adjacent to them." Is that too broad or too narrow?

I'm not linking directly to avoid self-promotion. But real founder, real product, I'll respond to all replies.

Hey r/SideProject. Mostly lurking here, finally posting.

Quick story. I started this thing because I kept needing to share decks with people but Google Slides felt heavy and Gamma felt locked-in. I love what Gamma does — the AI generation is genuinely magic — but I wanted the opposite: write Markdown, push, get a hosted deck. Boring. Predictable. Mine.

So I built a CLI. Then I added Markdown pagebreaks. Then I added an MCP server so I could publish decks straight from Claude or Cursor without leaving my editor. Then I realized the UI looked like a 2014 admin panel, and I spent the next 1 months redoing the brand:

- v1: industrial dark blueprint (looked like a SCADA dashboard)

- v2: light premium minimal (looked like every other SaaS)

- v3: editorial italic serif hero (closer, but the body type fought it)

- v4 (this week): one display family, hairline UI, a real wordmark, dual themes that don't fight each other

I think v4 is finally the one. The product underneath has been working the whole time — I just couldn't get out of the way of it.

What I'd love from this sub:

1. If a "publish-from-Markdown" deck tool walked into your stack tomorrow, what would have to be true for you to actually open it on day 2?

2. The MCP/AI-agent angle (claude.ai can publish a deck for you) — gimmick, or actual hook?

3. Honest reaction to the wordmark + light/dark surfaces if I drop a screenshot in the comments?

Not promoting in the title because of you wisely downvote that. Happy to share the link below if anyone wants to poke holes.

Thanks for reading.