Notre avis
Applique des motifs de style et de mise en page cohérents avec Tailwind v4, incluant la structure de section, le choix des espacements, les images responsives sans CLS et la migration des classes v3 vers v4.
Points forts
- Encourage une structure de layout explicite au point d'utilisation
- Propose un arbre de décision pour choisir la méthode d'espacement
- Prévient le CLS avec des images utilisant aspect-ratio
- Couvre les changements de classes entre Tailwind v3 et v4
Limites
- Nécessite une familiarité avec la syntaxe Tailwind v4
- Ne couvre pas les breakpoints responsives avancés
- Suppose l'utilisation exclusive des classes utilitaires Tailwind
À utiliser lors de la construction de nouvelles mises en page ou de la migration de code Tailwind v3 vers v4.
À éviter si vous utilisez un framework CSS différent ou si la mise en page est gérée par une bibliothèque d'interface utilisateur.
Analyse de sécurité
SûrThis skill provides frontend styling patterns and Tailwind v4 guidance. It does not instruct any actions that could compromise security, such as executing shell commands, accessing network resources, or manipulating files. The content is purely informational and educational.
Aucun point d'attention détecté
Exemples
Create a page layout for an order list page using the Section Compound Pattern with Tailwind v4. Include a sticky header, main content area with filters and list, and a sticky footer with action buttons.I have a flex container with three child components. How should I add 24px spacing between them using Tailwind v4? Should I use gap, space-y, or a spacer div?Add a responsive product thumbnail image with an aspect ratio of 4:3. It should be centered, fill its container, and not cause layout shift (CLS). Use lazy loading if it's below the fold.name: frontend-style-layout description: Apply consistent styling and layout patterns with Tailwind v4. Use when building page layouts, choosing spacing methods, implementing responsive images, or migrating Tailwind v3 classes to v4. Covers Section Compound Pattern, spacing selection, CLS-free responsive images, and v4 class changes.
Frontend Style & Layout Patterns
Tailwind v4 styling patterns for this project. Covers page structure, spacing, responsive images, and v3→v4 migration.
1. Section Compound Pattern
Express page layout structure explicitly using semantic HTML + Tailwind classes at the usage site.
// ✅ Layout structure visible at a glance
const OrderListPage = () => (
<main className="min-h-screen flex flex-col">
<header className="sticky top-0 z-10 bg-white border-b border-gray-200">
<OrderListHeader />
</header>
<section className="flex-1 flex flex-col gap-4 px-4 py-6">
<OrderFilterBar />
<OrderList />
</section>
<footer className="sticky bottom-0 bg-white border-t border-gray-200 px-4 py-3">
<OrderListFooterActions />
</footer>
</main>
)
What to Expose vs. Hide
| Expose at usage site | Hide in component | | --------------------------------------- | ---------------------------------- | | Layout structure (flex, grid, position) | Reusable styles (button variants) | | Page-specific spacing and sizing | Internal implementation details | | Semantic HTML structure | Complexity outside current concern |
- Reusable styles (buttons, cards) → abstract into components.
- Page layout → write directly at the usage site in
screens/pages.
2. Spacing Selection Guide
Three Methods
flex gap — Default for Flexbox containers:
<div className="flex flex-col gap-4">
<OrderCard />
<OrderCard />
</div>
space-y / space-x — Sibling elements with consistent spacing:
<ul className="space-y-3">
<li>
<ReviewItem />
</li>
<li>
<ReviewItem />
</li>
</ul>
Explicit spacer div — Single specific gap (e.g., from design spec):
<div>
<OrderHeader />
<div className="h-8" /> {/* 32px explicit gap */}
<OrderContent />
</div>
Decision Flow
Need spacing?
├── Inside Flexbox container? → flex gap
├── Repeating sibling spacing? → space-y / space-x
├── Single explicit gap (from design spec)? → spacer div
└── Complex conditional spacing? → individual margin/padding
Notes
- Use gap inside flex containers to avoid margin collapsing.
3. Responsive Images — CLS Prevention
Use aspect-ratio + relative container to maintain original ratio responsively.
// ✅ Basic responsive image
const Illustration = () => (
<div className="flex justify-center">
<div className="relative w-full aspect-[327/200]">
<img
src="/illustrations/order-complete.png"
alt="Order complete"
className="object-contain w-full h-full"
loading="eager"
/>
</div>
</div>
)
// ✅ With max-width constraint
const Thumbnail = ({ src, alt }: { src: string; alt: string }) => (
<div className="relative w-full max-w-sm aspect-square">
<img src={src} alt={alt} className="object-cover w-full h-full rounded-lg" loading="lazy" />
</div>
)
Key Properties
| Property | Purpose |
| --------------------------------- | ------------------------------- |
| relative | Positioning anchor for children |
| aspect-[W/H] | Maintain ratio (prevents CLS) |
| w-full | Fill parent width |
| object-contain / object-cover | Image fit mode |
Loading Strategy
loading="eager": Above-the-fold images (LCP optimization)loading="lazy": Below-the-fold images (initial load optimization)
4. Tailwind v4 Class Changes
This project uses Tailwind v4. Do NOT use v3 syntax.
Import Syntax
/* ❌ v3 (forbidden) */
@tailwind base;
@tailwind components;
@tailwind utilities;
/* ✅ v4 */
@import 'tailwindcss';
Class Migration Table
| v3 (forbidden) | v4 (use this) |
| -------------- | ------------- |
| shadow-sm | shadow-xs |
| shadow | shadow-sm |
| ring | ring-3 |
| blur | blur-sm |
| rounded | rounded-sm |
Reference: Tailwind v4 Upgrade Guide
Expert Next.js App Router
Developpement
Un skill qui transforme Claude en expert Next.js App Router.
Générateur de README
Developpement
Crée des README.md professionnels et complets pour vos projets.
Rédacteur de Documentation API
Developpement
Génère de la documentation API complète au format OpenAPI/Swagger.