A Claude Code plugin took 20-page brand reports off my desk
Four to six reports a month, twenty pages each, and a workflow that other departments ended up using too.
In this story3 sections
Every month, four to six reports would arrive from different departments. Each was around 20 pages. I checked every page and adjusted it to match the company’s brand: fonts, sizes, colours, tables and layout.
Depending on the reports, that work could take several days. The inputs varied too. Some arrived as Word files, some as PDFs. Some had charts. Some had been generated by other tools. Their structure and formatting were different each time.
- Reports a month
- 4 to 6
- Pages in each report
- ~20
- Of manual checking
- Several days
What I built
I built an internal Claude Code plugin around that workflow. I defined the brand rules and adapted them specifically for reports. The system would read the incoming document, identify its structure and produce a branded PDF. It also produced an HTML review view showing what it had found and how the document had been processed.
Inside, it is specialised agents, reusable skills and the brand rules. I iterated on it myself and with our finance manager until we had a stable version we could use. Files went into an input folder, and the workflow could be started with a short command. The agents handled the remaining steps, several reports at a time, and placed the results in the output folder.
I used it. Other departments used it. After it was in place, I stopped receiving those recurring reports for manual design.
Where the design work was
The design work included deciding how the brand rules should be represented, how different documents should enter the workflow and how the results could be reviewed.
The review view was the answer to the last one. For each document it showed what the system had read, what it had found and what it had checked. Word or PDF, with charts or without, the system read the document and identified its structure before it produced the branded PDF.
The plugin and the reports belong to the company, so there are no screenshots here. That is also why this story is told in words.
Not the only one
I was the studio manager for product design and engineering, and this was one of several tools I built around what the people there actually needed, from report formatting to an AI sitemap tool for client websites. The ones that stuck were the ones built around a real, recurring job. In 2025 I was named Employee of the Year.
The useful outcome was straightforward: a recurring job that had kept coming back to me no longer needed my manual formatting.
