Plugin Launch · May 2026
A new Claude plugin for the Grade team — generate, edit, preview, export, and publish on-brand proposals without leaving the chat. This is what it does, how to install it, and how to use it.
On-brand by default,
not by effort.
The plugin bakes Grade's design system and voice into a handful of skills you call from chat. Less typography to chase, fewer tabs to keep open, more time on the thinking.
Each proposal is still a single self-contained HTML file — same shape as the ones the team has been building by hand. The plugin automates the manual bits: scaffolding from a brief, bulk-editing copy, exporting clean PDFs, publishing to a shareable URL. The design system is the source of truth; the skills follow it strictly.
There are two short walkthroughs in this document — one for installing the plugin, one for using it. Watch, install, generate a proposal, share the link.
Section one
A one-time setup. Takes about a minute.
You'll need Claude Desktop installed, and the grade-prop-generator.zip file. Then it's eight clicks, in order.
Make sure you uploaded the .zip file, not the unzipped folder. Restart Claude Desktop and check Customize > Personal plugins — the plugin should be listed. Still stuck? Ping Adam.
Section two
From there, plain English or a slash command — either works.
Open Claude Desktop, head to the Code tab, and point it at a folder. That folder is where Claude saves the proposal and where you drop background docs — briefs, transcripts, references, anything you'd want it to use as context.
You now have a working HTML proposal file in the folder. Next: preview it and mark up edits visually.
The fastest way to iterate is the built-in preview alongside the chat.
Claude sees the markup and the instruction together — no need to describe where the change goes.
You can jump around — re-run any step, in any order.
A proposal usually moves through these steps. They're idempotent — re-publishing updates the same URL; re-exporting overwrites the PDF in place.
.copy.md file. Edit naturally, then re-run to apply.*.pages.dev URL the team can share./prop-add-section — add a new page or block.
/prop-restyle-section — change how a section looks without rewording.
/prop-draft-copy — get fresh options for one spot.
You don't have to memorise the commands.
Plain English works just as well.
| "Make a PDF of this" | /prop-export-pdf |
| "Share this with the client" | /prop-publish |
| "Let me edit the copy" | /prop-edit-copy |
| "Rename it for v2" | /prop-rename |
| "How does this work?" | /prop-help |
Both walk you through it the first time you run them.
First run, the skill detects you have no Cloudflare credentials and walks you through getting an API token and Account ID, pasting them back in, and writing them into a .env for you.
After that, redeploys just work.
Mac users — brew install node if you don't already have it.
Needs Google Chrome (or Chromium) installed. Most Macs have it already; if not, grab it from google.com/chrome.
No other config — the skill handles the rest.
Need a reminder? Type /prop-help any time — or just ask
"how does this work?"
— and the workflow prints back into the chat.
Try it on the next one
Install it, run it on a real brief, tell me where it falls short.