Internal Tool -- Built by a PM, Used by the Studio
Every deck,
one standard.

NetBramha produces proposals, audit reports, and kick-off decks constantly. Every one of them used to be assembled by hand -- no shared rules, no consistent output. I built the system that generates them instead.

Role Programme Manager
Context NetBramha Studios
Stack Apps Script + Cloudflare + Claude
Status Live -- in use
Output -- 8 Slide Types

Every slide is generated programmatically -- positions, fonts, and colours from a single token object. These are four of the eight types the sidebar can produce.

Client Name
Mobile Experience Design Proposal
June 2026Proposal v1.0
Cover
Project Scope
In Scope
Discovery
Stakeholder interviews
User testing
Design
Wireframes + prototypes
Visual design system
Bullet List
Design Goals
01.
Reduce drop-off at onboarding
02.
Map the journey across all states
03.
Ship a system the team can own
Numbered List
Project
Governance
Section Divider
The Problem

Manual decks.
No shared standard.

Before
Every proposal built slide by slide in Google Slides. Brand rules lived in people's heads. Decks looked different across PMs. New slide types meant starting from scratch every time.
After
Fill a form. Hit a button. The slide appears -- correct font, correct spacing, correct colour, every time. The standard is in the code, not in someone's memory.
What I Built

A design system,
expressed as code.

01
Design Token System
The foundation everything else builds on
15 named colours, 2 fonts, a full spacing scale -- all in one token object. Positions and sizes derive from it. Change the token, every future slide updates.
02
8 Slide Types
Cover, Bullet List, Table, Numbered List, Section Divider, Scope of Work, Boxed List, Statement
Each type has strict layout rules -- title block rhythm, spacing hierarchy, font and colour treatment. Every element drawn programmatically, not placed by hand.
03
Google Slides Sidebar
3 modes: Build, Reformat, AI Rewrite
Build generates a new slide from a form. Reformat reads an existing slide, infers its type with Claude, and rebuilds it to standard. AI Rewrite rewrites content in NB voice before inserting.
04
Cloudflare Worker + AI Layer
Browser fetch -- no Apps Script URL restrictions
AI Rewrite calls a Cloudflare Worker directly from the browser. The worker sends content to Claude with a full NB voice brief and returns structured JSON. The sidebar inserts it as a formatted slide.
05
SKILL.md -- Living Design Standard
v1.9 -- every spacing rule, font decision, and slide type documented
Fully documented so the next person can build on it without asking me. Covers both Google Slides and PptxGenJS environments -- the same standard, extended into the proposal generator being built next.
The real work was diagnosing. Apps Script has rendering quirks that don't appear in any documentation -- fonts silently fall back to Arial, colour requires RGB not hex, alignment calls corrupt the first character if timed wrong. The code was secondary to understanding the environment.
By the Numbers
8
Slide types
3
Sidebar modes
v1.9
Design standard
0
Manual formatting
Architecture

One sidebar. Three layers.

◆
Google Apps Script
Sidebar HTML + Code.gs. Draws every element via the Slides API -- shapes, lines, text boxes -- all from token formulas. No manual placement.
◈
Cloudflare Worker
Proxies Anthropic API calls from the browser sidebar. API keys never exposed. The AI endpoint is open CORS, protected by a shared key.
◄
Claude Sonnet 4.6
Two uses: Reformat infers slide type from extracted text. AI Rewrite restructures content in NB voice and returns structured JSON.
Why It Matters

Not a template library.
A system.

Templates still require a human to apply them correctly. This generates the slide -- spacing calculated dynamically, fonts enforced by code, colours from a named token that can be updated once and propagated everywhere.

It also doubles as the design foundation for the proposal generator tool being built next. The SKILL.md covers both environments. Same token system, same slide types, same rules -- extended, not duplicated.

And it shows what a PM-built internal tool looks like when the PM understands systems thinking: one source of truth, documented, versioned, and extensible by anyone who comes after.

One standard.
Every deck.
No exceptions.
Built at NetBramha Studios. Part of a suite of 10+ internal tools built in 2026.
NB Slide Builder · Built by Sarath MS · Programme Manager