Best agent skills for Design Skill Collection
A curated design toolkit spanning art direction, visual artifacts, interface craft, and motion.
Curated Agent Skills · review method · Page updated
Start with one skill
Choose your agent to check the fit, then follow the steps below. Recommendations come from our editorial reviews.
Start here: Baoyu Design
Local visual prototypes and multi-format artifact work that needs a coherent project structure.
Why this skill? Tradeoffs and evidence
Editorial rationale: The useful distinction is between a visual medium and a web product. Baoyu routes a deck, email, diagram, or prototype into its own craft recipe while preserving imported design systems and project assets. The companion editors make this broader than a prompt for an attractive landing page.
Process tradeoff: Reviewed from source, not from generated artifacts. The entry skill depends on a substantial methodology and recipes, and its four companion artifact skills use different file formats and verification rules.
Compatibility: Editorial guidance lists Claude Code, Codex, Cursor. This does not establish executed testing.
Upstream support: No upstream support attestation recorded in this review.
Execution evidence: No executed test recorded for this starting point.
Choose your agent above to see the installation steps and starter request.
No recorded example is published for this starting point. Use the result checks to assess your own run.
Detailed comparison and alternatives
How to choose
Choose by deliverable. Baoyu is the broad local artifact studio; Huashu emphasizes comparing real directions before production. Impeccable supplies targeted product UI refinement, while Taste Skill supplies subject-led web composition and browser measurements. Emil’s existing prototype and animate skills complement these with component exploration and purposeful motion. These are alternatives and complements, not instructions to load every workflow together. New entries were reviewed from source on October 29, 2026; generated visual quality has not been tested here.
Baoyu Design
Creates HTML visual artifacts with medium-specific recipes, imported design systems, asset tracking, and browser preview.
Our take: The useful distinction is between a visual medium and a web product. Baoyu routes a deck, email, diagram, or prototype into its own craft recipe while preserving imported design systems and project assets. The companion editors make this broader than a prompt for an attractive landing page.
Claude Design Canvas
Creates editable artboards using canvas.json and Design Components in a local canvas editor.
Claude Slides
Creates editable decks with deck.json and HTML slides; the local editor presents and exports PDF, HTML, or PowerPoint.
Claude Design System
Authors editable tokens, brand books, component previews, fonts, and assets that canvases and decks can reuse.
Claude Dashboard
Builds file-backed dashboards whose figures trace to attached datasets through a Sources panel.
Huashu Design
Takes HTML visual deliverables through real assets, divergent direction selection, medium-specific production, and a local design history.
Our take: Huashu addresses a specific failure: three options that are merely the same layout recolored. Its six candidates, visible specimens, reference boards, and comparison checks make structural divergence inspectable. The appearance ledger also addresses repetition between projects instead of only banning yesterday’s fashionable palette.
Impeccable
Routes product UI work into focused build, critique, audit, refinement, and visual iteration playbooks with persistent product and design context.
Our take: Its strongest idea is that a landing page, an editor, and a reading surface should optimize for different visitor outcomes. Focused playbooks then make critique, typesetting, layout, and hardening independently useful. Current upstream packages these as commands inside one skill; counting each command as a separate skill would misrepresent the install.
Taste Skill / design-taste-frontend
Develops subject-specific compositions and imagery, then checks source and rendered pages through linting, viewport measurements, screenshots, and critique.
Our take: Taste Skill makes an aesthetic recommendation falsifiable in useful ways: the direction comes from a library, imagery has sources, and a real browser measures what shipped. Separating a page that persuades from a screen someone works in is a meaningful correction to one-size-fits-all anti-template advice.
Emil Design Engineering
Encodes Emil’s core taste for polished interfaces, restrained motion, component details, and design decisions that compound.
Our take: Emil Design Engineering is the broad taste layer behind the collection. Its value lies in turning invisible interface quality into concrete choices—subtle borders, shadows, typography, component behavior, and restrained motion—without pretending polish comes from a single visual style.
Prototype
Builds genuinely different UI variants behind a visual picker so design direction can be compared in context.
Our take: Prototype addresses a common agent failure: converging on the first plausible UI and presenting cosmetic variants as exploration. By requiring materially different directions in a live picker, it turns subjective design choice into a fast comparison rather than a long prompt negotiation.
Animate
Builds purposeful web animation by choosing whether to animate, then selecting the right tool, properties, timing, interruption, and exit behavior.
Our take: Animate is the collection’s strongest implementation skill because it makes motion a decision chain instead of a decorative afterthought. Purpose, frequency, tool choice, properties, timing, interruption, and exit behavior are resolved before code, giving agents a much better chance of producing motion that feels intentional.