⏳ 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 expert design judgmentrepeatable by coding agents.
StyleSeed turns recorded design decisions into project-local rules and implementation workflows. 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.
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.
You do not need to memorize 23 skill names. The styleseed router selects the first workflow.
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.
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 |
| All-even grid of same-weight centered cards | the #1 machine-composed tell: no focal point |
| 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 universal aesthetic.
Judgment with implementation context — decisions, applicability, and evidence, not just palettes ·
Right grammar for the result — consumer service, operations, technical, editorial,
commerce, institutional, marketing, or sequential story ·
Real morphology choices — nine brand recipes change structure and component selection,
not just palette ·
Generative palette engine — any key color becomes OKLCH ramps, context-fit surfaces,
a scored companion, semantic roles, contrast evidence, CSS tokens, and media anchors; eight
recipes remain maintained product postures ·
Studio pipeline — three directions, human selection, interaction scenes, image/video jobs,
working prototype, and a prototype-first reel ·
References become rules — /ss-reference compiles screenshots, URLs, Figma, or an existing
UI into an evidence-backed project grammar ·
Only the context you need — /ss-resolve compiles the chosen me
// HOW IT'S BUILT
KEY FILES