Skip to main content

Local

The agent reads each pattern from a copy of the corpus bundled with the skill. The skill ships with the catalog, the Foundations rules, and every pattern file on disk; retrieval never leaves your machine. The skill's only allowed tool is Read. The skill is fully offline, zero network.

Install​

Pick your stack and your AI tool, then run the commands from your project's root. They create that tool's skills folder if it doesn't exist yet, download the skill, and unzip it there. The folder carries the whole corpus.

Your stack
Your AI tool
BASH
mkdir -p .claude/skills
curl -fsSL https://a11y-context-project.vercel.app/downloads/a11y-context-web-react-local.zip -o /tmp/a11y-context.zip
unzip -o /tmp/a11y-context.zip -d .claude/skills/

Or download a11y-context-web-react-local.zip and unzip it into .claude/skills/ yourself.

your-project/
├── .claude/
│ └── skills/
│ └── a11y-context-web-react-local/
│ ├── SKILL.md # brain: invocation + selection + read step
│ ├── decisions-protocol.md # when to ask before replacing your codebase's components
│ ├── patterns.json # local catalog (with source.path)
│ ├── global_rules.md # local Foundations rules
│ └── components/ # bundled pattern files, one per component
├── src/
└── package.json

To install it for every project instead, unzip into ~/.claude/skills/. Claude Code reaches for the skill on its own when you build UI; to call it by name, type /a11y-context-web-react-local.

To update, run the same commands again. Every ZIP is also on the Downloads page.

Verify​

After unzipping, run the prompts on Verify It's Working. The agent should select pattern IDs from the catalog, then read the matching components/{id}.md files from disk before generating UI code.

How it works​

Local is a retrieval mechanism, not a different brain — the selection logic is identical to every other variant; only the retrieval step changes. Every input sits on disk under the skill's own directory; nothing is fetched:

  • Catalog — local. The skill reads patterns.json to select pattern IDs. Each entry carries a source.path field pointing at that pattern's bundled file.
  • Pattern files — local. For each selected ID, the skill reads {source.path} from its own folder (for example components/toast.basic.md) and extracts Must Haves, Don'ts, Golden Pattern, and Customizable.
  • Foundations rules — local. The skill reads global_rules.md and applies each rule by scope.

The skill's only allowed tool is Read — there is no network step at all.