Skip to content
AI Building

Build an Atrium app with AI

One minimised file with everything an AI tool needs: how to work, the hard rules, the full app contract and the design system. Upload it to any LLM, then describe your app.

ATRIUM-AI-BUILD.mdMarkdown
  1. Upload the file to ChatGPT, Claude, Cursor or any AI tool (or paste its contents).
  2. Describe the app you want in plain English.
  3. Let the AI ask you for the API key when it needs one.
View the file
Auto

Component · Feedback

Inline alert

View .md

Stable

Alerts tell managers about something on the whole screen or a section: a save worked, something needs checking, or something went wrong. They sit at the top of the area they are about.

Settings savedReminders will go out at 9am.

Specifications

Anatomy

Check the datesTwo tenancies end this week.
1) Edge
border-left: 4px solid (status colour)
2) Title
font-weight: var(--at-weight-bold)
display: block
3) Message
font-size: var(--at-text-sm)
background: status -bg token
padding: var(--at-space-4) var(--at-space-5)

Information

Neutral news: something is syncing, a change is coming.

Example

SyncingReadings update every hour.

Success

Confirms an action worked. Show it after saving.

Example

SavedYour settings are saved.

Warning

Something needs attention soon, but nothing has failed.

Example

Check the datesTwo tenancies end this week.

Error

Something failed. Say what happened and what to do next.

Example

Discovery

Something new worth knowing: a new feature, or a first-use tip. Show it once, and let managers dismiss it.

Example

New: bulk remindersSelect several tenants to remind them all at once.

Usage

When to use

  • After saving.
  • When something on the page needs attention.
  • At the top of a form that failed validation.

When not to use

  • For a single field error: use the field error.
  • For marketing or tips.

Content

  • Lead with a short title: "Saved", "Could not save".
  • Then one sentence on what to do next.

Do and don't

DoSay what failed and how to fix it.
Don'tCodes and vague messages.

Do

  • Say what happened and what to do next.

Don't

  • Stack several alerts.

Implementation

HTML

<div class="at-stack at-stack--tight">
  <div class="at-alert at-alert--info" role="status"><strong class="at-alert__title">Syncing</strong>Readings update every hour.</div>
  <div class="at-alert at-alert--success" role="status"><strong class="at-alert__title">Saved</strong>Your settings are saved.</div>
  <div class="at-alert at-alert--warning"><strong class="at-alert__title">Check the dates</strong>Two tenancies end this week.</div>
  <div class="at-alert at-alert--danger" role="alert"><strong class="at-alert__title">Could not save</strong>COHO did not respond. Try again.</div>
</div>

Classes

ClassWhat it does
at-alertNeutral
at-alert--info / --success / --warning / --dangerVariants
at-alert__titleBold first line
at-alert--successSuccess
at-alert--warningWarning
at-alert--dangerError
at-alert--discoverySomething new

Tokens used

--at-border, --at-bg-neutral, --at-border-info, --at-bg-info-subtle, --at-border-success, --at-bg-success-subtle, --at-border-warning, --at-bg-warning-subtle, --at-border-danger, --at-bg-danger-subtle, --at-border-discovery, --at-bg-discovery-subtle


Accessibility

  • Use role="alert" for errors and role="status" for confirmations.

Related