Repository navigation
v0.1.4 — factory-design skill and docs-sync CI
Outcome: v0.1.4 — factory-design skill and docs-sync CI
Why: Codify the semantic-token design discipline as its own skill so every UI build draws from the same vocabulary; prevent README roster drift from recurring by checking skill / agent / command listings against disk on every PR.
Changes:
feat:
- 6fa7084 feat: add factory-design skill and docs-sync CI
Highlights (refine as you like):
- New skill
factory-design— token vocabulary (name intent, not palette position), CSS variables bridged into Tailwind, dark/light as a single variable swap, single vs two-layer token systems, what gets a token vs stays a utility, primitives as token consumers, the 3-uses promote-to-primitive rule, vocabulary-sprawl failure mode, and a migration playbook from daisyUI / Bootstrap / Material. - New CI check
docs-sync— runs on PRs touchingskills/,agents/,commands/, orREADME.md; fails when disk and README roster disagree in either direction. Surfaces drift inline via GitHub error annotations. factory-frontendsemantic-colors section now delegates tofactory-designfor the deeper discipline; CRUD-specific tone guidance stays local.frontend-engineeragent reading list addsfactory-design; no-hex-literal and no-dark:-variant rules added to the conventions checklist.factory-pitfallsgains a Design system block — eight entries (palette-position token names, hex in components, sprinkleddark:variants, spacing-token sprawl, primitive-layer leakage, "lift it later" components, token-sprawl, half-replaced theme libraries).- README skill table now lists
factory-voice,factory-design,factory-testing,factory-ci(previously missing); slash-commands list adds/release; local-clone example pin bumped tov0.1.3.