Tailwind CSS Patterns (v4 - 2025)

Overview

This public intake copy packages

plugins/antigravity-awesome-skills-claude/skills/tailwind-patterns

https://github.com/sickn33/antigravity-awesome-skills

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses

metadata.json

ORIGIN.md

Tailwind CSS Patterns (v4 - 2025) > Modern utility-first CSS with CSS-native configuration.

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: 1. Tailwind v4 Architecture, 2. CSS-Based Configuration, 3. Container Queries (v4 Native), 4. Responsive Design, 5. Dark Mode, 6. Modern Layout Patterns.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

• Use this skill when configuring Tailwind v4, using CSS-first theme and design tokens, or implementing container queries and modern Tailwind patterns.
• Use when the request clearly matches the imported source intent: Tailwind CSS v4 principles. CSS-first configuration, container queries, modern patterns, design token architecture.
• Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.
• Use when provenance needs to stay visible in the answer, PR, or review packet.
• Use when copied upstream references, examples, or scripts materially improve the answer.
• Use when the workflow should remain reviewable in the public intake repo before the private enhancer takes over.

Operating Table

metadata.json

ORIGIN.md

SKILL.md

SKILL.md

## Related Skills

Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

1. Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
2. Read the overview and provenance files before loading any copied upstream support files.
3. Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
4. Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes.
5. Validate the result against the upstream expectations and the evidence you can point to in the copied files.
6. Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity.
7. Before merge or closure, record what was used, what changed, and what the reviewer still needs to verify.

Imported Workflow Notes

Imported: 1. Tailwind v4 Architecture

What Changed from v3

tailwind.config.js

@theme

@apply

v4 Core Concepts

--*

Examples

Example 1: Ask for the upstream workflow directly

Use @tailwind-patterns to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.

Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

Example 2: Ask for a provenance-grounded review

Review @tailwind-patterns against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.

Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

Example 3: Narrow the copied support files before execution

Use @tailwind-patterns for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.

Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

Example 4: Build a reviewer packet

Review @tailwind-patterns using the copied upstream files plus provenance, then summarize any gaps before merge.

Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.

Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

• Principle - Implementation
• Purge unused - Automatic in v4
• Avoid dynamism - No template string classes
• Use Oxide - Default in v4, 10x faster
• Cache builds - CI/CD caching
• Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
• Prefer the smallest useful set of support files so the workflow stays auditable and fast to review.

Imported Operating Notes

Imported: 12. Performance Principles

Remember: Tailwind v4 is CSS-first. Embrace CSS variables, container queries, and native features. The config file is now optional.

Troubleshooting

Problem: The operator skipped the imported context and answered too generically

Symptoms: The result ignores the upstream workflow in

plugins/antigravity-awesome-skills-claude/skills/tailwind-patterns

metadata.json

ORIGIN.md

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated

SKILL.md

Problem: The task drifted into a different specialization

Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.

Related Skills

• @supply-chain-risk-auditor

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @sveltekit

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @swift-concurrency-expert

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @swiftui-expert-skill

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

references

references/n/a

examples

examples/n/a

scripts

scripts/n/a

agents

agents/n/a

assets

assets/n/a

Imported Reference Notes

Imported: 2. CSS-Based Configuration

Theme Definition

@theme {
  /* Colors - use semantic names */
  --color-primary: oklch(0.7 0.15 250);
  --color-surface: oklch(0.98 0 0);
  --color-surface-dark: oklch(0.15 0 0);
  
  /* Spacing scale */
  --spacing-xs: 0.25rem;
  --spacing-sm: 0.5rem;
  --spacing-md: 1rem;
  --spacing-lg: 2rem;
  
  /* Typography */
  --font-sans: 'Inter', system-ui, sans-serif;
  --font-mono: 'JetBrains Mono', monospace;
}

When to Extend vs Override

Imported: 3. Container Queries (v4 Native)

Breakpoint vs Container

md:

@container

Container Query Usage

@container

@sm:

@md:

@lg:

@container/card

When to Use

Imported: 4. Responsive Design

Breakpoint System

sm:

md:

lg:

xl:

2xl:

Mobile-First Principle

1. Write mobile styles first (no prefix)
2. Add larger screen overrides with prefixes
3. Example:

   w-full md:w-1/2 lg:w-1/3

Imported: 5. Dark Mode

Configuration Strategies

class

.dark

media

selector

Dark Mode Pattern

bg-white

dark:bg-zinc-900

text-zinc-900

dark:text-zinc-100

border-zinc-200

dark:border-zinc-700

Imported: 6. Modern Layout Patterns

Flexbox Patterns

flex items-center justify-center

flex flex-col gap-4

flex gap-4

flex justify-between items-center

flex flex-wrap gap-4

Grid Patterns

grid grid-cols-[repeat(auto-fit,minmax(250px,1fr))]

grid grid-cols-3 grid-rows-2

grid grid-cols-[auto_1fr]

Note: Prefer asymmetric/Bento layouts over symmetric 3-column grids.

Imported: 7. Modern Color System

OKLCH vs RGB/HSL

Color Token Architecture

--blue-500

--color-primary

--button-bg

Imported: 8. Typography System

Font Stack Pattern

'Inter', 'SF Pro', system-ui, sans-serif

'JetBrains Mono', 'Fira Code', monospace

'Outfit', 'Poppins', sans-serif

Type Scale

text-xs

text-sm

text-base

text-lg

text-xl

Imported: 9. Animation & Transitions

Built-in Animations

animate-spin

animate-ping

animate-pulse

animate-bounce

Transition Patterns

transition-all duration-200

transition-colors duration-150

ease-out

ease-in-out

hover:scale-105 transition-transform

Imported: 10. Component Extraction

When to Extract

Extraction Methods

Imported: 11. Anti-Patterns

!important

style=

@apply

Imported: Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.