Implement WCAG 2.1 accessibility standards for semantic HTML, keyboard navigation, ARIA attributes, and screen reader support.
Create detailed user stories, acceptance criteria, and feature specs
Example: Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example: Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example: Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example: Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Submit your Claude Code skill and start earning
epx add supercent-io/skills-template --skill web-accessibilityCompatible with
Supported agents
Covers semantic HTML structure, keyboard navigation (Tab, arrow keys, ESC), and focus management for modals and interactive components
Provides ARIA attribute guidance (aria-label, aria-live, aria-hidden, role attributes) with practical React/TypeScript examples
Includes color contrast requirements (WCAG AA/AAA), visual focus indicators, and testing strategie
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionweb-accessibilityExecute the skills CLI command in your project's root directory to begin installation:
epx add supercent-io/skills-template --skill web-accessibilityFetches web-accessibility from supercent-io/skills-template and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
.cursor/skills/web-accessibility
Restart Cursor to activate web-accessibility. Access via /web-accessibilityin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Time estimate: 30-60 minutes to see productivity improvements
Prerequisites
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
apple-design
emilkowalski/skills · design · tag: web
nutritional-specialist
ailabs-393/ai-labs-claude-skills · Productivity · same category
travel-planner
ailabs-393/ai-labs-claude-skills · Productivity · same category
yt-dlp
lwmxiaobei/yt-dlp-skill · Productivity · same category
xauusd-trading
huynguyen03dev/xauusd-trading · Productivity · same category
network-engineer
404kidwiz/claude-supercode-skills · Productivity · same category
web-accessibility is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
web-accessibility fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
web-accessibility has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: web-accessibility is the kind of skill you can hand to a new teammate without a long onboarding doc.
web-accessibility is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: web-accessibility is the kind of skill you can hand to a new teammate without a long onboarding doc.
Useful defaults in web-accessibility — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Solid pick for teams standardizing on skills: web-accessibility is focused, and the summary matches what you get after install.
We added web-accessibility from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in web-accessibility — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 31