frontend-design

Guides visual and interaction design decisions for frontend pages and components.

Updated Sep 20, 2026
One-click install
npx skills add https://github.com/aascer39/codeagent --skill frontend-design-aascer39
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: frontend-design
Source: https://github.com/aascer39/codeagent/tree/main/.agents/skills/frontend-design
Command: npx skills add https://github.com/aascer39/codeagent --skill frontend-design-aascer39

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated frontend interfaces tend to fall into recognizable template patterns—cream backgrounds with serif display fonts, uniform rounded SaaS cards, generic fade-in animations. This Skill helps you produce distinctive, intentional visual designs that match the product's theme instead of defaulting to generic output. ## Core Features & Use Cases - Theme-First Visual Direction: Derives color, typography, and layout choices from the product's industry and content rather than from templates, with a checklist of common generative design clichés to avoid. - Two-Round Design Process: Brainstorm a compact token system (4-6 named hex colors, font roles, ASCII layout sketch), then self-review against the brief for uniqueness before writing any code. - Quality Floor Checks: Covers responsive behavior, keyboard focus visibility, reduced-motion compliance, contrast, loading/empty/error states, and copywriting discipline. - Use Case: When asked to build a landing page or dashboard UI, use this Skill to define a deliberate visual identity, audit the proposal for template defaults, and implement with disciplined restraint. ## Quick Start Use the frontend-design skill to design a landing page for my product with a distinctive visual direction instead of a generic template look.

Frequently Asked Questions about frontend-design

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

FAQPage Schema
When should I not introduce a new visual system?▼

When the requirement is a pure functional fix that does not change the user experience, do not introduce a new visual system. Component implementation should follow the project's existing tech stack and established patterns.