Initial commit

This commit is contained in:
2026-04-25 12:37:38 +03:00
committed by GitHub
commit df7302b8b0
85 changed files with 10204 additions and 0 deletions
@@ -0,0 +1,27 @@
---
name: frontend-design
description: Use this skill when the user asks to design/build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
---
You tend to converge toward generic, "on distribution" outputs. In frontend design,this creates what users call the "AI slop" aesthetic. Avoid this: make creative,distinctive frontends that surprise and delight.
Focus on:
- Typography: Choose fonts that are beautiful, unique, and interesting. Avoid generic fonts like Arial and Inter; opt instead for distinctive choices that elevate the frontend's aesthetics.
- Color & Theme: Commit to a cohesive aesthetic. Use CSS variables for consistency. Dominant colors with sharp accents outperform timid, evenly-distributed palettes. Draw from IDE themes and cultural aesthetics for inspiration.
- Motion: Use animations for effects and micro-interactions. Prioritize CSS-only solutions for HTML. Use Motion library for React when available. Focus on high-impact moments: one well-orchestrated page load with staggered reveals (animation-delay) creates more delight than scattered micro-interactions.
- Backgrounds: Create atmosphere and depth rather than defaulting to solid colors. Layer CSS gradients, use geometric patterns, or add contextual effects that match the overall aesthetic.
Avoid generic AI-generated aesthetics:
- Overused font families (Inter, Roboto, Arial, system fonts)
- Clichéd color schemes (particularly purple gradients on white backgrounds)
- Predictable layouts and component patterns
- Cookie-cutter design that lacks context-specific character
Interpret creatively and make unexpected choices that feel genuinely designed for the context. Vary between light and dark themes, different fonts, different aesthetics. You still tend to converge on common choices (Space Grotesk, for example) across generations. Avoid this: it is critical that you think outside the box!
</frontend_aesthetics>
**IMPORTANT**: Match implementation complexity to the aesthetic vision. Maximalist designs need elaborate code with extensive animations and effects. Minimalist or refined designs need restraint, precision, and careful attention to spacing, typography, and subtle details. Elegance comes from executing the vision well.
**Remember:** The agent is capable of extraordinary creative work. Don't hold back, show what can truly be created when thinking outside the box and committing fully to a distinctive vision.
// Source: [Improving frontend design through Skills](https://www.claude.com/blog/improving-frontend-design-through-skills).
@@ -0,0 +1,83 @@
---
description: Read before writing any Tailwind CSS to understand the latest v4 features.
---
# Tailwind CSS v4 Development Practices
## Core Philosophy
- CSS-first configuration via `@theme` directive (no `tailwind.config.js`)
- Native CSS features: cascade layers, `@property`, `color-mix()`, logical properties
- Automatic content detection
## Setup
```css
@import "tailwindcss";
```
## @theme Configuration
### Define Tokens
```css
@theme {
--color-brand: oklch(0.72 0.11 178);
--font-display: "Inter", sans-serif;
--breakpoint-tablet: 640px;
}
```
→ Use as: `bg-brand`, `font-display`
### Multi-theme Pattern
```css
@theme inline {
--color-primary: var(--primary);
}
:root { --primary: #3b82f6; }
.dark { --primary: #60a5fa; }
```
Use `@theme inline` for runtime variable resolution.
### Rules
- Keep @theme variables flat (top-level only)
- No nesting in @media or selectors
- Use :root for non-Tailwind CSS variables
## v4 Features
### Native Opacity
```html
<div class="bg-black/50 text-brand/75">
```
### Container Queries
```html
<div class="@container">
<div class="@md:text-lg">
</div>
```
### Arbitrary CSS Variables
```html
<div class="fill-[--my-color] w-[--sidebar-width]">
```
### New Utilities
- 3D: `rotate-x-45`, `rotate-y-90`
- Gradients: `bg-gradient-radial`, `bg-gradient-conic`
- Variants: `not-*`, `color-scheme:*`, `@starting-style`
## Migration
### Renamed Classes
- `bg-opacity-50` → `bg-black/50`
- `overflow-ellipsis` → `text-ellipsis`
- `shadow-sm` → `shadow-xs`
## Best Practices
1. Put design tokens in `@theme`
2. Use `:root` for regular CSS variables
3. Trust auto-detection
4. Prefer `w-[--custom]` over complex config
// Seed prompt
// > Fill in a 1-pager copilot instructions (compact, minimal prose), targeted for frontend devs and focused on tailwind v4-specific development essentials; #web_search