ss-reference

Name: ss-reference
Author: bitjaru

810stars73forks

How to install ss-reference?

bitjaru/styleseed/ss-reference

$npx -y skills add bitjaru/styleseed --skill ss-reference

Installs into the current project.

Summary

Compile screenshots, URLs, Figma exports, or an existing UI into a project-local StyleSeed output grammar with evidence, tokens, confidence, anti-patterns, and a validation screen. Use when the user supplies a design reference that StyleSeed does not already model.

Files · 1

View on GitHub

SKILL.md

1	# Compile references into a design grammar
2
3	Do not merely imitate the supplied screen. Read `PRODUCT-PRINCIPLES.md`, `RULESETS.md`,
4	`ADAPTERS.md`, and `REFERENCE-COMPILER.md`, then execute the compiler pipeline in full.
5
6	## Workflow
7
8	1. Ingest every supplied reference and assign evidence IDs (`R1`, `R2`, ...). If a URL can be
9	rendered, capture it. If an image cannot be seen, stop claiming visual analysis for it.
10	2. Separate references by surface adapter and job. Do not merge a marketing homepage with an app
11	dashboard unless the user explicitly wants both languages connected.
12	3. Observe and measure the twelve axes. Every rule cites evidence IDs and a confidence level.
13	4. Resolve contradictions instead of averaging them. Explain any material choice briefly.
14	5. Choose the nearest built-in fallback grammar and adapter, then compile the project artifacts required by
15	`REFERENCE-COMPILER.md` under `.styleseed/rulesets/<slug>/`.
16	6. Update `STYLESEED.md` to select `reference:<slug>` while preserving bounded brand choices.
17	7. Validate transfer: apply the grammar to one representative screen not present in the source
18	set, run `/ss-score`, then `/ss-verify` if renderable. Fix and repeat to the gate floor.
19	8. Report what was learned, what remains low-confidence, where the artifacts live, and the
20	validation result.
21
22	## Rules
23
24	- Visible evidence before adjectives. “Calm” is not a rule; the spacing, type, color, hierarchy,
25	and motion decisions that create calm are rules.
26	- Never copy protected assets, brand marks, or prose.
27	- One reference produces a provisional grammar. Say so and keep confidence low where warranted.
28	- The generated grammar is project-local. Do not edit `RULESETS.md` or publish it as built-in.
29	- Core invariants and accessibility remain non-negotiable.

People who liked this also viewed

6 picks

Type

ss-reference

810stars73forks

View on GitHub

How to install ss-reference?

bitjaru/styleseed/ss-reference

$npx -y skills add bitjaru/styleseed --skill ss-reference

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Compile references into a design grammar
2
3	Do not merely imitate the supplied screen. Read `PRODUCT-PRINCIPLES.md`, `RULESETS.md`,
4	`ADAPTERS.md`, and `REFERENCE-COMPILER.md`, then execute the compiler pipeline in full.
5
6	## Workflow
7
8	1. Ingest every supplied reference and assign evidence IDs (`R1`, `R2`, ...). If a URL can be
9	rendered, capture it. If an image cannot be seen, stop claiming visual analysis for it.
10	2. Separate references by surface adapter and job. Do not merge a marketing homepage with an app
11	dashboard unless the user explicitly wants both languages connected.
12	3. Observe and measure the twelve axes. Every rule cites evidence IDs and a confidence level.
13	4. Resolve contradictions instead of averaging them. Explain any material choice briefly.
14	5. Choose the nearest built-in fallback grammar and adapter, then compile the project artifacts required by
15	`REFERENCE-COMPILER.md` under `.styleseed/rulesets/<slug>/`.
16	6. Update `STYLESEED.md` to select `reference:<slug>` while preserving bounded brand choices.
17	7. Validate transfer: apply the grammar to one representative screen not present in the source
18	set, run `/ss-score`, then `/ss-verify` if renderable. Fix and repeat to the gate floor.
19	8. Report what was learned, what remains low-confidence, where the artifacts live, and the
20	validation result.
21
22	## Rules
23
24	- Visible evidence before adjectives. “Calm” is not a rule; the spacing, type, color, hierarchy,
25	and motion decisions that create calm are rules.
26	- Never copy protected assets, brand marks, or prose.
27	- One reference produces a provisional grammar. Say so and keep confidence low where warranted.
28	- The generated grammar is project-local. Do not edit `RULESETS.md` or publish it as built-in.
29	- Core invariants and accessibility remain non-negotiable.

People who liked this also viewed

6 picks

Type