Score a visual artifact's implementation quality 0-100 against its composed StyleSeed rule set — category breakdown, evidence, and prioritized fixes.
Before this workflow, follow the once-per-session update preflight.
Design Score
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.
Deterministic check boundary
Functional completion is separate from this score. For declared user outcomes, the optional
artifact contract validation.functional.scenarios requires executed, passing tests; see
functional checks. Missing or skipped outcomes cannot be
offset by appearance points. Plain scoring does not run or attach functional evidence without
an authorized build/test task. An artifact with no functional contract is unverified for
functionality, even when its other gates pass.
For the executable contract and stable diagnostics, run the canonical checker:
