ss-build
Build a screen with StyleSeed's composed design method — choose or compile an output grammar, apply a brand recipe plus domain/page/profile/lock constraints, then run the code and pixel gates before presenting.
Profile →npx skills add bitjaru/styleseed --skill ss-build --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Build with the composed StyleSeed method The build method is the product. Score and screenshots are auxiliary evidence, not the source of design judgment. ## Step 1 — Establish the rule set before code 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. ## Step 2 — Compose, do not improvise 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
- Step 1 — Establish the rule set before code
- Step 2 — Compose, do not improvise
- Step 3 — Build with design judgment
- Step 4 — Code gate loop
- Step 5 — Pixel gate loop
- Step 6 — Present with proof
- Rules
What does the ss-build skill do?
Build a screen with StyleSeed's composed design method — choose or compile an output grammar, apply a brand recipe plus domain/page/profile/lock constraints, then run the code and pixel gates before presenting.
How do I install it?
Run `npx skills add bitjaru/styleseed --skill ss-build --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From bitjaru/styleseed, a repository with 867 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.