Skill
Aurora ships a Claude Code skill alongside the components — a structured guide that gives any Claude session in the monorepo Aurora-aware context (correct imports, semantic tokens, component composition rules) without you having to remember to read the docs.
The skill is built from view/ content, not authored by hand. When the docs change, the skill regenerates from them.
External distribution is TBD
The skill currently lives only inside the scaler-mono monorepo and auto-loads via a symlink at the repo root. External consumers — sibling Scaler repos, teammates without GitHub access, eventual AWS-hosted distribution — will need an install path. Likely shape: a small CLI that downloads a versioned tarball into ~/.claude/skills/aurora/, with a pinned-version-plus-update-nag UX. The artifact (packages/aurora/skill/) is already designed to be portable across hosts; only the install / update mechanism needs to be defined when distribution becomes a goal.
What you get
Any Claude session in scaler-mono auto-loads the skill via a symlink at the repo root:
.claude/skills/aurora -> packages/aurora/skillThe skill ships:
- Always-loaded operating principles — semantic-token rules, button conventions, form-pattern reach-for, when to read a reference file.
- Per-component references loaded on demand — variants, sizes, props, do/don't, code examples.
- Foundations references — colors, typography, spacing, effects, icons.
- Pattern references — currently just forms; more as we add them.
In the same session you also get the import paths for every Aurora surface (auto-derived from package.json's exports), plus an alphabetical components index pointing to each reference file.
Editing the skill
The skill content is a derivative of view/. To update it, edit the source doc and run the regenerate-aurora-skill flow — see Contributing → Regenerating the skill.