Skip to main content

HTTP

The agent fetches each pattern from this site at generation time, so there is nothing to vendor locally, and pattern pages are always current. The skill ships as a SKILL.md plus a small local catalog and the Foundations rules; the pattern corpus itself lives on the docs site and is pulled over HTTP only for the patterns a given task actually selects. The base URL is baked into the skill; there is nothing to configure.

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 holds four small files and no corpus.

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

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

your-project/
├── .claude/
│ └── skills/
│ └── a11y-context-web-react-http/
│ ├── SKILL.md # brain: invocation + selection + fetch step
│ ├── decisions-protocol.md # when to ask before replacing your codebase's components
│ ├── patterns.json # local catalog (selection only)
│ └── global_rules.md # local Foundations rules
├── 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-http.

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 local catalog, then fetch …/web/react/components/{id} for each before generating UI code.

How it works​

HTTP is a retrieval mechanism, not a different brain. The skill's selection logic is identical to every other variant; only the retrieval step changes. Two of the three inputs stay local — only the per-component pattern pages travel over the network:

  • Catalog — local. The skill reads patterns.json from its own folder to select pattern IDs. It is not fetched over HTTP.
  • Pattern pages — remote. For each selected ID, the skill issues GET https://a11y-context-project.vercel.app/web/react/components/{id} — all fetches in parallel, each URL at most once per session — and extracts Must Haves, Don'ts, Golden Pattern, and Customizable from the response.
  • Foundations rules — local. The skill reads global_rules.md from its own directory and applies each rule by scope.

So HTTP mode is local catalog + local Foundations rules + remote pattern pages. The base URL is baked into the skill; there is nothing to configure.