refactor

Refactor codebases to fix accessibility issues and improve WCAG compliance.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/scamai/scamai-landing --skill refactor-scamai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: refactor
Source: https://github.com/scamai/scamai-landing/tree/main/.agents/skills/refactor
Command: npx skills add https://github.com/scamai/scamai-landing --skill refactor-scamai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Accessibility challenges in legacy and modern codebases are common, and this Skill centrally addresses them by performing targeted refactors to improve semantics, keyboard navigation, and screen-reader compatibility.

Core Features & Use Cases

  • Extracts accessible components and restructures markup for clearer semantics and maintainability.
  • Adds ARIA attributes, proper roles, and semantic HTML to align with WCAG 2.1 standards.
  • Applies across single files or large projects to drive scalable accessibility improvements.

Quick Start

Refactor the target path to fix accessibility issues while preserving functionality.

Frequently Asked Questions about refactor

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

FAQPage Schema
How do I refactor frontend code to fix WCAG accessibility issues?

You can refactor frontend code for WCAG compliance by restructuring markup for clearer semantics, adding proper ARIA attributes, and implementing roles to improve keyboard navigation and screen-reader compatibility across targeted directories.

What is the best way to add ARIA patterns to legacy HTML?

The best way to add ARIA patterns to legacy HTML is through targeted refactoring that restructures existing markup into semantic components. This ensures changes align with project coding standards while improving screen-reader compatibility and keyboard navigation.

Can I apply accessibility refactoring across multiple files or an entire directory?

Yes, accessibility refactoring can be applied across multiple files or a targeted directory. This approach drives scalable accessibility improvements by extracting accessible components and implementing proper ARIA patterns throughout the project scope.

How do I ensure refactoring for accessibility preserves existing functionality?

Ensuring refactoring for accessibility preserves existing functionality requires careful code changes that focus on semantics and ARIA implementation without altering core logic. Changes should be documented for traceability and aligned with project coding standards.

Do I need to manually update components to meet WCAG 2.1 standards?

Meeting WCAG 2.1 standards requires updating components by adding proper ARIA attributes, semantic HTML, and correct roles. Refactoring extracts accessible components and restructures markup to align with these accessibility compliance requirements.