agentleFS
wearekansowearekanso/agent-skills/skills/react-native-accessibility/AGENTS.md

agent-skills / react-native-accessibility

AGENTS.md8 starsChanged 9 months agoMITView on GitHub

This file provides guidance to AI coding agents working with the react-native-accessibility skill. This skill automatically detects and fixes accessibility issues in React Native and Expo projects. It supports both iOS (VoiceOver) and Android (TalkBack), with platform-specific considerations noted per rule.

The file

We split this AGENTS.md into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 are 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.

  • 3

    Very specific

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

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

    Add the rule to rules/_sections.md under the appropriate priority section

    line 33
  2. Very specific:

    Update SKILL.md to reference the new rule in the Quick Reference section

    line 34
  3. Very specific:

    Add a before/after example to the relevant file in examples/

    line 35

≈ “Common” is an estimate: at least 1 in 5 of the 42,283 AGENTS.md 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
AGENTS.md

AGENTS.md

This file provides guidance to AI coding agents working with the react-native-accessibility skill.

Skill Overview

This skill automatically detects and fixes accessibility issues in React Native and Expo projects. It supports both iOS (VoiceOver) and Android (TalkBack), with platform-specific considerations noted per rule.

File Structure

  • SKILL.md — Main skill definition with 5-phase workflow
  • rules/ — Individual detection and fix rules, one per issue category
    • _sections.md — Section index with priority ordering
    • _template.md — Template for adding new rules
    • p0-*.md — Critical priority rules (2 rules)
    • p1-*.md — High priority rules (5 rules)
    • p2-*.md — Medium priority rules (9 rules)
  • assets/ — Templates and checklists
    • jest-a11y-test-template.tsx — Jest accessibility test template
    • checklist.md — Manual verification checklist for both platforms
  • examples/ — Before/after transformation examples
    • before-after-expo.md — Expo managed workflow examples
    • before-after-bare-rn.md — Bare React Native examples
  • references/ — API and guideline reference material
    • react-native-a11y-api.md — Full React Native accessibility API catalog
    • platform-differences.md — iOS vs Android behavior differences
    • wcag-guidelines.md — WCAG AA and platform guideline reference

Adding a New Rule

  1. Copy rules/_template.md to rules/{priority}-{rule-name}.md
  2. Fill in all sections: detection patterns, fix logic, before/after examples, platform considerations
  3. Add the rule to rules/_sections.md under the appropriate priority section
  4. Update SKILL.md to reference the new rule in the Quick Reference section
  5. Add a before/after example to the relevant file in examples/

Key Principles

  • Never overwrite existing accessibility code
  • Add [VERIFY] markers on inferred labels that need human review
  • Preserve formatting — match the indentation and style of surrounding code
  • Detect project type — check for app.json/app.config.js (Expo) vs bare RN
  • Platform-aware fixes — include both accessibilityElementsHidden (iOS) and importantForAccessibility (Android) when hiding elements
  • Progressive disclosure — SKILL.md stays concise; rules and references are loaded on-demand
  • 48x48 dp minimum — use as the unified touch target minimum (satisfies both iOS 44pt and Android 48dp)

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.