Aurora

Skill ​

Aurora ships a Claude Code skill alongside the components, so any Claude session in the monorepo writes Aurora-correct UI — right imports, semantic tokens, existing components instead of hand-rolled twins — without you having to paste context.

The design is deliberately lean: there is no generated copy of anything.

  • These docs are the skill's component layer. Agents read the same view/*.md files you are reading now — there is no transformed mirror to drift out of sync.
  • Code facts are pointed at, never duplicated. Import paths, icon names, and token lists are read from src/ at use time (src/components/<x>/index.ts, the icon collections, src/theme/css/tailwind/*.css), so they cannot be stale.
  • Two hand-written files carry everything else, at packages/aurora/skill/:
    • SKILL.md — the always-loaded layer: the anti-guessing rule, Tailwind-reflex corrections (text-error → text-error-primary, …), silently-wrong defaults, house style, an intent → component routing table, and the component index.
    • review.md — audit mode: a fixed checklist + output format for reviewing existing UI against Aurora.

How it loads ​

Any Claude session in scaler-mono auto-loads the skill via a symlink at the repo root:

.claude/skills/aurora -> packages/aurora/skill

External distribution is TBD

The skill currently lives only inside the scaler-mono monorepo. External consumers — sibling Scaler repos, teammates without repo access — would need an install path that ships skill/ together with view/ and src/ (the skill points into both). Defined when distribution becomes a goal.

How docs feed the skill ​

Each doc's frontmatter carries two fields the skill derives its routing from:

  • blurb: — ≤10 words, becomes the doc's line in SKILL.md's component index.
  • reach: — task phrases in the requester's vocabulary ("a search box above a table"), becomes rows in the intent → component table.

Everything else in the doc is read on demand when an agent works with that family. The authoring contract — section order, Incorrect/Correct pairs, gotcha style — lives in view/_template.md.

Editing the skill ​

  • Component guidance → edit the component's view/ doc. Done — agents read it directly.
  • Added, renamed, or removed a doc (or changed blurb:/reach:) → run the regenerate-aurora-skill skill to refresh SKILL.md's two derived sections — see Contributing → Regenerating the skill.
  • Norms, corrections, house style → edit packages/aurora/skill/SKILL.md by hand.