frontend-design

Guides frontend UI implementation, refinement, and audit with evidence-based design quality gates.

1|Updated Sep 10, 2026
One-click install
npx skills add https://github.com/thienty1207/Hotel_Staff --skill frontend-design-thienty1207
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: frontend-design
Source: https://github.com/thienty1207/Hotel_Staff/tree/main/.baron/core/skills/frontend-design
Command: npx skills add https://github.com/thienty1207/Hotel_Staff --skill frontend-design-thienty1207

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Frontend work often produces generic, template-looking interfaces that ignore product context, accessibility, and responsive behavior. This Skill provides structured guidance for building, refining, and auditing UI surfaces so changes stay grounded in repository evidence and verified design standards. ## Core Features & Use Cases - Mode Selection: Choose between audit, refine, and redesign modes with explicit boundaries so small styling tasks do not escalate into unapproved redesigns. - Design Quality Gates: Apply anti-template checks, brief fingerprints, and responsive/state proof matrices to catch generic card grids, decorative gradients, contrast issues, and untested viewports. - Verification Discipline: Record every responsive, interaction, and accessibility check as observed, not applicable, or not verified instead of claiming unmeasured results. - Use Case: When asked to improve a SvelteKit dashboard page, load the anti-template gates reference, preserve the existing information architecture, verify mobile and desktop layouts, and report exactly which states were tested. ## Quick Start Ask the assistant to refine the styling of a specific page or component while preserving its current layout and verifying responsive and accessibility behavior.

Frequently Asked Questions about frontend-design

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

FAQPage Schema
How do I improve a frontend page without redesigning it?▼

Use the refine mode, which preserves the existing information architecture, user flows, and design language while improving spacing, typography, color, and interaction states. A redesign is only allowed when explicitly requested or justified by recorded evidence.

What is the difference between audit, refine, and redesign modes?▼

Audit reviews an existing surface and reports evidence-backed findings without changes. Refine improves a known surface while keeping its product job intact. Redesign changes structure and requires explicit user approval plus documented evidence.

Does this frontend guidance work with Svelte, Vue, or vanilla projects?▼

Yes, the guidance is framework-agnostic and explicitly warns against stack-mismatched advice such as recommending Next.js-only patterns for Svelte or Vue projects. It aligns with existing repository conventions and design tokens instead.

How are responsive and accessibility claims verified?▼

Each viewport and interaction state is recorded as observed, not applicable with reason, or not verified using the responsive-state-proof matrix. Unchecked viewports or states can never be reported as passing.

When should the reference files be loaded?▼

Load brief-fingerprint.md for new compositions or approved redesigns, anti-template-gates.md for visual refinement or dashboard work, and responsive-state-proof.md for responsive, form, or accessibility tasks. Small CSS or copy changes need no references.