eslint-aria-accessibility-project-specific

Codify recurring project-specific ESLint accessibility conventions into decision checklists.

171|10|Updated Feb 20, 2026

Search Tags:#accessibility #eslint #conventions #checklists #project-specific #aria

Ready to run

npx skills add https://github.com/fmflurry/settings-opencode --skill eslint-aria-accessibility-project-specific

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: eslint-aria-accessibility-project-specific
Source: https://github.com/fmflurry/settings-opencode/tree/main/.claude/skills/eslint-aria-accessibility-project-specific
Command: npx skills add https://github.com/fmflurry/settings-opencode --skill eslint-aria-accessibility-project-specific

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and codify recurring project-specific conventions to reduce drift and improve consistency.

Core Features & Use Cases

Provides a reusable pattern that documents and enforces project-specific conventions (e.g., ESLint accessibility rules) for consistency across sessions and repositories.
Translates conventions into simple decision checklists with concrete examples and anti-pattern guidance.
Use Case: Onboard new teams and ensure uniform application of project standards across multiple projects.

Quick Start

Apply this pattern to translate recurring conventions into a decision checklist and example workflow for your project.

Frequently Asked Questions about eslint-aria-accessibility-project-specific

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I enforce project-specific ESLint accessibility rules across multiple repositories?▼

To enforce project-specific ESLint accessibility rules, you can codify recurring conventions into a reusable pattern with decision checklists and anti-pattern guidance to reduce drift across repositories. This ensures consistent application of team standards during onboarding.

What is the best way to document ARIA accessibility conventions for consistent team usage?▼

Documenting ARIA accessibility conventions involves translating them into simple decision checklists with concrete examples and anti-pattern guidance. This standardizes project-specific rules so teams apply them uniformly across multiple sessions.

How do I reduce configuration drift for ESLint accessibility checks in software projects?▼

Reduce configuration drift for ESLint accessibility checks by identifying and codifying recurring project-specific conventions into a reusable pattern. This provides structured decision checklists to maintain consistency across different sessions and codebases.

Can I use a checklist pattern to onboard new teams to project-specific ARIA conventions?▼

Yes, you can use a checklist pattern to onboard new teams to project-specific ARIA conventions. This pattern translates conventions into decision checklists with examples and caveats, ensuring uniform application of project standards across multiple projects.

Does codifying ESLint accessibility rules require any specific dependencies?▼

Codifying ESLint accessibility rules with this pattern requires no specific dependencies. It provides a reusable structural pattern with steps and examples to translate conventions into checklists, working independently within your existing software engineering environment.

When should I avoid using a reusable pattern for ESLint accessibility conventions?▼

You should avoid using a reusable pattern for ESLint accessibility conventions if your project lacks recurring rules or if your team requires highly dynamic, non-standardized configurations that cannot be translated into simple decision checklists and anti-pattern guidance.