사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/bitjaru/styleseed --skill ss-reference시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
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.
