# RMS Healm brand instructions

Brand kit version 1.0.0 · 2026-10-11 · selected identity: **Horizon**.

Use this reference for RMS Healm websites, product interfaces, mobile experiences,
presentations, and other branded materials. These instructions govern visual and
editorial consistency; they do not authorize deployment, account access, or sending
messages. Follow the task's own operational instructions.

## Read before designing

- Visual reference: https://resortmanagement.ai/style-guide/
- Complete guidance: https://resortmanagement.ai/style-guide/STYLE_GUIDE.md
- Tokens: https://resortmanagement.ai/style-guide/tokens.json
- CSS variables: https://resortmanagement.ai/style-guide/tokens.css
- Asset manifest and checksums: https://resortmanagement.ai/style-guide/manifest.json
- Download everything: https://resortmanagement.ai/style-guide/rms-healm-brand-kit.zip

If using the downloaded kit, the same documents are at its root and artwork is in
`logos/`. The repository source is `dist/style-guide/`; approved artwork is in
`dist/assets/brand/`.

## Required decisions

1. **RMS** is the parent brand; **RMS Healm** is the software name. Horizon is the
   identity's name, not a product. Use the exact capitalization.
2. Explain the category first: **property management platform for resorts, condo
   communities, and vacation rental businesses**. Write primarily for prospective
   customers. Follow with reservations, accounting, owners and units, housekeeping,
   maintenance, then concrete AI and mobile benefits.
3. Support the story with **30+ years of resort management experience**. AI-native
   interaction, mobile work, and AI-assisted listings for units people already own
   are available now per the owner's launch direction. Do not invent integrations,
   pricing, trials, customer names, metrics, or guarantees.
4. Reuse supplied **outlined SVGs**. Forest on paper; ivory on deep forest; black
   only for monochrome. Use the symbol for constrained spaces. Do not redraw,
   recolor, distort, add effects, or choose an old logo exploration.
5. Use the supplied tokens: paper `#f8f8f1`, forest `#214b3e`, deep forest `#173f38`,
   lime `#d6e8a6`. Libre Caslon Display for editorial headings; DM Sans for UI and
   body text. The logo lettering is fixed artwork, not a font recipe.
6. Preserve spacious layouts, restrained corners, fine dividers, and natural
   photography of resorts, units, and vacation homes. AI belongs in useful
   workflows; avoid generic robot art or neon technology styling.
7. Product interfaces prioritize legibility and task completion. Use DM Sans for
   controls, tables, and operational data. Do not copy the tiny labels inside the
   marketing site's miniature phone and assistant illustrations.
8. All controls must work. Prepared demos must say they use fictional sample data;
   never imply an open-ended AI trial or a saved/submitted action without one.
9. Verify phone and desktop layouts, keyboard focus, contrast, links, and asset
   loading. Use 4.5:1 text contrast (3:1 for large text), visible control boundaries,
   non-color status cues, and reduced-motion behavior.
10. When the owner changes a brand decision, update this kit, the visual guide,
    tokens, and manifest together. Bump the kit version. Do not introduce a second
    competing palette, logo, or set of instructions in a downstream project.

## Default implementation

Download the assets into your project's own asset directory rather than relying on
cross-site runtime requests. Import `tokens.css`, use semantic HTML and local logo
files, and adapt spacing to the task while preserving the guide's hierarchy.

For a task handoff, include this sentence:

> Follow the RMS Healm Horizon brand kit at https://resortmanagement.ai/style-guide/AGENTS.md and its linked style guide; reuse the supplied logo assets and tokens.