I built OpenGamma with Claude Code. It's a web app for creating editable PowerPoint decks, with sensitive names and values replaced by placeholders before the AI works on them and restored at export. One awkward problem wasn't getting Claude to write a slide. It was getting the slide to survive putting the real information back. [CLIENT_1] is short. "Northwind Logistics Holdings" isn't. A slide can look fine while it's being designed around the token, then break when the full name returns. The AI has made room for the thing it can see, not the thing the reader will get. I had to size text for the real value rather than the placeholder. Otherwise, hiding the information just moved the problem to export. One part of the Claude workflow was making it choose a visual system for the deck before writing the slides: the layout rhythm, chart style and where the emphasis should go. Otherwise it kept falling back to a title and three bullets. But a better-looking layout still had to survive the real text replacing the tokens. The design constraint: don't hide a value and accidentally hide everything the next step needs to work. A layout doesn't need to know the client's name, but it does need enough room for it. The same goes for a table cell or a chart label. That leaves two separate checks: did the sensitive value stay out of what the model saw, and does the finished deck still work once it's restored? Passing the first doesn't tell you the second passed. Masking alone also doesn't make a document safe to share. If you want to try the workflow, it's at https://opengamma.app/ . New accounts get 30 days of Core free without a card. I built it, and paid plans are available after the trial.   submitted by   /u/shoumikgoswami [link]   [comments]