frontend-design

# Frontend Design (Impeccable Fusion Edition) This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. It fuses [Impeccable](https://github.com/pbakaus/impeccable) design philosophy with extended knowledge on state management, engineering, and design style systems. --- ## Context Gathering Protocol Design skills produce generic output without project context. You MUST have confirmed design context before doing any design work. **Required context** — every design skill needs at minimum: - **Target audience**: Who uses this product and in what context? - **Use cases**: What jobs are they trying to get done? - **Brand personality/tone**: How should the interface feel? **Gathering order:** 1. **Check current instructions (instant)**: If your loaded instructions already contain a **Design Context** section, proceed immediately. 2. **Check .impeccable.md (fast)**: If not in instructions, read `.impeccable.md` from the project root. If it exists and contains the required context, proceed. 3. **Run /teach-impeccable (REQUIRED)**: If neither source has context, you MUST run `/teach-impeccable` NOW before doing anything else. Do NOT skip this step. Do NOT attempt to infer context from the codebase instead. --- ## Design Direction Commit to a BOLD aesthetic direction: - **Purpose**: What problem does this interface solve? Who uses it? - **Tone**: Pick an extreme: brutally minimal, maximalist chaos, retro-futuristic...