惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

GbyAI
GbyAI
WordPress大学
WordPress大学
D
DataBreaches.Net
腾讯CDC
小众软件
小众软件
B
Blog RSS Feed
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
T
The Blog of Author Tim Ferriss
MongoDB | Blog
MongoDB | Blog
U
Unit 42
Y
Y Combinator Blog
V
V2EX
I
InfoQ
D
Docker
量子位
N
Netflix TechBlog - Medium
Recent Announcements
Recent Announcements
A
About on SuperTechFans
博客园 - 叶小钗
大猫的无限游戏
大猫的无限游戏
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
B
Blog
阮一峰的网络日志
阮一峰的网络日志
MyScale Blog
MyScale Blog

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
Why we hardcoded 8 niche presets instead of letting GPT g...
汪小春 · 2026-05-16 · via DEV Community

Most AI slide tools let GPT decide everything — the layout, the typography hierarchy, the section structure. Each generation is a new design lottery. We shipped the opposite approach: 8 hardcoded niche presets that GPT can fill but not redesign.

This post is about why constraint won over creativity for our slide-generation pipeline.

The problem with letting LLM design layouts

Early prototype: pure GPT layout generation. The model decides:

  • How many sections per slide
  • Title vs subtitle hierarchy
  • Bullet vs paragraph structure
  • Color emphasis
  • Asset placement

Result: each deck looked different from the next. "Different" sounds good until users started telling us:

  • "Why does the second slide have a 5-point list and the third has a 3-bullet hierarchy?"
  • "The font on slide 7 is huge, but slide 8 is tiny."
  • "Looks AI-generated."

The third complaint was the killer. When variance is visible, users default to "this AI doesn't know what it's doing."

The fix: pre-pick layouts, let LLM only fill content

We hardcoded 8 vertical-specific presets:

  • Career: hierarchy of pain → frame → action sections
  • Finance: chart-heavy with bullet clarifications
  • Reading: book cover + chapter quotes + 3-takeaway template
  • Beauty: image-led with overlay captions
  • Health: stats-forward with citation footers
  • Culture: timeline-style with accent imagery
  • Travel: map + photo grid + itinerary breakdown
  • Knowledge: 3-column comparison + "key insight" callout

Each preset is a deterministic layout system. GPT picks the right one based on the input topic, then fills slot content. The structural variance disappears.

Why niche-first, not generic-first

We considered the obvious alternative: 5 universal templates ("clean", "minimal", "playful"). It failed in user testing because:

  • "Clean" doesn't tell you what content goes where
  • The same "minimal" template applied to a finance deck and a travel deck both look generic

Niche-specific templates encode domain assumptions:

  • A finance deck's first slide should be a chart
  • A reading deck's first slide should be a book cover
  • A travel deck's last slide should be a map

These assumptions ride for free with the niche selection — no need to teach the LLM what each genre expects.

What we lose

We lose:

  • Flexibility for niches we didn't anticipate (business pitch, scientific paper, etc.)
  • The ability to experiment with novel layouts mid-deck

For both, our answer is "we'll add presets when there's clear demand" rather than "let the LLM figure it out". The latter is what failed in v0.

What I'd do differently

Each preset has a single "voice" — the same layout system applied throughout the deck. In hindsight, voice should vary by slide position (cover vs body vs CTA) within a preset, not just by niche. We'd ship "preset families" with intra-deck variation rather than treating each preset as a single template.

Try it

If you want to see what 8-niche-preset architecture looks like in practice, AnySlide ships the v1 of this. Free to start (60 credits at signup, daily +10 reset, no credit card).

I'd love to hear from anyone who took the opposite bet (full LLM creativity) — did it pay off?