A practical guide for event ops teams on how to use Claude Design Systems for on-brand event assets in minutes
Every ops person knows the feeling. Doors open in an hour and you need a directional sign, a “session moved” slide and three reprinted badges. The design team is offline, in a different time zone, or buried under the sponsor deck. The asset is small, the brand rules matter, and you need it NOW.
This is exactly the gap a lightweight design system inside Claude Design fills. Set it up once, and anyone on the ops team can generate on-brand signage, badges, social graphics and holding slides in minutes, without touching Figma and without waiting on anyone.
Here is how we do it for Event Tech Live, with the prompts you can copy.
What we mean by a “design system”
Forget the heavyweight definition for a second. You are not building a 200-page brand portal. You are writing one reusable brief that holds your brand, so every asset comes out consistent without you re-explaining the rules each time.
You give Claude Design your colours, fonts, logo rules and tone once. After that, you just ask for the thing you need (“an A1 directional sign to registration”) and it inherits the system automatically. Same brand, every time, whoever on the team is asking.
The output comes back as a self-contained artifact you can preview, tweak, screenshot, or export to PDF or PNG.
Set it up once
The trick is the foundation prompt. This is the part that holds your brand. The best home for it is a Claude Project, so the whole ops team shares the same system rather than each person keeping their own version. Paste it into the project’s custom instructions and you are done. If you are working solo in a single chat, just paste it at the top.
Here is the foundation prompt we use. Swap the example tokens for your own.
| You are the in-house design assistant for [EVENT NAME]. Every asset you produce must follow this design system exactly. When I ask for an asset, output it as a self-contained artifact,sized correctly for its use, using only these tokens. Primary colour: #1A1A2E Secondary colour: #E94560 Accent: #0F3460 Background: #FFFFFF Text: #1A1A2E Heading font: Space Grotesk (fallback: Arial, sans-serif) Body font: Inter (fallback: Helvetica, sans-serif) Logo: (This should be added to the design system as an asset) Keep clear space equal to the logo height on all sides. RULES – Never invent colours outside the palette. – Maintain WCAG AA contrast as a minimum. – Generous whitespace. No clutter. Big, legible type. – Tone: confident, plain English, no jargon. OUTPUT – Always state the dimensions and where the asset is meant to be used. – For signage, default to print proportions and give me the size in mm plus a note on bleed. – If a request is ambiguous, make a sensible call and tell me the assumption you made. Confirm you have got it, then wait for my first asset request. |
That is the whole system. Everything below is just asking for things.
Then just ask
Once the foundation is in, the day-to-day is fast. A few examples we run constantly, with the exact wording.
Directional signage – example file
| Using the design system, make an A1 portrait directional sign.Headline: “Registration”. Below it, a large right-pointing arrow.Footer: space for the event logo. Readable from 10 metres. |
Session or room sign – example file
| A2 landscape sign for outside a room. Room name: “Innovation Theatre”.Include a clear slot for the current session title and time that Ican edit. Leave space bottom-right for a sponsor logo. |
Name badges, by attendee type – example file
| Design a name badge, 90mm x 120mm portrait, for a lanyard insert.Large first name, smaller surname and company beneath. A colour baracross the top that changes by attendee type. Give me all fivevariants: Visitor, Exhibitor, Speaker, Press, Crew. |
Wayfinding “you are here” – example file
| An A0 portrait wayfinding board. Title “You are here”. Leave a largecentral area for me to drop a floor plan image. Add a clean legenddown the right side with five numbered zones. |
Speaker announcement for social – example file
| A 1080×1080 speaker announcement. Placeholder circle for a headshottop-centre. Below: speaker name, job title, company, session title,and the date. On-brand, bold, scroll-stopping. |
Holding and error slides – example file
| A 16:9 holding slide reading “We’ll be back shortly”, with the eventlogo and a subtle branded background. Then a second version reading”This session has moved. Please check the app for the new room.” |
Each comes back ready to preview. If it is not quite right, you say “make the arrow bigger” or “swap to the accent colour” and iterate in seconds.
Where this shines, and where it does not
Be honest with yourself about fit, because that is what keeps the brand safe.
It is brilliant for fast, internal and onsite assets: holding slides, screen graphics, A4 prints, social posts, simple directional signage, reprinted badges. Anything where speed matters more than a perfect press finish.
For large-format print, treat the artifact as a strong first draft rather than the final file. Big signage needs proper resolution, bleed and often CMYK, so take the design into your print workflow to finalise. The same goes for anything that sets the tone for the whole show. Your hero stage graphics still deserve a designer.
Two habits worth keeping:
- Run a quick brand sign-off the first few times, until the team trusts the system.
- Check contrast and legibility on real signage at real distance, not just on screen.
Try it
Build the foundation prompt with your own colours and fonts, drop it into a shared project, and pick one nagging asset you always end up doing at the last minute. Generate it. You will know within five minutes whether this earns a permanent place in your ops kit.
We use this every show. Come and tell us how you get on at Event Tech Live.
