web-tailwind

Included with Lifetime

$97 forever

Tailwind CSS 4: utility classes, config, JIT, arbitrary values, darkMode, plugins, shadcn/ui

Designtailwindcssutilityweb

What this skill does


# web-tailwind

## Purpose
This skill enables the AI to assist with Tailwind CSS 4 for building responsive, utility-first web interfaces, focusing on features like utility classes, configuration, JIT compilation, arbitrary values, dark mode, plugins, and shadcn/ui integration.

## When to Use
Use this skill when developing web projects that require rapid styling with reusable classes, such as creating responsive layouts, theming with dark mode, or integrating pre-built components from shadcn/ui. Apply it in scenarios like frontend development for React/Vue apps or static sites where CSS bloat needs minimization.

## Key Capabilities
- Utility classes for direct styling (e.g., 'flex', 'p-4', 'hover:bg-blue-700').
- JIT mode for on-demand CSS generation to reduce bundle size.
- Arbitrary values for custom styling (e.g., 'w-[14rem]' for width).
- Dark mode support via 'dark:' prefix or media queries.
- Plugins for extending functionality, like adding custom utilities.
- shadcn/ui integration for component-based UI kits.
- Responsive design with breakpoints (e.g., 'md:flex' for medium screens and up).

## Usage Patterns
To apply Tailwind classes, add them directly to HTML elements in your markup. For configuration, edit the tailwind.config.js file to customize themes, extend utilities, or enable JIT. Always import Tailwind's base, components, and utilities in your CSS entry point. For shadcn/ui, clone the repository and integrate components via Tailwind classes. To enable dark mode, set it in config and use the 'dark:' variant.

Example 1: Create a responsive button.
```html
<button class="bg-blue-500 hover:bg-blue-700 text-white font-bold py-2 px-4 rounded md:px-6">
  Click me
</button>
```

Example 2: Configure dark mode in tailwind.config.js.
```js
module.exports = {
  darkMode: 'class',  // Use 'media' for OS-level or 'class' for manual toggle
  theme: { extend: {} },
};
```

## Common Commands/API
Use the Tailwind CLI for building and initializing projects. Run `npx tailwindcss init` to generate tailwind.config.js. Build CSS with `npx tailwindcss -i ./input.css -o ./output.css --jit` to enable JIT mode. For purging unused styles, add content paths in config: `content: ['./src/**/*.{html,js}']`. API-wise, Tailwind exposes no direct endpoints, but access config via JavaScript modules. To add plugins, require them in config: `plugins: [require('tailwindcss/plugin')(function({ addUtilities }) { ... })]`.

## Integration Notes
Integrate Tailwind by installing via npm: `npm install -D tailwindcss`. In a React project, import the output CSS in your index.js: `import './output.css';`. For shadcn/ui, run `npx shadcn-ui@latest init` and select Tailwind as the framework, then add components like buttons with Tailwind classes. If using Vite or Webpack, configure PostCSS to process Tailwind. Environment variables aren't required, but for any API-based tools (e.g., if extending with external services), use `$TAILWIND_API_KEY` in scripts.

## Error Handling
If JIT doesn't enable, check for misconfiguration in tailwind.config.js (e.g., ensure `mode: 'jit'` is set). For purging errors, verify content paths include all relevant files; add debug mode with `--watch` flag. Common issues: Missing utilities might indicate uninstalled plugins—install via npm and restart build. If dark mode fails, ensure the 'dark' class is added to the HTML element and check for CSS conflicts. Handle arbitrary values errors by validating CSS units (e.g., use 'px' or 'rem'). Always run `npx tailwindcss build --config tailwind.config.js` to test outputs.

## Graph Relationships
- Related to cluster: web-dev (shares tools for web development).
- Connected to tags: tailwind (core framework), css (styling language), utility (class-based approach), web (domain focus).
- Links to other skills: web-react (for integrating with React components), web-vue (for Vue.js projects).

Files: 1

Size: 4.2 KB

Complexity: 12/100

Category: Design

Source: https://github.com/alphaonedev/openclaw-graph/tree/main/skills/web-dev/web-tailwind

Related in Design

contribute

Included

Local-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".

Designscripts

architectural-analysis

Included

User-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).

Designscripts

mcp

Included

Model Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.

Designscripts

react-native-skia

Included

Design, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.

Designscripts

plaid

Included

Product Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".

Designscripts

nextjs-framer-motion-animations

Included

Adds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.

Designscripts