
frontend-design
by gtakairo
Personal dotfiles and development environment configurations with comprehensive Claude Code setup
SKILL.md
name: frontend-design description: "Create production-ready frontend interfaces with high-quality, memorable design. Use when building web components, pages, or applications." enabled: true visibility: default allowedTools: ["read", "write", "edit", "glob", "grep", "bash"]
Frontend Design Skill
Create visually striking, production-grade frontend interfaces that avoid generic AI aesthetics.
Design Thinking Process
Before writing any code, understand and commit to a bold aesthetic direction:
1. Understand Context
- Purpose: What problem does this interface solve? Who uses it?
- Tone: Choose a distinctive aesthetic direction
- Constraints: Technical requirements (framework, performance, a11y)
- Differentiation: What makes this memorable?
2. Aesthetic Directions
Choose one and commit fully:
| Direction | Characteristics |
|---|---|
| Minimal | Extreme restraint, precision typography, whitespace |
| Maximalist | Rich layers, bold colors, density |
| Retro-futuristic | Nostalgic tech aesthetics, neon, CRT vibes |
| Organic | Natural curves, earth tones, fluid motion |
| Luxury | Refined typography, subtle animations, premium feel |
| Playful | Rounded shapes, vibrant colors, toy-like interactions |
| Editorial | Magazine layouts, asymmetry, dramatic typography |
| Brutalist | Raw, exposed, honest, anti-design aesthetic |
| Industrial | Utility-focused, monospace, technical precision |
CRITICAL: Pick a clear direction and execute with precision. Both bold maximalism and refined minimalism work. What matters is intentionality, not intensity.
Aesthetic Guidelines
Typography
❌ AVOID: Inter, Roboto, Arial, system fonts, Space Grotesk
✅ USE: Beautiful, unique, interesting typefaces
Strategy:
- Distinctive display font + refined body font
- Unexpected, personality-driven font choices
- text-balance for headings, text-pretty for body
- tabular-nums for data display
Color & Theme
✅ Use consistent CSS variables
✅ Dominant color + striking accent
❌ AVOID: Timid, evenly-distributed palettes
❌ AVOID: Purple gradients on white (overused AI aesthetic)
Light vs Dark:
- Don't just invert colors
- Different fonts, different aesthetics possible
- Each theme should feel intentionally designed
Motion & Animation
Priority:
1. One unified animation on page load
2. Staggered reveals (animation-delay)
3. Scroll-triggered and hover states
4. CSS-only when possible with HTML/CSS
Technical:
- Animate only transform and opacity
- Duration ≤ 200ms for micro-interactions
- Respect prefers-reduced-motion
- Use motion/react for JavaScript animations
- High-impact moments over scattered micro-interactions
Spatial Composition
✅ Unexpected layouts
✅ Asymmetry and overlapping elements
✅ Diagonal flows
✅ Grid-breaking elements
✅ Generous negative space OR controlled density
❌ AVOID: Cookie-cutter predictable layouts
Background & Visual Details
Create atmosphere and depth, not just solid colors:
- Gradient meshes
- Noise textures
- Geometric patterns
- Layered transparency
- Dramatic shadows
- Decorative borders
- Custom cursors
- Grain overlays
Technical Implementation
Stack Preferences
CSS: Tailwind CSS (default)
Animation: motion/react for JS, CSS for simple effects
Class logic: cn() utility (clsx/tailwind-merge)
Icons: aria-label required for icon-only buttons
Component Guidelines
Accessibility:
- Use accessible primitives: Base UI, React Aria, Radix
- NEVER rebuild keyboard/focus behavior manually
- Icon-only buttons must have aria-label
Interactions:
- Destructive actions require AlertDialog confirmation
- Display errors near where action happens
- Never block paste functionality
Do's and Don'ts
❌ NEVER
- Use overused fonts (Inter, Roboto, Arial, system fonts)
- Purple gradient on white background
- Predictable cookie-cutter layouts
- Designs lacking context-specific personality
- Scattered micro-interactions without purpose
- Add animations unless explicitly requested
✅ ALWAYS
- Interpret creatively
- Make unexpected choices
- Design as if truly made for the context
- Make light/dark themes genuinely different
- Ensure every design is unique
- Match implementation complexity to aesthetic vision
Complexity Matching
Maximalist Design:
→ Complex code with extensive animations and effects
→ Rich layering, bold choices, density
Minimalist Design:
→ Restraint, precision, careful attention to space
→ Focus on typography and subtle details
→ Elegance from well-executed vision
Output Approach
When building interfaces:
- State your aesthetic direction before coding
- Explain key design choices (fonts, colors, layout approach)
- Implement with full commitment to the chosen direction
- Include responsive considerations
- Provide accessible markup
## Design Direction
[Aesthetic: chosen direction]
[Key choices: typography, color, layout approach]
## Implementation
[Code with detailed styling]
## Responsive Notes
[Mobile/tablet considerations]
Mindset
Claude can do extraordinary creative work. Don't hold back. When you "think outside the box" and fully commit to a clear vision, show what you can truly create.
The goal: interfaces that are intentional, memorable, and production-ready.
スコア
総合スコア
リポジトリの品質指標に基づく評価
SKILL.mdファイルが含まれている
ライセンスが設定されている
100文字以上の説明がある
GitHub Stars 100以上
3ヶ月以内に更新がある
10回以上フォークされている
オープンIssueが50未満
プログラミング言語が設定されている
1つ以上のタグが設定されている
レビュー
レビュー機能は近日公開予定です