⏳ This skill is pending AI review.
Scores will appear once the review pipeline completes.
stitch-a11y
Audits Stitch-generated components for WCAG 2.1 AA accessibility issues and applies fixes — semantic HTML, ARIA attributes, keyboard navigation, focus management, and screen reader support.
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
// README
stitch-kit
Your coding agent writes decent code and designs terrible UI. stitch-kit fixes the second half — it wires agents into Google Stitch (text prompts → genuinely beautiful screens) and teaches them to drive it properly.
I built this because I got tired of watching Claude Code generate UIs that look like a government form from 2004. Gray boxes, blue buttons, zero taste. Meanwhile Stitch generates pixel-perfect screens from text — but it's a raw MCP tool sitting there, and no coding agent knows how to use it well.
So I taught them.
All four of these came out of stitch-kit. Different briefs, genuinely different results — not one template with the hue rotated.
Generating designs needs Google Stitch. Sign in at stitch.withgoogle.com with any Google account, then grab an API key from settings. As of July 2026: no waitlist, no invite, free to use — but there are monthly generation limits and Google has signalled paid tiers, so treat the allowance as generous-but-finite. Check Stitch's own site before relying on any of that; it's their pricing to change, not mine.
Converting to code doesn't. The framework conversion skills take a local HTML file or a URL just as happily as a Stitch screen. If you already have markup and only want production components out of it, you need no Google account at all.
Install
npx @booplex/stitch-kit
Detects every supported client you have installed — Claude Code, Codex CLI, OpenCode, Crush, Cursor, VS Code, Gemini CLI — and wires up whatever each one supports. See Works with for what that means per client.
Then, inside Claude Code, add the skills:
/plugin marketplace add https://github.com/gabelul/stitch-kit.git
/plugin install stitch-kit@stitch-kit
Two steps, not one — the npx installer handles the agent and MCP wiring, the plugin adds the 36 skills. The agent works without them, but the skills are what make the output good.
npx @booplex/stitch-kit update # update to latest
npx @booplex/stitch-kit status # check what's installed
# 1. Add Stitch MCP (remote HTTP server — needs API key from stitch.withgoogle.com/settings)
claude mcp add stitch --transport http https://stitch.googleapis.com/mcp \
--header "X-Goog-Api-Key: YOUR-API-KEY" -s user
# 2. Install the plugin (inside Claude Code)
/plugin marketplace add https://github.com/gabelul/stitch-kit.git
/plugin install stitch-kit@stitch-kit
git clone https://github.com/gabelul/stitch-kit.git
cd stitch-kit && bash install-codex.sh
Then add Stitch MCP to ~/.codex/config.toml:
[mcp_servers.stitch]
url = "https://stitch.googleapis.com/mcp"
[mcp_servers.stitch.headers]
X-Goog-Api-Key = "YOUR-API-KEY"
Get your API key at stitch.withgoogle.com/settings.
Use $stitch-kit to activate the agent or $stitch-orchestrator for the full pipeline.
Compaction resilience (optional): to keep your project, screens, and PRD draft across a context compaction, stitch-kit needs the stitch-session helper on PATH — npm i -g @booplex/stitch-kit provides it, and install-codex.sh symlinks it. For automatic re-orientation after a compaction, install stitch-kit as a Codex plugin (codex plugin add) and trust its hooks. Details: docs/compaction-resilience.md.
Works with
The installer detects what you've got and wires up whatever that client supports. Not every agent takes skills, so here's the honest breakdown rather than a logo wall:
| Client | Stitch MCP | Agent | Skills |
|---|---|---|---|
| Claude Code | ✅ | ✅ | ✅ via plugin |
| Codex CLI | ✅ | ✅ | ✅ |
| OpenCode | ✅ | ✅ | ✅ |
| Crush | ✅ | — | ✅ |
| Cursor | ✅ | — | — |
| VS Code | ✅ | — | — |
| Gemini CLI | via extension | — | — |
Skills are the structured workflows — ideation, prompt engineering, ID-safe MCP wrappers, framework conversion. Agent is the Stitch-aware persona that knows the full toolset. MCP only means you get Stitch wired into the client and can drive it by hand, but none of the design intelligence — which is most of the point, so the top three are where this actually shines.
Gemini CLI handles MCP through its own extension system rather than a config file, so the installer points you at gemini extensions list instead of writing config for you.
Check what you've got with npx @booplex/stitch-kit status.
What actually happens when you use it
Without stitch-kit, your agent sends Stitch a half-baked prompt, gets confused by ID formats, generates one screen, hands you raw HTML, and calls it a day. With stitch-kit:
-
Think first —
stitch-ideatedoes something your coding agent literally cannot: design research. It fetches trends, analyzes competitor UIs, and proposes 3 distinct design directions with real hex colors, typography pairings, and mood descriptions. It's the design buddy your agent was missing. -
Generate smart — The orchestrator detects whether your request needs ideation or can go straight to generation (there's a specificity scoring system — hex colors and layout details skip ideation, vague requests trigger it). It engineers a structured prompt, sends the full PRD to Stitch, and batch-generates up to 10 screens in one call. If there are more, it auto-continues.
-
Iterate without starting over — Edit screens with text prompts, generate design variants, apply design systems across multiple screens for visual consistency. The agent knows which Stitch tool to reach for (and more importantly, which ID format each one expects — because apparently Google couldn't pick one).
-
Ship real code — Convert to production components with dark mode, TypeScript, design tokens, and ARIA. Not "here's some JSX, figure it out" — proper Server/Client component spli
// HOW IT'S BUILT
// FILES
2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.
skills/stitch-a11y/SKILL.md7.9 KBupstream ↗
--- name: stitch-a11y description: Audits Stitch-generated components for WCAG 2.1 AA accessibility issues and applies fixes — semantic HTML, ARIA attributes, keyboard navigation, focus management, and screen reader support. allowed-tools: - "Read" - "Write" - "Bash" --- # Stitch Accessibility Audit & Fix You are an accessibility engineer. You audit components generated from Stitch designs, identify WCAG 2.1 AA violations, and apply fixes directly to the source files. You don't just report issues — you fix them. **Run this skill AFTER** component generation. Components should be working before you audit them. ## When to use this skill Use this skill when: - Components are generated and working, and need accessibility review before shipping - The design has complex interactive patterns (modals, dropdowns, tab panels, accordions, carousels) - The user mentions "accessibility", "a11y", "WCAG", "screen reader", "keyboard navigation" - Preparing for a production launch or accessibility audit ## Step 1: Discover components to audit Read the project file structure to find all component files: ```bash # Next.js / React find src -name "*.tsx" -not -path "*/node_modules/*" # SvelteKit find src -name "*.svelte" -not -path "*/node_modules/*" ``` Read each component file before auditing. Focus your energy on interactive components — static content needs less attention than forms, navigation, modals, and dropdowns. ## Step 2: The audit — 6 categories Work through each category systematically for every component. ### Category 1: Semantic HTML **Violations to find:** - `<div>` or `<span>` used for navigation, headers, footers, main content, articles, sections - `<div onClick>` instead of `<button>` or `<a>` - Heading hierarchy out of order (h3 before h2, skipping levels) - Tables used for layout (not data) - Lists rendered as plain `<div>` elements **Fixes:** ```tsx // ❌ Wrong <div className="nav"> <div onClick={goHome}>Home</div> </div> // ✅ Fixed <nav aria-label="Main navigation"> <a href="/">Home</a> </nav> // ❌ Wrong — div button <div className="btn" onClick={handleClick}>Submit</div> // ✅ Fixed — real button <button type="button" onClick={handleClick}>Submit</button> // ❌ Wrong — visual list as divs <div className="menu"> <div>Item 1</div> <div>Item 2</div> </div> // ✅ Fixed <ul role="list"> <li>Item 1</li> <li>Item 2</li> </ul> ``` ### Category 2: ARIA attributes Only add ARIA where semantic HTML doesn't provide sufficient information. Remember: **no ARIA is better than bad ARIA.** **Violations to find:** - Icon-only buttons with no accessible name - Multiple `<nav>` landmarks with no `aria-label` - Multiple `<main>` elements - Status/live regions that update dynamically but have no `aria-live` - Interactive elements missing `aria-expanded`, `aria-haspopup`, `aria-controls` **Fixes:** ```tsx // Icon-only button <button aria-label="Close dialog" type="button"> <XIcon aria-hidden="true" /> </button> // Multiple nav regions <nav aria-label="Main navigation">...</nav> <nav aria-label="Breadcrumb">...</nav> <nav aria-label="Pagination">...</nav> // Dropdown toggle <button aria-expanded={isOpen} aria-haspopup="menu" aria-controls="user-menu" > Account </button> <ul id="user-menu" role="menu" hidden={!isOpen}> <li role="menuitem"><a href="/profile">Profile</a></li> </ul> // Live status region <div aria-live="polite" aria-atomic="true" className="sr-only"> {statusMessage} </div> ``` ### Category 3: Keyboard navigation Every interactive element must be operable by keyboard. Test this mental model: Tab through the page — can you reach and activate every action? **Violations to find:** - Custom interactive elements that don't receive Tab focus - `tabIndex={-1}` used where focus should be reachable - `tabIndex={1}` or higher (breaks natural tab order) - Modal open — focus not moved into modal - Modal closed — focus not returned to trigger - Dropdown closed with Escape — focus not returned **Fixes:** ```tsx // Focus management for modal — React import { useEffect, useRef } from 'react' export function Modal({ isOpen, onClose, children }: ModalProps) { const modalRef = useRef<HTMLDivElement>(null) const triggerRef = useRef<HTMLButtonElement>(null) useEffect(() => { if (isOpen) { // Move focus into modal when it opens modalRef.current?.focus() } }, [isOpen]) function handleClose() { onClose() // Return focus to trigger when modal closes triggerRef.current?.focus() } return ( <> <button ref={triggerRef} onClick={() => setIsOpen(true)}> Open Modal </button> {isOpen && ( <div ref={modalRef} role="dialog" aria-modal="true" aria-labelledby="modal-title" tabIndex={-1} /* Makes div focusable without entering tab order */ > <h2 id="modal-title">Modal Title</h2> {children} <button onClick={handleClose}>Close</button> </div> )} </> ) } // Keyboard handler for custom interactive elements <div role="button" tabIndex={0} onClick={handleAction} onKeyDown={(e) => { if (e.key === 'Enter' || e.key === ' ') { e.preventDefault() handleAction() } }} > Custom button behavior </div> ``` ```svelte <!-- Focus management in Svelte --> <script lang="ts"> let dialogEl = $state<HTMLDialogElement>() let triggerEl = $state<HTMLButtonElement>() let isOpen = $state(false) function openDialog() { isOpen = true // tick() ensures DOM is updated before focusing tick().then(() => dialogEl?.focus()) } function closeDialog() { isOpen = false triggerEl?.focus() // Return focus to trigger } </script> <button bind:this={triggerEl} onclick={openDialog}>Open</button> {#if isOpen} <dialog bind:this={dialogEl} tabindex="-1" aria-modal="true" onkeydown={(e) => e.key === 'Escape' && closeDialog()} > <button onclick={closeDialog}>Close</button> </dialog> {/if} ``` ### Category 4: Focus visibility Every interactive element must have a visible focus indicator. Never remove the focus ring without providing an equally visible replacement. **Violations to find:** - `outline: none` or `outline: 0` without a custom focus style - `.focus:outline-none` in Tailwind without `focus-visible:ring-*` - Focus styles that only appear on click, not keyboard focus **Fixes:** In CSS: ```css /* Never this */ *:focus { outline: none; } /* Always this — uses :focus-visible to show only on keyboard focus */ *:focus-visible { outline: 2px solid var(--color-primary); outline-offset: 2px; border-radius: 2px; } ``` In Tailwind: ```tsx // ❌ Wrong <button className="focus:outline-none"> // ✅ Fixed <button className="focus:outline-none focus-visible:ring-2 focus-visible:ring-primary focus-visible:ring-offset-2"> ``` ### Category 5: Images and media **Violations to find:** - `<img>` or `<Image>` without `alt` attribute - Meaningful images with `alt=""` - Decorative images with descriptive alt text (adds noise to screen readers) - Icons without accessible labels when used as interactive elements - Video without captions **Fixes:** ```tsx // Meaningful image <Image src="/hero.jpg" alt="Team members collaborating at a whiteboard in a modern office" /> // Decorative image — empty alt so screen readers skip it <Image src="/bg-pattern.svg" alt="" aria-hidden="true" /> // Icon in a button — hide icon, label the button <button aria-label="Delete item"> <TrashIcon aria-hidden="true" /> </button> // Icon with adjacent text — hide the icon (it's redundant) <button> <SaveIcon aria-hidden="true" /> <span>Save changes</span> </button> ``` ### Category 6: Color and contrast Check these without automated tools by reasoning about the design: **Violations to find:** - Muted text (`--color-text-muted`) on a muted background (`--color-surface`) — often fails 4.5:1 - Primary color on white atREADME.mdupstream ↗
Contents are not inlined in the catalog. Open the upstream file.
Plain-text copy, no login: /skill-bundles/gabelul-stitch-kit-skills-stitch-a11y.md