design-taste-frontend

Infer design briefs and deliver frontend design guidance with accessibility checks.

99|6|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/vvedantb/eva --skill design-taste-frontend-vvedantb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-taste-frontend
Source: https://github.com/vvedantb/eva/tree/main/.agents/skills/design-taste-frontend
Command: npx skills add https://github.com/vvedantb/eva --skill design-taste-frontend-vvedantb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Anti-slop frontend design guidance to ensure landing pages, portfolios, and redesigns avoid templated aesthetics; reads briefs to infer right direction and applies audit-first checks with real design systems when applicable.

Core Features & Use Cases

  • Infers design direction from briefs to avoid canned UI.
  • Delivers actionable frontend design guidance for landing pages, portfolios, and redesigns.
  • Provides audit-ready constraints (accessibility, brand consistency, design-system alignment) across typical projects.

Quick Start

Ask the agent to infer the design brief and ship an anti-slop frontend interface.

Frequently Asked Questions about design-taste-frontend

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I avoid templated UI aesthetics when designing a landing page?

Anti-slop frontend design prevents templated aesthetics by inferring the correct design direction from your brief and applying audit-first checks for accessibility and brand consistency, ensuring non-canned, premium interfaces.

Can I use this approach to redesign an existing portfolio interface?

Yes, redesigning an existing portfolio interface benefits from anti-slop frontend guidance by applying design-system alignment and accessibility checks to deliver non-templated, premium interfaces.

What's the best way to align a new frontend interface with an existing design system?

Aligning a new frontend interface with an existing design system requires applying audit-first checks for system coherence and accessibility, interpreting the brief to ensure real-world usability without templated aesthetics.

Does anti-slop frontend design guidance include accessibility checks?

Anti-slop frontend design guidance includes audit-ready accessibility checks, brand consistency, and design-system alignment to ensure real-world usability across landing pages and portfolios.

Why does my landing page look like a generic template despite using a design system?

A landing page looks like a generic template when the design brief is not properly inferred to direct the design. Applying anti-slop frontend checks ensures system coherence and avoids canned UI patterns.