.agents/skills/frontend-design/SKILL.md
Design thinking and decision-making for web UI. Use when designing components, layouts, color schemes, typography, or creating aesthetic interfaces. Teaches principles, not fixed values.
npx skillsauth add JoelBonito/gestion-chs frontend-designInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Philosophy: Every pixel has purpose. Restraint is luxury. User psychology drives decisions. Core Principle: THINK, don't memorize. ASK, don't assume.
Read REQUIRED files always, OPTIONAL only when needed:
| File | Status | When to Read | |------|--------|--------------| | ux-psychology.md | 🔴 REQUIRED | Always read first! | | color-system.md | ⚪ Optional | Color/palette decisions | | typography-system.md | ⚪ Optional | Font selection/pairing | | visual-effects.md | ⚪ Optional | Glassmorphism, shadows, gradients | | animation-guide.md | ⚪ Optional | Animation needed | | motion-graphics.md | ⚪ Optional | Lottie, GSAP, 3D | | decision-trees.md | ⚪ Optional | Context templates | | scripts/accessibility_checker.py | ⚪ Optional | Accessibility audit |
🔴 ux-psychology.md = ALWAYS READ. Others = only if relevant.
Execute these for audits (don't read, just run):
| Script | Purpose | Usage |
|--------|---------|-------|
| scripts/ux_audit.py | UX Psychology & Accessibility Audit | python scripts/ux_audit.py <project_path> |
STOP! If the user's request is open-ended, DO NOT default to your favorites.
Color not specified? Ask:
"What color palette do you prefer? (blue/green/orange/neutral/other?)"
Style not specified? Ask:
"What style are you going for? (minimal/bold/retro/futuristic/organic?)"
Layout not specified? Ask:
"Do you have a layout preference? (single column/grid/asymmetric/full-width?)"
| AI Default Tendency | Why It's Bad | Think Instead | |---------------------|--------------|---------------| | Bento Grids (Modern Cliché) | Used in every AI design | Why does this content NEED a grid? | | Hero Split (Left/Right) | Predictable & Boring | How about Massive Typography or Vertical Narrative? | | Mesh/Aurora Gradients | The "new" lazy background | What's a radical color pairing? | | Glassmorphism | AI's idea of "premium" | How about solid, high-contrast flat? | | Deep Cyan / Fintech Blue | Safe harbor from purple ban | Why not Red, Black, or Neon Green? | | "Orchestrate / Empower" | AI-generated copywriting | How would a human say this? | | Dark background + neon glow | Overused, "AI look" | What does the BRAND actually need? | | Rounded everything | Generic/Safe | Where can I use sharp, brutalist edges? |
🔴 "Every 'safe' structure you choose brings you one step closer to a generic template. TAKE RISKS."
Before any design work, ANSWER THESE or ASK USER:
| Constraint | Question | Why It Matters | |------------|----------|----------------| | Timeline | How much time? | Determines complexity | | Content | Ready or placeholder? | Affects layout flexibility | | Brand | Existing guidelines? | May dictate colors/fonts | | Tech | What stack? | Affects capabilities | | Audience | Who exactly? | Drives all visual decisions |
| Audience | Think About | |----------|-------------| | Gen Z | Bold, fast, mobile-first, authentic | | Millennials | Clean, minimal, value-driven | | Gen X | Familiar, trustworthy, clear | | Boomers | Readable, high contrast, simple | | B2B | Professional, data-focused, trust | | Luxury | Restrained elegance, whitespace |
| Law | Principle | Application | |-----|-----------|-------------| | Hick's Law | More choices = slower decisions | Limit options, use progressive disclosure | | Fitts' Law | Bigger + closer = easier to click | Size CTAs appropriately | | Miller's Law | ~7 items in working memory | Chunk content into groups | | Von Restorff | Different = memorable | Make CTAs visually distinct | | Serial Position | First/last remembered most | Key info at start/end |
VISCERAL (instant) → First impression: colors, imagery, overall feel
BEHAVIORAL (use) → Using it: speed, feedback, efficiency
REFLECTIVE (memory) → After: "I like what this says about me"
Use for proportional harmony:
├── Content : Sidebar = roughly 62% : 38%
├── Each heading size = previous × 1.618 (for dramatic scale)
├── Spacing can follow: sm → md → lg (each × 1.618)
All spacing and sizing in multiples of 8:
├── Tight: 4px (half-step for micro)
├── Small: 8px
├── Medium: 16px
├── Large: 24px, 32px
├── XL: 48px, 64px, 80px
└── Adjust based on content density
| Element | Consideration | |---------|---------------| | Touch targets | Minimum comfortable tap size | | Buttons | Height based on importance hierarchy | | Inputs | Match button height for alignment | | Cards | Consistent padding, breathable | | Reading width | 45-75 characters optimal |
60% → Primary/Background (calm, neutral base)
30% → Secondary (supporting areas)
10% → Accent (CTAs, highlights, attention)
| If You Need... | Consider Hues | Avoid | |----------------|---------------|-------| | Trust, calm | Blue family | Aggressive reds | | Growth, nature | Green family | Industrial grays | | Energy, urgency | Orange, red | Passive blues | | Luxury, creativity | Deep Teal, Gold, Emerald | Cheap-feeling brights | | Clean, minimal | Neutrals | Overwhelming color |
For detailed color theory: color-system.md
| Content Type | Scale Ratio | Feel | |--------------|-------------|------| | Dense UI | 1.125-1.2 | Compact, efficient | | General web | 1.25 | Balanced (most common) | | Editorial | 1.333 | Readable, spacious | | Hero/display | 1.5-1.618 | Dramatic impact |
Contrast + Harmony:
├── DIFFERENT enough for hierarchy
├── SIMILAR enough for cohesion
└── Usually: display + neutral, or serif + sans
For detailed typography: typography-system.md
Key properties:
├── Semi-transparent background
├── Backdrop blur
├── Subtle border for definition
└── ⚠️ **WARNING:** Standard blue/white glassmorphism is a modern cliché. Use it radically or not at all.
Elevation concept:
├── Higher elements = larger shadows
├── Y-offset > X-offset (light from above)
├── Multiple layers = more realistic
└── Dark mode: may need glow instead
Harmonious gradients:
├── Adjacent colors on wheel (analogous)
├── OR same hue, different lightness
├── Avoid harsh complementary pairs
├── 🚫 **NO Mesh/Aurora Gradients** (floating blobs)
└── VARY from project to project radically
For complete effects guide: visual-effects.md
Duration based on:
├── Distance (further = longer)
├── Size (larger = slower)
├── Importance (critical = clear)
└── Context (urgent = fast, luxury = slow)
| Action | Easing | Why | |--------|--------|-----| | Entering | Ease-out | Decelerate, settle in | | Leaving | Ease-in | Accelerate, exit | | Emphasis | Ease-in-out | Smooth, deliberate | | Playful | Bounce | Fun, energetic |
For animation patterns: animation-guide.md, for advanced: motion-graphics.md
For EVERY design task:
1. CONSTRAINTS
└── What's the timeline, brand, tech, audience?
└── If unclear → ASK
2. CONTENT
└── What content exists?
└── What's the hierarchy?
3. STYLE DIRECTION
└── What's appropriate for context?
└── If unclear → ASK (don't default!)
4. EXECUTION
└── Apply principles above
└── Check against anti-patterns
5. REVIEW
└── "Does this serve the user?"
└── "Is this different from my defaults?"
└── "Would I be proud of this?"
For deeper guidance on specific areas:
Remember: Design is THINKING, not copying. Every project deserves fresh consideration based on its unique context and users. Avoid the Modern SaaS Safe Harbor!
tools
n8n workflow automation principles, patterns, and validation. Expression syntax, node configuration, MCP tools usage, code node patterns.
testing
# Example Skill > Template skill for specialist squads. Replace with your domain-specific knowledge. ## Overview This skill provides domain-specific knowledge and patterns for the squad. ## When to Use - When the squad needs domain expertise - When applying domain-specific patterns - When reviewing domain-related outputs ## Key Principles 1. **Principle 1:** Description of the first principle 2. **Principle 2:** Description of the second principle 3. **Principle 3:** Description of the th
development
Web application testing principles. E2E, Playwright, deep audit strategies.
development
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".