Artefact design

A design.md file is a plain-text brand specification written in Markdown. Attach it to an assistant, and every visual artefact that assistant generates — an HTML page, a dashboard, a report — follows it. Colors, typography, spacing and component patterns stay consistent, without you describing your brand again in every prompt.

What a design.md gives you

Without a design.md, an assistant defaults to a generic visual style. With one attached, its generated artefacts reflect your organization’s actual brand consistently, conversation after conversation.

What to put in it

A design.md doesn’t follow a rigid schema — the assistant reads it as instructions written in natural language and structured lists. Good things to include:

• Color palette — primary, secondary, accent, background and text colors, with hex values.
• Typography — font families, sizes and weights for headings, body text and code.
• Spacing and layout — column widths, padding, border-radius values.
• Component patterns — how buttons, cards, tables and badges should look.
• Tone guidance — how copy should feel: formal, friendly, concise.
• Restrictions — things to avoid, such as stock art or garish colors.

Attaching it to an assistant

Open the assistant, go to Edit, and add your design.md file as an attachment. It’s active from the next conversation onward — see Attachments for how attachments work generally.

Which artefacts it affects

Any HTML-based or visual artefact: HTML pages, interactive demos, styled reports and dashboards, and data visualizations rendered in HTML or CSS. Plain-text output — summaries, bullet lists, code in a non-visual language — isn’t affected by design.md.

Keeping it up to date

Treat design.md like any other piece of shared knowledge: when your brand guidelines change, update the file, and every future artefact the assistant generates reflects the change automatically.