ss-component

# UI Component Generator ## Registry-first artifact boundary If either `.styleseed/project.json` or `.styleseed/artifacts/index.json` exists, require a complete, valid registry. Resolve the requested artifact ID before writing a component; ask for scope if it is ambiguous. Never fall back to the global legacy bundle, create `STYLESEED.md`, or restart setup because a registry is incomplete, invalid, or has no compiled output. Locate the installed `ss-resolve` skill directory (shown as `<ss-resolve>` below), then run this read-only check from the target project root with the active agent (`codex`, `claude`, etc.): ```sh node "<ss-resolve>/scripts/resolve-context.mjs" --project-root . --artifact <artifact-id> --agent <agent> --check ``` For a valid registry with missing or stale compiled output, run the same command without `--check`, then check again. Stop on invalid configuration or installation errors; do not change approved selections to make the check pass. After success, read only the selected `.styleseed/bundles/<artifact-id>.md` and `.styleseed/manifests/<artifact-id>.json` as the compiled method and provenance. A shared component affecting multiple artifacts requires resolving and checking each affected artifact separately, not merging their bundles. Legacy projects use the following path only when neither registry file exists. Preserve `STYLESEED.md`; if it is missing, use setup before component code. ```sh node "<ss-resolve>/scripts/resolve-context.mjs" --proje...