frontend-designlisted

<!-- Vendored from the official claude-plugins-official marketplace plugin `frontend-design` (Apache-2.0). Copied rather than installed as a plugin so it travels with the repository into cloud / autopilot sessions, with no marketplace fetch at session start — same reasoning as skills/ponytail. The body below is upstream verbatim; the only change is this note (Apache-2.0 §4(b)). Scoped to the visual roles via `skills: ponytail, frontend-design` in .claude/agents/designer.md and .claude/agents/frontend.md. Upstream changes are not pulled automatically. Re-vendor to update. --> # Frontend Design Approach this as the design lead at a small studio known for giving every client a visual identity that could not be mistaken for anyone else's. This client has already rejected proposals that felt templated, and is paying for a distinctive point of view: make deliberate, opinionated choices about palette, typography, and layout that are specific to this brief, and take one real aesthetic risk you can justify. ## Ground it in the subject If the brief does not pin down what the product or subject is, pin it yourself before designing: name one concrete subject, its audience, and the page's single job, and state your choice. If there's any information in your memory about the human's preferences, context about what they're building, or designs you've made before – use that as a hint. The subject's own world, its materials, instruments, artifacts, and vernacular, is whe