How to use
- Copy the installation command and review the source package before installing it in your own agent environment.
- Check the source document for required tools, credentials and supported hosts.
- Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/bitjaru/styleseed --skill ss-referenceBefore you start
- Installation does not include a model subscription, API allowance or permission to access your files.
- Repository stars and installation counts describe activity, not an independent quality or security test.
Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.
Compile references into a design grammar
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.
Do not merely imitate the supplied screen. Read PRODUCT-PRINCIPLES.md, RULESETS.md, ADAPTERS.md, and REFERENCE-COMPILER.md, then execute the compiler pipeline in full.
Workflow
- Ingest every supplied reference and assign evidence IDs (
R1,R2, ...). If a URL can be
rendered, capture it. If an image cannot be seen, stop claiming visual analysis for it.
- Separate references by surface adapter and job. Do not merge a marketing homepage with an app
dashboard unless the user explicitly wants both languages connected.
- Observe and measure the twelve axes. Every rule cites evidence IDs and a confidence level.
- Resolve contradictions instead of averaging them. Explain any material choice briefly.
- Choose the nearest built-in fallback grammar and adapter, then compile the project artifacts required by
REFERENCE-COMPILER.md under .styleseed/rulesets/<slug>/.
- Select
reference:<slug>in the chosen artifact's project-owned configuration for registry
projects; only when neither registry file exists, update the legacy STYLESEED.md. Preserve bounded brand choices. A partial or invalid registry is an error, not a fallback.
- Validate transfer: apply the grammar to one representative screen not present in the source
set, run /ss-score, then /ss-verify if renderable. Within the authorized validation scope, fix and repeat until passing or three correction passes per gate, counting delegated passes. Do not reset the budget by switching skills; report actual scores and unresolved failures.
- Report what was learned, what remains low-confidence, where the artifacts live, and the
validation result.
Rules
- Visible evidence before adjectives. “Calm” is not a rule; the spacing, type, color, hierarchy,
and motion decisions that create calm are rules.
- Never copy protected assets, brand marks, or prose.
- One reference produces a provisional grammar. Say so and keep confidence low where warranted.
- The generated grammar is project-local. Do not edit
RULESETS.mdor publish it as built-in. - Core invariants and accessibility remain non-negotiable.
