Huxberry Brand guidelines

Chapter 12 of 12

Using this guideline with AI agents

Plain text PDF Source

On this page
  1. The addresses to paste
  2. Which file for which job
  3. Set-up by tool
  4. System prompt to paste
  5. Rules for agents
  6. Keeping agents current
  7. Before you accept an agent's work

This guideline is published for people and for software. Every chapter on brand.huxapps.com has a plain-text twin that an AI tool can read, so ChatGPT, Claude, Gemini, Codex, Cursor, image tools and agency tools apply the 2026 brand without anyone retyping it. This chapter says which address to give which tool, and the rules an agent must keep.

The addresses to paste

File Address Give it to an agent when
Index https://brand.huxapps.com/llms.txt It can browse and should find the right chapter itself
Everything in one file https://brand.huxapps.com/llms-full.txt It cannot browse, or you want no gaps. All chapters in order
One chapter https://brand.huxapps.com/guidelines/03-colour.md The job touches one topic. Every chapter has the same address pattern: number, hyphen, name, .md
Tokens, JSON https://brand.huxapps.com/tokens/huxberry-tokens.json It builds a design system, a Figma library, a theme, a template, a chart or a slide master
Tokens, CSS https://brand.huxapps.com/tokens/huxberry-tokens.css It writes HTML, CSS, Liquid, email or web components
Claude skill https://brand.huxapps.com/SKILL.md It is Claude or Codex, or any tool that reads skill files
Logo files https://brand.huxapps.com/logo/ It lays out anything that carries the logo. It must use these files, never draw one
The website https://brand.huxapps.com A person, or an agent with a browser

The full list of chapter addresses, with the current version number, is always in llms.txt.

Which file for which job

Job Give the agent
Write copy: product page, email, social caption, ad, WhatsApp reply Chapter 01 (voice) and chapter 09 (digital marketing). When in doubt, llms-full.txt
Design a page, a template, a slide deck, a brochure The tokens JSON plus chapters 03, 04, 05 and 07. For print, add chapter 08
Write web code, a Shopify section, an email template The tokens CSS plus chapters 07 and 10
Make or edit a product image or video Chapter 11 (it contains the prompt blocks) and chapter 06
Prepare a file for the printer Chapter 08, chapter 03 (CMYK builds) and the logo files
Check finished work before it goes out The checklist at the end of chapters 08, 09 and 11, and the one at the end of this chapter
Anything else llms-full.txt

Set-up by tool

ChatGPT

  • Project or custom GPT: upload llms-full.txt and huxberry-tokens.json as knowledge files, and paste the system prompt below into the instructions.
  • A single chat: with browsing on, paste the llms-full.txt address and ask it to read the whole file before answering.

Claude

  • claude.ai project: add llms-full.txt, huxberry-tokens.json and SKILL.md to the project knowledge, and paste the system prompt below into the project instructions.
  • Claude Code: install the skill once and Claude applies the brand whenever a task mentions Huxberry. Run the same two lines again after each release to update it.
mkdir -p ~/.claude/skills/hux-brand-guidelines
curl -fsSL https://brand.huxapps.com/SKILL.md -o ~/.claude/skills/hux-brand-guidelines/SKILL.md
  • One repository only: save the same file as .claude/skills/hux-brand-guidelines/SKILL.md inside that repository instead.

Gemini

  • Gem: paste the system prompt into the instructions and upload llms-full.txt as a file.
  • A single chat: Gemini can read the addresses directly. Paste llms.txt and ask it to read the chapters it needs.

Codex

  • Skill: save SKILL.md as ~/.codex/skills/hux-brand-guidelines/SKILL.md (or .codex/skills/ inside a repository).
  • AGENTS.md: add this block to the file at the root of the repository.
## Huxberry brand
Before making anything customer-facing, read https://brand.huxapps.com/llms.txt and the chapters it points to.
Tokens: https://brand.huxapps.com/tokens/huxberry-tokens.json
Logo: use the files at https://brand.huxapps.com/logo/ as they are. Never draw or type the wordmark.

Cursor, Windsurf and other coding assistants

  • Rules file: save the system prompt below as .cursor/rules/huxberry-brand.mdc (Cursor) or the equivalent rules file for your editor, set to apply always.
  • Docs: in Cursor, add https://brand.huxapps.com/llms-full.txt under Settings, Features, Docs, so the guideline can be referenced with @Docs.

Image and video tools

  • The prompts live in chapter 11. Paste the master style block and the avoid block exactly as written.
  • Never ask an image model for the logo, text, badges, certificates or star ratings. They are added in layout from the real files.
  • Check every result against the chapter 11 checklist before it is used anywhere.

Agency and design tools

Tool What to give it
Figma huxberry-tokens.json through a tokens plugin, or the values typed from the Colours and Type pages. Satoshi from Fontshare. Logo SVGs from the zip
Canva, Adobe Express A brand kit built from the hex values on the Colours page, the SVG logos from the zip, Satoshi uploaded from Fontshare
InDesign, Illustrator, Affinity Swatches from the CMYK builds in chapter 03 for coated stock, logo SVGs, Satoshi installed from Fontshare, the print rules in chapter 08
Shopify, Klaviyo, Mailchimp huxberry-tokens.css for the values, chapter 07 for components, chapter 09 for email
Slides, Docs, Office The hex values, Satoshi (Arial where it cannot be installed), the PNG logos from the zip

System prompt to paste

Paste this into the instructions of any assistant. Shorten it if the tool has a character limit, but keep the numbered rules.

You are working for Huxberry, a natural and organic sleep and furniture brand in Dubai.
Follow the Huxberry brand guidelines at https://brand.huxapps.com
Index: https://brand.huxapps.com/llms.txt
Full text: https://brand.huxapps.com/llms-full.txt
Tokens: https://brand.huxapps.com/tokens/huxberry-tokens.json
Read the relevant chapter before you design or write anything.

Rules that are never broken:
1. Use only the brand colours in the tokens, each for its stated job. Text on green or dark grounds is White.
2. One typeface, Satoshi, with Arial as the fallback. Headlines are Regular 400, never bold. Body copy is 16 px minimum on the web and nothing is smaller than 14 px.
3. Buttons, badges and toggles are pills. Panels, cards and photos have 16 px corners. Flat: the only shadow is a soft one on review cards.
4. Sentence case everywhere. British English. Prices as AED 2,300. Sizes as 160 × 200 cm. No em dashes and no exclamation marks.
5. The logo is always one of the real files from https://brand.huxapps.com/logo/. Never type, draw, recolour, stretch or modify the wordmark.
6. Never invent claims, certificates, numbers, reviews or awards. An organic or safety claim names its certificate and applies only to the product category the certificate covers. Warranty: 15 years on Huxberry mattresses, 10 years on Hypnos mattresses.
7. Before you hand over, check the work against the checklist in the chapter you used and list what you checked.

When the guideline and your own taste disagree, the guideline wins. When the guideline is silent, choose the lighter, calmer, simpler option and say that you did.

Rules for agents

Rule Why
Use the real logo files. Never type, draw, trace or recolour the wordmark, and never delete the square on the H A redrawn logo is the fastest way to be sent back. The files are free to download and already in every colour we allow
Never invent a claim, certificate number, review, rating, award or statistic Every claim we make can be checked. A made-up one is a legal problem, not a style problem
Copy the values from the tokens. Do not approximate a hex code, a size or a radius "Close enough" greens drift across a hundred documents until nothing matches
Stay inside the palette. No tints, gradients or new colours If a lighter green is needed it is Pale Sage or Mist. If a lighter warm ground is needed it is Sand or Linen
No em dashes anywhere, in any language House style. Use a comma, a colon, a full stop or "to"
Keep every text size at or above the minimums in chapter 04 Small text is the most common complaint about generated layouts
Use the sizes and safe areas in chapters 09 and 11 for social, ads and video A layout that ignores the safe area loses its headline behind the app's own interface
Check the work against the chapter checklist and say what was checked The checklist is the definition of done for print, social and AI imagery
State assumptions. When the guideline is silent, say what was chosen and why Nobody can correct a decision they cannot see
Keep the record for AI images: prompt, reference, tool and date So a good image can be repeated and a wrong one traced

Keeping agents current

  • The version number is in the tokens JSON and at the top of llms.txt. After a release, re-download the files an agent holds as knowledge, and run the skill install lines again.
  • If an agent mentions Fraunces, Inter, 4 px corners, Deep Green buttons, Ochre stars or coral, it has read the 2024 guideline or the first 2026 draft. Point it at the addresses above.
  • Agents fetch the site directly, so an agent with browsing is always current. Files uploaded as knowledge are only as current as the upload.

Before you accept an agent's work

  • The logo is an unmodified file from logo/, the right version for its ground, with the ® rule from chapter 02 followed
  • Every colour is a token value and every text and ground pair passes the contrast table in chapter 03
  • Satoshi throughout, headlines Regular, nothing under 14 px on the web or under the print minimums in chapter 08
  • Sentence case, British English, prices as AED 2,300, no em dashes, no exclamation marks
  • Every claim names its certificate and the warranty is stated correctly
  • Pill buttons, 16 px corners, White and Sand bands, generous space, one dark band at most
  • Any AI image passes the chapter 11 checklist, and its prompt, reference and tool are saved with the file