Presentation Studio.

Interview in; projector-ready deck with live QR polls out. 'No human writes code in this repo' - and kept.

SEE HOW IT WAS DIRECTED →ALL SYSTEMS

INTERNAL SYSTEM · REAL INTERFACE, PROTECTED DATA · WALKTHROUGH AVAILABLE ON REQUEST

the lightcastle deck · presented live●

The real LightCastle deck title slide, rendered by the engine in the Signal design system

01 · THE PROBLEMWHAT WAS BROKEN

Every talk, a hand-built app. Deck two nearly destroyed deck one. Decks are software - they needed an engine.

02 · THE SYSTEMWHAT SHIPPED · WHO USES IT

The Signal design system - deep-navy editorial title slide

The Neo-Grid-Bold design system - black and acid-green brutalist title

The Retro-Windows design system - a Win-95 PRESENTATION.EXE window

The Broadside design system - fire-orange poster title

The Pin-and-Paper design system - field-notes with pinned cards

ONE DECK SPEC · FIVE DESIGN WORLDS · REAL RENDERS

Built as versioned code with decision records - not slideware.

A talk is now an hour of conversation plus a build.

7decks delivered

~600people reached

34design systems built

SOURCE: His delivery record · Shikho internal, LightCastle, NSU

03 · UNDER THE HOODWHAT ACTUALLY HAPPENS

Pick a moment. Watch the calls the system makes that no one sees.

CODETHE MODELA CHECKTHE CLEVER BIT00/07

THE THINKING BEHIND EACH STEP

01We take it raw on purpose. Knowing the talk is the author's job; structuring it into slides is the machine's - so the entry is a messy voice note or a paragraph.

02Open questions get abandoned, so every question ships with guesses mined from the dump itself. Answering is mostly tapping, not typing - the form fills itself before the author gives up.

03This is where scattered answers become an argument, not a list. A talk that just replays your dump goes nowhere, so the deck earns a spine before any slide is styled.

04"The Graveyard" tells the room nothing; "Four delivery startups raised big and still died" makes the point before you speak. A title that carries no argument does not ship.

05Two text-only slides in a row and the room glazes over. So cadence is enforced, not hoped for - a real exhibit every few slides, a poll where the room should participate.

06Offer 34 systems and the author freezes; pick one for them and you have taken their taste. Three - each with a reason - is a choice a person can make.

07This interview asks poll-shaped questions because it knows the room will vote live off one QR. Most tools plan blind to delivery - here planning and delivery are one system.THE CLEVER BIT

EVERY STEP MINED FROM THE REAL BUILD · NOTHING INVENTED

04 · WHY NOT ONE PROMPTWHAT A ONE-SHOT WOULD HAVE GOT WRONG

One prompt gets you a deck. It does not get you a deck engine that survives contact with a live audience.

The first architecture was wrong - real use proved it. A React template engine grew ten themes, then hit its ceiling: every theme forced into the same 19 fixed components.
The polling layer is scar tissue. A network tunnel once silently ate the fancy solution mid-talk.
Quality is measured, not vibed. Tokens were proven by pixel-diffing regenerated decks against the originals - a geometry harness hunted overlaps at three screen sizes.
Zero marginal cost, deliberately. A five-dollar bill for two runs moved the whole pipeline onto the subscription.

05 · THE DIRECTIONWHERE THE HUMAN WAS

THE FORK · WHAT THE AI PITCHED VS WHAT I SENT

Late June. React, 19 fixed templates, a tenth theme shipped. The decks all look... related. The model's fix: deepen the themes, keep the templates.

THE MODEL'S PITCH · AND ITS POST-MORTEM, THE NEXT DAY

The architecture I'm going to use (my recommendation): a **theme becomes a "style kit"** [...] The theme can repaint and lightly reshape — **it can't change what the slide structurally *is*.** That ceiling is the architecture, not a tuning problem. The StyleKit was a valiant retrofit onto a fixed-template engine, and it can't reach the depth because **the templates dictate the grammar, the design system doesn't.**

WHAT I SENT · TYPOS KEPT

It seems we might have built our current system in such a way that we are trying to retrofit and that isn't working - so if required, you can remove the entire current architecture and rethink the architecture so it can handle this. [...] Basically, I am giving you the freedom to not have any legacy code.

But I want a great product whos fundamental job is to create stunning wow slides - with animations, fades, reveals, all of that - something a powerpoint presentation would take months to do.

Thirteen hours later, React was deleted - replaced by the 34-system library above, each deck authored fresh in its world. Only the polling core survived. Five worlds, one deck spec.

SESSION TRANSCRIPT · 2026-06-27 · BOTH SIDES QUOTED EXACTLY · [...] MARKS OMITTED SPEECH

The model optimizes inside the architecture it has. Direction is noticing the architecture is the problem - and granting permission to demolish.

46 slide patterns34+ append-only ADRsadversarial per-slide judgingzero marginal costHOW IT WAS RUN, NOT HOW IT WORKS

NEXT SYSTEM Beton Kemon →

▸