⏳ This skill is pending AI review.
Scores will appear once the review pipeline completes.
check-accessibility
Review component for accessibility issues
Choose how to use this skill
You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.
1. Native installer
This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.
Do not guess an installer command or replace an existing version without reviewing the diff.
2. Complete package recommended
Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.
No complete ProSkills package is published for this listing yet.3. Prompt-only
Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.
Need only the instruction file?
Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.
No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.
// RATINGS
Not yet listed on ClawHub or SkillsMP
// README
Source-first architecture
AgnosticUI components are copied into your project at install time.
They live in your repo (not hidden inside node_modules):
- Full control over the source
- Native integration with your framework
- AI-readable, high-fidelity context
You own the source (and the Context)
cd your-project
npx agnosticui-cli init --framework vue # or react, lit, svelte
npx agnosticui-cli add Button Card Input
The component source lands directly in your project. Readable, editable, and yours.
src/
components/
ag/
Button/
Button.vue ← your file now
Button.css ← your tokens now
Button.test.ts ← your tests now
Components land under src/components/ag/ by default: a dedicated namespace that keeps AgnosticUI components separate from your own. Configurable if you prefer otherwise.
🤖 AI-Native by Design
Because the code is local, it solves the "Black Box" problem of traditional libraries hidden in node_modules.
Cursor · Claude · Copilot · Windsurf · Aider · Gemini · Replit · Kiro · Antigravity
Every tool sees the raw source. This creates a high-fidelity environment for Generative UI and Agent-driven interfaces:
- Reduce Hallucination: No more "invented" props or APIs. Since the LLM reads local files like any other code, it knows exactly what is possible.
- Better Token Efficiency: Using semantic HTML and standard CSS provides "clean context." Agents spend fewer tokens to understand the UI, leading to faster, more accurate generations.
- Agent Skills: Treat AgnosticUI Playbooks as pre-defined skills. Use them to prompt an agent to scaffold complex, accessible workflows (Login, Onboarding, Discovery Dashboard, Support Center, Data Grids) using the local components it already "sees."
This is the architecture for the next era of development: context-aware, framework-agnostic, and AI-ready.
The schema-driven layer ships with three companion documents:
v2/docs/sdui-architecture.md— full system architecture: codegen pipeline, node graph model, renderers, CI gates, and key design decisionsv2/docs/llm-prompt-guide.md— copy-paste system prompt template and few-shot examples for generating validAgNode[]graphsv2/docs/schema-coverage.md— per-component SDUI coverage registry, renderer parity status, and omission reasons
Built once. Runs everywhere.
AgnosticUI's components are authored as Lit Web Components, a standards-based layer over native Custom Elements. The CLI wraps them for your framework at copy time.
Your design system doesn't fork when your tech stack does. Supports agent-generated UI workflows directly from Playbooks.
...
| AgnosticUI | Typical component library | |
|---|---|---|
| Source in your repo | ✅ | ❌ |
| Framework agnostic core | ✅ | ❌ |
| LLM-readable locally | ✅ | ❌ |
| AI & agent-driven Playbooks included | ✅ | ❌ |
| Multiple theme skins | ✅ | Limited |
| Zero runtime dependency | ✅ after ejection | ❌ |
AI Playbooks: AI-Prompt-Driven UI Components
Playbooks (Login Form, Onboarding Wizard, Discovery Dashboard, Support Center, Data Grid, Blog / Article Reader, Landing / Marketing Page) demonstrate modular, prompt-driven UI components. Each Playbook can be used in agent systems, for context-aware applications, or to create generative UI patterns.
| Playbook | What it builds |
|---|---|
| Login Form | Responsive login: mobile, floating card, two-column desktop; works with AI prompt-driven generation |
| Onboarding Wizard | Multi-step flow with progress, validation, and skip logic; supports agent-assisted workflows |
| Discovery Dashboard | Dashboard shell with header, sidebar, and data regions — ideal for agent-generated interfaces |
| Support Center | Help center with search, categories, and article layout; integrates with prompt-driven workflows |
| Data Grid | Responsive, interactive data grid with sorting, filtering, and multiple view modes; compatible with agent-driven and context-aware interfaces |
| Blog / Article Reader | Typography-first editorial layout with scroll-aware components and in-article search highlighting; theme switcher, dark/light mode, React/Vue/Lit demos |
| Landing / Marketing Page | Polished product marketing page with hero, features, testimonials, pricing, and FAQ; animated components, theme switcher, dark/light mode, React/Vue/Lit demos |
Each Playbook on the docs site includes live StackBlitz examples for React, Vue, and Lit, and ships with:
PROMPT-3-FRAMEWORKS.md: one prompt to generate the pattern across all three frameworks- Skin switcher to preview your theme tokens instantly
Fully prompt-ready for agent-driven UI generation. Drop a Playbook prompt into Cursor, Claude Code, or Copilot and watch it assemble Input, Button, Card, and FormGroup correctly on the first try — because it has the full recipe, not just a component reference.
The prompts are yours to adapt. Feed o
// HOW IT'S BUILT
// FILES
2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.
.claude/skills/check-accessibility/SKILL.md2.5 KBupstream ↗
--- name: check-accessibility description: Review component for accessibility issues disable-model-invocation: true allowed-tools: Read, Grep, Glob, WebSearch, WebFetch --- **Usage:** `/check-accessibility COMPONENT_NAME` **Examples:** - `/check-accessibility button` - `/check-accessibility alert` - `/check-accessibility v2/lib/src/components/Button.ts` Check accessibility for: $ARGUMENTS **Setup:** 1. Read `.claude/PROJECT_CONTEXT.md` for AgnosticUI structure and accessibility principles **Process:** 2. **Search for latest standards:** - Use WebSearch for "WCAG 2.2 [component-type] accessibility" - Use WebSearch for "ARIA [specific-pattern] best practices" - Fetch W3C WAI-ARIA documentation if needed for specific patterns 3. **Locate component files:** - Core component: `v2/lib/src/components/$ARGUMENTS*` - Framework implementations if relevant: `v2/playgrounds/*/src/stories/*$ARGUMENTS*` - Check PROJECT_CONTEXT for AgnosticUI's accessibility standards location 4. **Analyze against current standards:** - **Semantic HTML:** Proper element usage for meaning and structure - **ARIA attributes:** Correct, necessary, and following latest specs - **Keyboard navigation:** Tab order, focus management, keyboard shortcuts - **Focus indicators:** Visible focus styles meeting contrast requirements - **Screen reader support:** Meaningful labels, descriptions, live regions - **Color contrast:** WCAG 2.2 AA requirements (4.5:1 text, 3:1 UI) - **Touch targets:** Minimum 44x44px for interactive elements - **Motion/animation:** Respects prefers-reduced-motion 5. **Framework-specific considerations:** - Check if accessibility differs across Lit, React, Vue implementations - Verify ARIA is applied correctly in each framework's rendering - Test that events work with keyboard in all frameworks 6. **Report findings:** - List issues with severity (Critical/High/Medium/Low) - Reference specific WCAG 2.2 success criteria - Provide remediation steps with code examples - Link to current W3C/MDN documentation - Note AgnosticUI-specific patterns to follow 7. **If fixes requested:** - Propose changes that work across all frameworks - Ensure fixes align with AgnosticUI's CSS-first approach - **WAIT FOR USER APPROVAL** before implementing **AgnosticUI Accessibility Requirements:** - WCAG 2.1 AA compliance minimum - Framework-agnostic solutions preferred - CSS custom properties for focus indicators - Consistent behavior across Lit, React, VueREADME.mdupstream ↗
Contents are not inlined in the catalog. Open the upstream file.
Plain-text copy, no login: /skill-bundles/agnosticui-agnosticui-claude-skills-check-accessibility.md