Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →bitjaru/ss-build
Build a screen with StyleSeed's composed design method — choose or compile an output grammar, apply domain/page/profile/lock constraints, then run the code and pixel gates before presenting.
Passed 14 of 18 test cases with the skill, and 7 of 18 without it.
and 5 more in the full report
8 fixed9 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
When applying pattern components from a bundled brand recipe to our top-level component element, what DOM attribute must be attached to mark the recipe ID?
| Checked | Without skill | With skill |
|---|---|---|
| Sets data-styleseed-recipe attribute on the artifact root element | Missed | Passed |
The instructions your model reads when the skill loads.
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.
The build method is the product. Score and screenshots are auxiliary evidence, not the source of design judgment.
If STYLESEED.md does not exist, run /ss-setup and write it before UI code. If the user
supplied a visual reference that the selected built-in grammar does not capture, run
/ss-reference first. Never reduce an unfamiliar reference to a palette swap.
Then invoke /ss-resolve (Claude Code) or $ss-resolve (Codex), or run its bundled
scripts/resolve-context.mjs --project-root . --from-lock STYLESEED.md --agent <agent>.
Read .styleseed/effective-rules.md and preserve .styleseed/manifest.json as the provenance
record. Do not load llms-full.txt after resolution succeeds.
The compiled bundle already composes the authority order: core invariants → selected grammar → surface adapter → domain/page → brand recipe → optional profile → bounded lock → craft baseline. Use the manifest selection and source hashes to detect drift. Open a full source document only when the bundle points to a genuine ambiguity; do not reassemble the handbook ad hoc.
Before code, state the effective rule set in one line, for example:
operations-console × SaaS × dashboard × enterprise-workbench × swiss × locked brand tokens
Resolve conflicts by authority. A profile or lock cannot waive task fitness, coherence, or accessibility.
test cases passed, vs 7 / 18 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.