410 skills · sorted by relevance
Review custom tabs, menus, lists, and similar controls for required ARIA child roles, which describe interface elements to assistive technology. Identify missing roles and structural wrappers that prevent screen readers from recognizing the items.
Review ARIA attributes, which describe interface elements to assistive technology, for invalid values and missing ID references. Get specific corrections and guidance for checking that element states and labels are communicated correctly.
Check buttons, links, and other controls for clear accessible names, the labels used by assistive technology. Identify missing or vague names and suggest descriptive text or aria-label attributes that explain each action or destination.
Review file explorers and other expandable tree interfaces so screen reader users can identify each item. Check descriptive names and expanded states, then suggest fixes using visible text or ARIA attributes, which provide information to assistive technology.
Review buttons, links, and menu items to check whether screen readers announce their purpose. Identify missing accessible names, meaning labels available to assistive technology, and suggest fixes using text or ARIA attributes, with guidance for verification.
Review HTML for deprecated ARIA roles, which describe elements to assistive technology, and abstract roles that should not appear in markup. Suggest recommended replacements or native HTML elements and explain potential browser and screen reader compatibility issues.
Review ARIA roles, labels that tell assistive technology what page elements do, and correct invalid values. Prefer standard HTML controls where suitable, then check keyboard behavior, focus movement, and screen reader output to verify the changes.
Check HTML for misspelled or nonexistent ARIA attributes, which convey interface information to assistive technology. Replace invalid names with standard attributes and explain how to verify that screen readers can interpret element roles and states.
Check whether ARIA attributes, which describe interface elements to assistive technology, are supported by each element’s role. Review rendered HTML and interactive states, identify invalid combinations, and suggest removals or corrections to support accurate screen reader interpretation.
Check a page for duplicate accesskey values, which define keyboard shortcuts for elements. Identify conflicting assignments, suggest unique values or removal, and describe how to verify keyboard behavior with browser accessibility tools or assistive technology.
Check that ARIA roles, which describe interface elements to assistive technology, include their required attributes. Identify missing state or value information in rendered HTML and get guidance on fixes and accessibility verification.
Review meter elements for accessible names, the labels screen readers use to explain what a value measures. Identify missing labels, add aria-label or aria-labelledby, and describe checks using browser accessibility tools or assistive technology.
Review whether ARIA roles, which describe interface elements to assistive technology, have the required parent roles. Find misplaced menu items, tabs, or list items, suggest suitable containers, and explain how to verify the corrected structure.
Review tooltips so their extra information is available to screen reader users. Check accessible names, meaning labels available to assistive technology, and links to the elements that trigger them, then suggest fixes and verification steps.
Search current library documentation and code examples with Context7 CLI, a command-line tool. Find API usage and configuration guidance, select available version-specific documentation, and prioritize examples in the programming language you use.
Research companies from the terminal using a domain name. Intelwatch combines financial data and technology stack detection into readable company profiles, with an optional AI due diligence mode for examining potential acquisition targets.
Support decisions with market, technical, competitor, and other research. Draft prompts for external research tools, condense existing reports into source-cited summaries, or conduct web research directly, including comparisons between candidates.
Turn a plain language app request into a project plan, technology choices, and coordinated development tasks. Use project templates to structure web, mobile, desktop, API, or command line applications, with agents handling different development responsibilities.
Plan and develop Android apps with guidance on technology choices, app structure, screen design, testing, debugging, performance, and releases. Covers native Kotlin and Java development alongside Flutter, RN, KMM, and hybrid approaches.
Prepare an industry briefing once a project's sector is defined. It covers sector context, potentially applicable regulations, familiar interface patterns, technology choices, and risks, while separating verified evidence from hypotheses and questions requiring further review.
Build and review interfaces against WCAG 2.2 accessibility guidelines. Covers keyboard navigation, screen readers that read interface content aloud, accessible forms, mobile support, and display preferences, helping identify and fix barriers to using a website or app.
Investigate bugs and slow applications through reproducible examples, logs, environment comparisons, and hypothesis testing. The skill structures root cause analysis and performance measurement, helping developers narrow down failures and verify that a fix works.
Create and maintain project documents in conductor/ covering the product, technology stack, development workflow, and work units. Extract context from existing code, check document consistency before implementation, and update documentation as the project evolves.
Guide web app testing with screen readers such as VoiceOver, NVDA, and JAWS. Check forms, dialogs, keyboard navigation, and spoken update notifications to identify accessibility problems across desktop and mobile browser combinations.