Build, improve, or inspect UI with StyleSeed. Preserves project design choices and routes setup, layout, tokens, review, rendered verification, and updates through one entry point.
StyleSeed
Use the user's goal to choose one first workflow below. This is the only registered core
skill; the 22 workflows and their executable dependencies ship inside this directory.
Read only the selected workflow, then references needed for that task.
Registry-first artifact boundary
When .styleseed/project.json and .styleseed/artifacts/index.json exist, resolve the requested
artifact first. Read its .styleseed/bundles/<artifact-id>.md and manifest. A partial or invalid
registry is an error; never fall back to the global legacy bundle. Legacy projects may use
.styleseed/effective-rules.md only when no registry exists.
Before the first workflow in a project/task session, follow the
update preflight.
Working contract
- Preserve approved project design choices. Support expert judgment; a score is not human acceptance.
- Resolve the current artifact first. For multiple plausible artifacts, ask one bounded clarification question.
- Never fan out to run every workflow. Choose exactly one first workflow; it may call the required gates.
- Honor the user's authorized scope. Audit, score, verify, and status requests do not authorize edits.
Workflow metadata records the intended tool/scope boundary even though it is not host registration metadata. - Paths in workflow files are relative to those files. Resolve installed scripts from this skill's
actual directory, never assume a particular agent folder or download a missing sibling skill. - In older instructions,
/ss-build,$ss-build, and otherss-*names mean the corresponding
internal workflow. Readworkflows/<name>/WORKFLOW.md; do not invoke an unregistered skill.
Users may sayStyleSeed build,$styleseed build, or the old workflow name in natural language. - Learning is an optional extension, not part of the core install. Only for explicit learning capture,
use separately installedss-learn; if absent, report that dependency and never auto-install it.
Choose exactly one first workflow
| Request | Read |
|---|---|
| Build or redesign a screen, page, or component | build |
| First setup or missing design lock | setup |
| Explore creative directions; direction not yet selected | studio |
| Use screenshot, URL, Figma export, or existing UI as a reference | reference |
| What is wrong with this screen; UX critique | audit |
| Review implementation against project design rules | review |
| Score implementation or run code/evidence gates | score |
| Inspect rendered output, screenshot, or spacing in pixels | verify |
| Change spacing/density or another single design axis | dial |
| Apply an aesthetic profile | restyle |
| Brand color, semantic palette, or design tokens | tokens |
| Named animation or motion treatment | motion |
| Specifically scaffold a page | page |
| Specifically generate a reusable component | component |
| Compose existing primitives into a UI pattern | pattern |
| Accessibility audit and requested fixes | a11y |
| Quick design lint | lint |
| Navigation and user flows | flow |
| UX microcopy | copy |
| Loading, empty, success, or error states | feedback |
| Update installation or consolidate old skill entries | update |
| Compile rules, inspect local install/bundle/evidence health | resolve |
For status-only requests use resolve's read-only scripts/styleseed-doctor.mjs; do not update,
recompile, or visually inspect instead. For vague requests infer the first step from project state
and the user's goal; ask only when an unresolved choice materially changes the work.
