do-design-systemlisted

# Design System Skill Translate a visual moodboard into concrete, additive edits to a design system — `.pen` source, charter, downstream CSS tokens — and enforce the canonical organization of design files in the repo. Use when: - Someone shares a moodboard URL and asks you to tighten, professionalize, or re-theme an existing design system. - A new brand direction has mood imagery but no component spec. - You need to audit drift between the design system and the aesthetic the team is actually pointing at. - The repo's `docs/designs/` structure needs organizing (scattered `.pen` files, missing charter, flat inspiration folder). Do **not** use when the moodboard is abstract (vibes only, no reusable motifs) or when the existing system already matches — additive changes without a concrete signal waste effort. ## Scope This skill edits ONLY: - `docs/designs/design-system.pen` (reserved filename — the system source) - `docs/designs/charter.md` (when scaffolding) - `docs/designs/gap-audit.md` (append-only) - `docs/designs/inspiration/**` (adds images + per-pass README) - `docs/designs/README.md` and `docs/designs/product/README.md` (indexes) - Downstream CSS: brand tokens + Tailwind `@theme` bridge The skill MUST NOT touch: - Any `.pen` file other than `design-system.pen` (product/ wireframes, flows, mockups have different schemas and will be corrupted) - Application code, templates, or component implementations - Renames or deletions of existing tokens/components #