spectrum-audit
Audit a codebase for adherence to the Spectrum design system and React Spectrum S2 best practices. Use when a developer asks to audit, review, lint, or check a project for Spectrum/S2 correctness, configuration, styling, accessibility, or component-usage issues.
- Installs
- 357
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://react-spectrum.adobe.com --skill spectrum-audit- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads spectrum-audit automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Spectrum Audit
Audit a codebase for adherence to the Spectrum design system and React Spectrum S2 best practices, then produce a scored, prioritized report. This skill is report-only — it does not modify any files.
When to use
Use when a developer asks to audit, review, lint, or check a project for Spectrum / S2 correctness, configuration, styling, accessibility, or component-usage issues.
Requires a project with @react-spectrum/s2 installed. If S2 is not a dependency, say so and stop.
How it works
Run these phases in order.
Phase 0 — Scope
- Identify the project — or, in a monorepo, the specific package — to audit. Audit the package, not the workspace root.
- Detect the package manager from the lockfile, the bundler (Vite / webpack / Next.js / Parcel / Rollup / ESBuild), and read
package.jsondependencies. - Confirm
@react-spectrum/s2is installed. Establish the source globs to scan (e.g.src/**/*.{tsx,jsx,ts,js}). - Check whether the
react-spectrum-s2skill is available (listed among the agent's installed skills, or present under a local skills directory such as.cursor/skills/or.agents/skills/). Record whether it was found — the report template uses this.
Phase 1 — Run the checks
Work through each check file in references/checks/, in order. For every violation, record a finding: {file:line, rule, severity, category, fix}. Cite only line numbers you actually read or grepped — never invent locations. Record one finding per distinct root cause at a file:line — if multiple check files cover the same issue (e.g. a missing collection aria-label or a third-party design system), assign it to the most specific check and do not duplicate it across categories.
- 01 — Setup & configuration
- 02 — Component usage
- 03 — Styling
- 04 — Accessibility & correctness
- 05 — Versioning & maintenance
- 06 — Testing
The canonical rules behind these checks live in the react-spectrum-s2 skill — read its SKILL.md (implementation guidance) and references/guides/getting-started.md, references/guides/component-decision-tree.md, and references/components/ as needed. If that skill is not installed, proceed using the check files alone, but note the limitation in the report (see Phase 3).
Phase 2 — Score
Apply the scoring rubric to the recorded findings to compute per-category scores and the overall Spectrum Adherence Score. The score is arithmetic over counted findings — do not estimate it.
Phase 3 — Report
Write SPECTRUM-AUDIT.md to the audited project following the report template: headline score, grade, and severity counts; a summary; scores by category; findings grouped by severity (each with a clickable file:line and the check name that defines its rule); prioritized action items; what looks good; and — if react-spectrum-s2 was not detected in Phase 0 — a recommendation to install it.
Phase 4 — Hand off
This skill does not edit code. Recommend:
-
The
react-spectrum-s2skill to implement the fixes. If it is not installed:npx skills add https://react-spectrum.adobe.com --skill react-spectrum-s2 -
The
migrate-react-spectrum-v3-to-s2skill if Spectrum 1 packages (@adobe/react-spectrum,@react-spectrum/*,@spectrum-icons/*) are present.
FAQ
What does the spectrum-audit skill do?
Audit a codebase for adherence to the Spectrum design system and React Spectrum S2 best practices. Use when a developer asks to audit, review, lint, or check a project for Spectrum/S2 correctness, configuration, styling, accessibility, or component-usage issues.
How do I install spectrum-audit?
Run npx skills add https://react-spectrum.adobe.com --skill spectrum-audit in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/spectrum-audit/ (personal) or .claude/skills/spectrum-audit/ (project).
Which AI agents can use spectrum-audit?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is spectrum-audit safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains spectrum-audit?
It is published by react-spectrum.adobe.com in react-spectrum.adobe.com. It has 357 recorded installs.
More from react-spectrum.adobe.com
react-spectrum-s2
react-spectrum.adobe.com
Build UIs with React Spectrum S2 (Spectrum 2), Adobe's component library for React. Use when developers are using @react-spectrum/s2 or need Adobe design system components. Includes React Aria Components docs as a reference for building custom components on top of unstyled primitives.
migrate-react-spectrum-v3-to-s2
react-spectrum.adobe.com
Open the skill to read its SKILL.md instructions.
Popular security skills
azure-compliance
microsoft/azure-skills
Run Azure compliance and security audits with azqr plus Key Vault expiration checks. Covers best-practice assessment, resource review, policy/compliance validation, and security posture checks. WHEN: compliance scan, security audit, BEFORE running azqr (compliance cli tool), Azure best practices, Key Vault expiration check, expired certificates, expiring secrets, orphaned resources, compliance assessment.
minimal-run-and-audit
lllllllama/rigorpilot-skills
Rigor Run skill for README-first deep learning repo reproduction. Use when the task is specifically to capture or normalize evidence from the selected smoke test or documented inference or evaluation command and write standardized reprooutputs/ files, including patch notes when repository files changed. Do not use for training execution, initial repo intake, generic environment setup, paper lookup, target selection, hidden scientific-meaning changes, or end-to-end orchestration by itself.
seo-audit
coreyhaines31/marketingskills
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," "indexing issues," "stuck on page 2," "striking distance keywords," "title tag rewrite," "low CTR," "local SEO," "Google Business Profile," or "map pack." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.
firebase-security-rules-auditor
firebase/agent-skills
Audits Firebase (Firestore, Cloud Storage) security rules for vulnerabilities, privilege escalation, role bypasses, create vs update inconsistencies, resource exhaustion, type safety, size limits, and hasOnly ownership checks. Use when auditing/reviewing rules, running red-team rule assessments, or scoring against auditor checklists. Don't use for Firebase CLI (login, deploy), Auth, Crashlytics, Remote Config, or database queries.
audit
pbakaus/impeccable
Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.
competitors
coreyhaines31/marketingskills
When the user wants to create competitor comparison or alternative pages for SEO and buyer-facing use. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'how do we compare to X,' 'competitor teardown,' 'audit our competitor pages,' 'are our comparison pages out of date,' or 'competitive asset audit.' Use this for any content that positions your product against competitors. Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. For auditing existing claims (not researching competitors from scratch, which is competitor-profiling; not technical SEO on these pages, which is seo-audit), use the asset audit here. For internal battle cards and sales-specific competitor docs, see sales-enablement.