StyleSeed — скилл

---
name: styleseed
description: Route a StyleSeed request to exactly one first workflow after resolving the current artifact boundary. Use when the user asks generally for StyleSeed help rather than invoking one specific ss-* skill.
argument-hint: "[request or goal]"
allowed-tools: Read, Grep, Glob, Bash
---

# StyleSeed router
## 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.

This router chooses exactly one first workflow. It is the primary entry skill when a user asks for
StyleSeed help in general terms.

## First principles

- Help coding agents repeat expert design decisions, not replace expert authority with presets.
  Preserve approved project choices; identify unsupported or unresolved choices before routing
  to work that would change them. A score is not human acceptance.
- Resolve the current artifact first when `.styleseed/project.json` and `.styleseed/artifacts/index.json`
  exist.
- Never fan out to “run every StyleSeed skill.”
- Never copy the full design handbook into this router. Route to the maintained skill that already
  owns the workflow.
- Learning is an optional extension, not part of the core install. Only after an explicit capture
  request such as “remember this lesson” may the router check whether `ss-learn` is separately
  installed. If absent, state the dependency precisely; never auto-install it.
- If the request is ambiguous, ask one bounded clarification question that decides the first workflow.

## One-workflow routing table

Choose exactly one first workflow:

- `ss-setup` for first-time method setup, missing lock/setup, or “set up StyleSeed for this project.”
- `ss-build` for implementing or redesigning a concrete screen/component/page when the direction is already known.
- `ss-reference` for compiling supplied references that are not already represented by a maintained grammar.
- `ss-studio` for creative direction, exploration, concept generation, or multi-direction concept work.
- `ss-audit` for critique, heuristic review, UX issue finding, or “what is wrong with this screen.”