--- name: taste-studio description: "Use Taste Skill for art direction, distinctive frontend composition, redesigns, typography and page or dashboard design. Load the complete pinned Taste scripts, references and libraries while preserving the selected Starlight brand pack." --- # Taste studio Read `../../vendor/taste/SKILL.md`. Resolve its `` to `/vendor/taste`; retain the user's project as the working directory. Read its page or app-screen route according to what the visitor does. Inventory subject-specific assets, facts, constraints and authentic proof before choosing composition. Use the bundled draw pipeline to compare directions, then select one against the real brief. Use `references/` and `library/` progressively; the full source closure is bundled, not only the entry prompt. Invoke draws through `node /scripts/taste-draw.mjs ` from the owning project. This wrapper verifies source bytes and pins `TASTE_SKILL_HISTORY` to `/.taste-skill/history.json`. The upstream draw otherwise writes a user-wide history file, which must not mix client subjects. The upstream no-ornament house style is a diagnostic baseline. The explicit brand pack and requested direction override generic bans. Retain purposeful states, named controls, operational density and accessible navigation. Never replace useful product information with empty whitespace to satisfy a detector. Run scripts only after the source-integrity check. Node 22+ and an installed Chromium-family browser are upstream prerequisites. `assets.mjs` uses network access; fetching a photograph does not establish publication rights. Keep generated evidence under the owning project, not inside the installed plugin. Use `scripts/inspect.mjs` and actual rendered captures where the runtime supports them. Inspect desktop, mobile, keyboard focus and reduced motion. When the browser is unavailable, continue source-level improvements and mark rendered verification incomplete. Finish with the chosen direction, concrete changes, before/after evidence and unresolved checks.