agentleFS
Sign inStart free
adobeadobe/spectrum-web-components/.cursor/rules/component-accessibility-specification.mdc

spectrum-web-components / rules

Cursor rule1.6k starsChanged 8 days agoApache-2.0View on GitHub

Points to the component-accessibility-specification skill when a component accessibility specification document is being written or edited.

Trending

Less talk lately.about the whole repository

Dec 2025: 1 mentionJan 2026: 0 mentionsFeb 2026: 1 mentionMar 2026: 0 mentionsApr 2026: 12 mentionsMay 2026: 0 mentionsJun 2026: 1 mentionJul 2026: 4 mentionsAug 2026: 7 mentionsSep 2026: 0 mentionsOct 2026: 4 mentionsNov 2026: 1 mention
Dec 2025Jun 2026Nov 2026
Mentions a month of the adobe/spectrum-web-components repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about adobe/spectrum-web-components

The biggest 5 of 51 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 51

Talked about on GitHub and Bluesky (51 times).

On GitHub · 50

45 more on GitHub

The file

We split this component-accessibility-specification.mdc into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Before you write or change content, load the component-accessibility-specification skill at …

    line 13

≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
component-accessibility-specification.mdc
---
description: Points to the component-accessibility-specification skill when a component accessibility specification document is being written or edited.
globs: CONTRIBUTOR-DOCS/**/component-accessibility-specification.md
alwaysApply: false
---

<!-- GENERATED by .ai/scripts/sync.js from .ai/rules/component-accessibility-specification.md. Do not edit. Edit the source and run `yarn ai:sync`. -->

# Component accessibility specification documents

You're working on a component accessibility specification document for a migrated or new gen2 component, including the "analyze accessibility" migration step. A 1st-gen predecessor is not required.

Before you write or change content, load the `component-accessibility-specification` skill at `.ai/skills/component-accessibility-specification/SKILL.md`. It defines the required section order, the ARIA recommendations structure, Shadow DOM guidance, keyboard and focus conventions, and the testing table format.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free