Skip to content

v2.4.0 — Consistent application (plan-mode setup, design lock, rule-gap fixes)

Choose a tag to compare

@bitjaru bitjaru released this 23 Jun 01:47

Theme: consistent application. Real usage showed the one-paste prompt could still produce mediocre UI (random colors, no key color, different every run). Root cause: consistency comes from constraints, and the paste path is the least-constrained. This release raises the floor of the default path — validated by dogfooding the engine end-to-end.

Added

  • Quick Setup protocol — agents work in plan mode, lock a key color + motion seed with the user before building, then self-check.
  • Design Lock — agents write & obey a project-root STYLESEED.md (skin, accent, radius, motion) every prompt, so decisions persist instead of drifting. /ss-setup writes it.
  • Troubleshooting guide (README) + FAQ entries for "applied StyleSeed but it still looks bad / results vary."

Changed

  • Stronger canonical paste-prompt — points to llms-full.txt (the full rules, not the summary) and bakes in plan-mode + key-color lock + coherence self-check.

Rules (gaps closed from real failures + dogfooding)

  • No emoji as UI icons — they inject many uncontrolled hues; use one line-icon set in currentColor.
  • Status color = severity, not decoration — fixed a rule that told agents to "vary status colors for visual interest" (the cause of noisy rainbow lists). Normal/OK/"보통" rows are neutral grey; color marks only the minority needing attention; same value → same color.
  • Quality/score scales (good→bad, e.g. air-quality/health/life-index) now have guidance — neutral+exception or one sequential ramp, never scattered process hues.
  • Favorite/saved/rating affordances convey on/off by fill (filled accent / outline grey), not gold/red.
  • Enforced in /ss-review, /ss-score, the design-review skill, and .cursorrules.

Full notes: CHANGELOG.md · Update: run /ss-update or npx skills add bitjaru/styleseed