ss-studio

# Build a directed interactive concept ## 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. Run the full Studio pipeline. Do not reduce it to a moodboard, a static image, or a set of arbitrary motion effects. ## Start the run Read `STUDIO-PIPELINE.md`, `PRODUCT-PRINCIPLES.md`, and the resolved project rules first. If the project has no valid `STYLESEED.md`, run setup and resolve before Studio. Initialize a durable run: ```bash node <skill-dir>/scripts/studio-run.mjs init \ --project-root . \ --artifact <artifact-id> \ --name "<project or concept>" \ --brief "<product job and desired interaction>" \ --surface mobile-app \ --platform web ``` The command prints the run directory under `.styleseed/studio/`. Use the artifact schemas in `references/artifact-contract.md`. Use `references/provider-adapters.md` only when media generation or recording is required. If the project uses the artifact registry, `--artifact` is required and the run binds the current artifact manifest and method hash at init time. ## 1. Scout by role Classify supplied and discovered references as `structure`, `navigation`, `signature`, `mot...