Why
Skins are the smallest visual extension surface in StyleSeed: one metadata file and one semantic-token stylesheet. An original community skin is a useful first visual contribution and creates a result the contributor can share.
Scope
Create one original, generically named skin at:
skins/<your-skin>/skin.json
skins/<your-skin>/theme.css
Start from skins/arc/ only as a file-shape reference. Choose a distinct but reusable visual posture—for example archival, botanical, high-contrast editorial, or technical monochrome.
Acceptance criteria
- The name is generic and does not use another company's trademark as the skin identity.
- No logos, copied product layouts, proprietary assets, or protected brand material.
- Required semantic surface, text, action, status, focus, radius, and shadow tokens are present for light and dark modes.
- Contrast remains readable and status colors keep stable meanings.
npm run build --prefix demo-pricing and git diff --check pass.
- Attach a current screenshot from the generated demo showing the new skin.
- Note any intentional limitation in the PR.
Boundary
A skin changes token material. If the proposal changes component selection, containment, or geometry, stop and open a brand-recipe proposal instead of expanding this PR.
Visual designers and first-time code contributors are welcome to claim this issue.
Why
Skins are the smallest visual extension surface in StyleSeed: one metadata file and one semantic-token stylesheet. An original community skin is a useful first visual contribution and creates a result the contributor can share.
Scope
Create one original, generically named skin at:
Start from
skins/arc/only as a file-shape reference. Choose a distinct but reusable visual posture—for example archival, botanical, high-contrast editorial, or technical monochrome.Acceptance criteria
npm run build --prefix demo-pricingandgit diff --checkpass.Boundary
A skin changes token material. If the proposal changes component selection, containment, or geometry, stop and open a brand-recipe proposal instead of expanding this PR.
Visual designers and first-time code contributors are welcome to claim this issue.