⏳ This skill is pending AI review.
Scores will appear once the review pipeline completes.
ss-a11y
Audit a component or page for accessibility issues and fix them
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
StyleSeed
Make AI coding agents keep your design systemacross screens, sessions, and teammates.
You choose the design decisions. StyleSeed compiles them into the rules an agent reads before each screen, then checks the rendered result. Support experts, not replace them with a collection of tastes. Open source, for Claude Code · Codex · Cursor.
Same product. Same prompt. Only the rules changed.
Measured on 120 rendered benchmark cells: the enforced gate improved both Codex and Claude Code by +5.3 points. Raw rules alone were inconsistent (Codex +1.6, Claude Code −3.7), which is why StyleSeed ships a render → score → revise loop—not a prompt dump. Read BENCH-V1 and inspect the raw evidence →
Easy Start (30 seconds)
Our goal is repeatable application of expert judgment, not a claim of expert-level output today. The engine compiles selected rules, preserves project choices, and supports code and rendered checks. A score does not replace human design acceptance. Product principles · Quality-first roadmap
1. Open a terminal in your project folder and run this command. Requires Node.js/npm.
Already installed? Update and consolidate your existing skill list. One request covers the same install scope, verified backup, and revision checks.
npx -y skills add bitjaru/styleseed -a codex claude-code -y --copy
Installs the core skills for Codex and Claude Code together, with no agent, skill, or install-mode menus. It copies the skills into this project. It does not install globally or change other projects.
2. Send one message to your agent. Start a fresh session if the skills do not appear.
- Codex:
$styleseed Help improve this screen. Preserve our existing design choices and show me what needs a decision. - Claude Code:
/styleseed Help improve this screen. Preserve our existing design choices and show me what needs a decision.
Only styleseed is registered. It selects the needed internal workflow from your request.
Choose unresolved design decisions together, then inspect the actual rendered result.
- Codex only:
npx -y skills add bitjaru/styleseed -a codex -y --copy - Claude Code only:
npx -y skills add bitjaru/styleseed -a claude-code -y --copy - Cursor or another agent:
npx skills add bitjaru/styleseed→ your agent → Project → Copy. - In the interactive list, Codex is already included under Universal. Do not look for it again under Additional agents.
-yskips installer questions; it does not bypass your coding agent's tool permissions.
Claude Code guide · Codex guide · See examples · Need help?
Evaluating the repository?
Use the three-minute verification path to test a clean public install before trusting the README. The source-level evaluator quickstart then connects that install to the published release manifest, Windows PowerShell evidence, CI, SBOM, benchmark boundary, and production build.
Want a first PR? Fix a doc, add a regression fixture, improve a skin, or claim a
good first issue. Small docs and test fixes need no proposal. See the 15-minute contribution path.
For a fixed evaluation version, use the v5.0.0 release archive and its checksums. The default bitjaru/styleseed command follows mutable main.
Upgrading an existing 23-skill install
Reinstall through the same channel. Then ask StyleSeed, consolidate my old skill entries.
The update workflow verifies the new unified payload and archives only unmodified old ss-*
directories outside skill discovery; modified copies remain for review. Restart the agent session.
Use $styleseed build / /styleseed build instead of the former $ss-build / /ss-build
registrations. All 22 workflows remain bundled; selecting only styleseed is now sufficient.
What the current rules check
StyleSeed ships 74 craft rules and a 0–100 scored gate that tells an installed agent to revise screens below 80 before presentation. Checks must be interpreted through the selected grammar and project contract, not as universal taste. The workflow must actually be invoked; a markdown file alone cannot block delivery, and 80 points is not expert approval.
| Check | Why |
|---|---|
| Unselected default accent | require an intentional, recorded color role |
| Emoji as UI icons 🚗 🧺 ⭐ | inject random colors, render differently per OS |
| The icon-in-a-chip above every feature card | gen-1 AI tell — decoration pretending to be information |
| Same-weight cards that hide the current priority | the #1 machine-composed tell; truly equivalent options may share weight |
| Accidental flat-black backgrounds | use the selected grammar's surface model; explicit supported exceptions differ |
| Type sizes outside the selected scale | prevent unintentional hierarchy drift |
| Hardcoded hex in components | tokens only — otherwise the lock can't hold across screens |
Banning the defaults isn't enough — agents converge on new uniforms once the old ones are blocked. That's why the rules come with an enforced score-then-fix loop, not a checklist. What happens after install ↓
One component. Three token skins. Same chat UI morphing across Toss · Raycast · Arc-inspired token sets. A skin changes color and type material; a StyleSeed brand recipe changes the actual geometry, containment, controls, collections, density, and motion.
Skins are inspired-by token sets, not recreations. Compare the nine structural recipes →
**Expert decisions become repeatable instructions — not one univer
// 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/ss-a11y/SKILL.md3.6 KBupstream ↗
--- name: ss-a11y description: Audit a component or page for accessibility issues and fix them argument-hint: "[file-path]" allowed-tools: Read, Write, Edit, Grep, Glob --- Before this workflow, follow the once-per-session [update preflight](../ss-update/references/update-preflight.md). # Accessibility Audit ## Registry-first artifact boundary When `.styleseed/project.json` and `.styleseed/artifacts/index.json` exist, resolve the requested artifact ID first, then read only `.styleseed/bundles/<artifact-id>.md` and `.styleseed/manifests/<artifact-id>.json`. Never fall back to the global legacy bundle for a registry project. Legacy projects may use `.styleseed/effective-rules.md` only when no registry exists. ## When NOT to use - For general design system compliance review → use `/ss-review` - For Nielsen UX heuristics → use `/ss-audit` - For non-StyleSeed code (no `data-slot`, no semantic tokens) — assumes StyleSeed conventions - For runtime testing — this is a static code audit, not a screen-reader simulation Target: **$ARGUMENTS** ## Audit Criteria ### WCAG 2.2 AA Compliance #### 1. Perceivable - **Color contrast**: Text must meet 4.5:1 (normal) or 3:1 (large/bold text) - Check `text-muted-foreground` (#717182) on `bg-background` (#FFFFFF) = 4.6:1 (passes) - Check `text-brand` on white (verify contrast with your skin's brand color) - Flag any custom colors that don't meet ratio - **Non-text contrast**: UI controls/graphics must meet 3:1 - **Text alternatives**: All `<img>` need `alt`, icons need `aria-label` when meaningful - **Color independence**: Don't convey info by color alone (add icons/text) #### 2. Operable - **Touch targets**: Minimum 44x44px (`min-h-11 min-w-11`) on touch surfaces - Flag undersized touch hit areas, not approved pointer-first desktop controls merely for being 36–40px tall - Pointer-first controls follow the resolved contract; preserve keyboard access and applicable accessibility floors - Icon buttons need an explicit hit area appropriate to the input mode - **Keyboard navigation**: All interactive elements must be keyboard-accessible - Tab order should be logical - `focus-visible:ring-2 focus-visible:ring-ring focus-visible:ring-offset-2` - **Motion**: Animations must respect `prefers-reduced-motion` ```css @media (prefers-reduced-motion: reduce) { *, *::before, *::after { animation-duration: 0.01ms !important; transition-duration: 0.01ms !important; } } ``` #### 3. Understandable - **Labels**: Form inputs must have visible labels or `aria-label` - **Error messages**: Form errors must be programmatically associated (`aria-describedby`) - **Language**: `<html lang="en">` (or appropriate language code for your project) #### 4. Robust - **Semantic HTML**: Use appropriate elements (`<button>`, `<nav>`, `<main>`, `<header>`) - **ARIA**: Use Radix UI components (they handle ARIA automatically) - **Roles**: Custom interactive elements need proper `role` attributes ## Design System Token Reference | Token | Minimum Contrast | Note | |-------|-----------------|------| | `--foreground` | 7:1+ | Body text — verify with your skin | | `--muted-foreground` | 4.5:1+ | Secondary text — verify with your skin | | `--brand` | 4.5:1+ | Accent — verify with your skin's brand color | | `--destructive` | 4.5:1+ | Error — verify with your skin | | `--success` | 3:1+ | Large text/icons only — verify with your skin | | `--warning` | 4.5:1+ | Warning text — some skins need a darker variant | ## Output 1. **Issues found**: List with severity (Critical/Major/Minor) 2. **Auto-fixes**: Apply fixes directly where possible 3. **Manual review needed**: Flag items that need human judgmentREADME.mdupstream ↗
Contents are not inlined in the catalog. Open the upstream file.
Plain-text copy, no login: /skill-bundles/bitjaru-styleseed-skills-ss-a11y.md