automatica11y 0.4.0 → 0.4.1

package/AGENTS.md

@@ -10,6 +10,8 @@ Keep the user's request as they gave it, including the target and any settings t
 npx --yes automatica11y@latest guide skill
 ```
 
+If `automatica11y` is already on the `PATH` (the user ran `npm i -g automatica11y`, and `automatica11y --version` prints a version), you can run `automatica11y guide skill` and `automatica11y guide fixtures` instead, and use `automatica11y` wherever the steps say `npx --yes automatica11y@latest`. The version check in the steps still applies. An installed copy can be older than the steps expect, and then the check stops you. Use `npx` when the installed version is the wrong series, or when nothing is installed.
+
 When the steps tell you to write a fixture, read the fixture guide:
 
 ```bash

package/README.md

@@ -13,12 +13,22 @@ It's **not** an attestation or certification tool. Automated checks cover only p
 
 You need Node 20 or newer and Chrome or Chromium.
 
+Install it once, and `automatica11y` is on your `PATH`, with the short name `a11y` too:
+
+```bash
+npm i -g automatica11y
+```
+
+Then run it without `npx`:
+
 ```bash
-npx automatica11y doctor
-npx automatica11y audit https://example.com
-npx automatica11y compare radix=npm:@radix-ui/react-dialog aria=npm:react-aria-components
+automatica11y doctor
+automatica11y audit https://example.com
+automatica11y compare radix=npm:@radix-ui/react-dialog aria=npm:react-aria-components
 ```
 
+You can skip the install and put `npx` in front instead, for example `npx automatica11y doctor`. `npx` fetches the tool the first time and checks the registry after that. A global install doesn't update itself, so run `npm i -g automatica11y@latest` to upgrade, and `automatica11y --version` to see what you have. The rest of this page writes the short form. Add `npx` if you didn't install it.
+
 `doctor` checks your setup. If it can't find a browser, it prints the command that installs one:
 
 ```bash
@@ -120,7 +130,7 @@ Fixtures are code that the tool bundles and runs in a browser on your machine. W
 
 ## Use it with an AI agent.
 
-The tool prints its own guidance, so any agent that can run `npx` can learn to use it:
+The tool prints its own guidance, so any agent that can run `npx` can learn to use it. If the tool is installed globally, the agent can run `automatica11y guide skill` instead of `npx automatica11y@latest guide skill`:
 
 ```bash
 npx automatica11y@latest guide           # where to start (the AGENTS.md file)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "automatica11y",
-  "version": "0.4.0",
+  "version": "0.4.1",
   "description": "Test and compare the accessibility of web pages, Storybook builds, and npm component libraries.",
   "license": "MIT",
   "type": "module",

package/skills/automatica11y/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: automatica11y
-compatibility: Needs Node 20 or newer, a shell that can run npx, and network access to the npm registry.
+compatibility: Needs Node 20 or newer, a shell that can run npx or the installed automatica11y command, and network access to the npm registry.
 description: Test and compare web accessibility. Use when someone asks how accessible a web page, Storybook, or npm component library is, asks for an accessibility or WCAG check or audit, or asks to compare the accessibility of two or more sites or component libraries (for example "how accessible is Radix Dialog?" or "compare React Aria and Headless UI").
 ---
 
@@ -20,6 +20,8 @@ automatica11y tests and compares web accessibility. This skill only gets you sta
 
    If the command exits with an error or prints no usable output, including after that retry, tell the user it failed, include the error text, and stop. Don't continue with partial instructions.
 
+   If `automatica11y` is already installed (`automatica11y --version` prints a version), you can run `automatica11y guide skill` instead. The steps check that the installed version matches them.
+
    After reading the steps, pass only settings they list as supported. If the user named a setting they don't list as supported, tell the user which setting is unsupported, list the supported values from the steps, and ask which to use. Don't ask again for anything they've already said.
 
 4. If you can't run shell commands, or `npx` can't reach the npm registry, tell the user and stop. Don't guess at results.

package/skills/automatica11y-runner/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: automatica11y-runner
-compatibility: Needs Node 20 or newer, Chrome or Chromium, a shell that can run npx, and network access to the npm registry.
+compatibility: Needs Node 20 or newer, Chrome or Chromium, a shell that can run npx or the installed automatica11y command, and network access to the npm registry.
 description: The full steps for running automatica11y audits and comparisons, from building the command to writing the report. Use it when the automatica11y skill or AGENTS.md sends you here, or when you've already been told to run automatica11y and need the steps.
 ---
 
@@ -24,6 +24,8 @@ npx --yes automatica11y@latest --version
 
 If the command exits with an error or prints nothing, tell the user it failed, include the error text, and stop. If the output doesn't start with `0.4.`, stop. Tell the user the version you got and the series this copy expects (`0.4.x`). If this copy came from a file, offer to read the matching steps with `npx --yes automatica11y@latest guide skill`. Don't run an audit until the user confirms how to proceed.
 
+If the user installed the tool globally (`npm i -g automatica11y`), `automatica11y` is on the `PATH` (so is the short name `a11y`), and it runs the same commands as `npx --yes automatica11y@latest`. Every command in this skill is written with `npx`, so replace that prefix with `automatica11y` only when `automatica11y --version` passes the check above. If the installed version is the wrong series, or nothing is installed, use `npx`.
+
 ## 2. Check the setup
 
 ```bash