skill-tailwindWrite, configure, migrate, and review modern Tailwind CSS v4 (CSS-first) in any stack or none — framework-agnostic, examples are plain HTML + CSS/SCSS. Use w...
Install via ClawdBot CLI:
clawdbot install rekryt/skill-tailwindGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://clawhub.ai/user/rekrytAudited Aug 8, 2026 · audit v1.0
Generated Aug 8, 2026
A large enterprise is migrating its legacy CSS codebase to Tailwind CSS v4. They need to map existing design tokens into @theme, migrate from v3 configuration, and ensure consistency across multiple teams. The skill provides a structured reference for CSS-first configuration, token mapping, and migration rules, ensuring a smooth transition without visual regression.
Startups and agencies building MVPs need to quickly style UI components without the overhead of a full design system. Tailwind CSS v4 allows utility-first styling that speeds up iteration. This skill guides teams on choosing between utility-first and BEM+@apply approaches, and provides agnostic component patterns for common elements like buttons, forms, and cards.
Developers creating themes for CMS platforms like WordPress or headless CMSs need to style content and layouts consistently. Tailwind's CSS-first configuration integrates well with PHP or templating engines. The skill's documentation on custom utilities, variants, and design tokens helps them build maintainable themes with dark mode and responsive design.
DesignOps teams responsible for maintaining design tokens across multiple products can use this skill to define and document Tailwind CSS v4 @theme tokens. It ensures tokens are semantically named and mapped correctly, enabling cross-product consistency and easier theme switching, including dark mode.
Teams maintaining a component library built with Tailwind CSS v4 will benefit from this skill's review checklists and best practices for @apply usage, variant stacks, and accessibility. It helps prevent anti-patterns, ensures consistent styling, and facilitates adding new components in both utility-first and BEM approaches.
A SaaS product that provides a UI component library or theme built with Tailwind CSS, generating recurring subscription revenue. The skill helps ensure the underlying Tailwind code is high-quality, maintainable, and suitable for a wide range of customers.
Web development agencies use this skill to deliver faster, more consistent Tailwind CSS implementations for clients. It reduces debugging time, ensures best practices, and increases client satisfaction. Revenue is project-based or hourly billing.
Selling premium UI kits, themes, or templates built with Tailwind CSS. The free version attracts users, while the paid version includes advanced components and documentation. The skill ensures the codebase is robust and documented, justifying the premium price.
💬 Integration Tip
When integrating into a project, start by mapping existing design tokens to @theme variables to ensure consistency, and use the skill's decision tree to determine whether to use utility-first or BEM+@apply for each component. Also, integrate the skill's reference docs into your team's documentation repository for easy access.
Scored Aug 8, 2026
Use when building UI with shadcn/ui components, Tailwind CSS layouts, form patterns with react-hook-form and zod, theming, dark mode, sidebar layouts, mobile navigation, or any shadcn component question.
Tailwind reference tool. Use when working with tailwind in frontend contexts.
A product creation skill based on the "Bee Website Builder" Open API. It is used to create a new product under a specified site language and product group, w...
A product update skill based on the "Bee Website Builder" Open API. It is used to update an existing product under a specified site language and supports upd...
Build WCAG 2.1 AA compliant websites with semantic HTML, proper ARIA, focus management, and screen reader support. Includes color contrast (4.5:1 text), keyboard navigation, form labels, and live regions. Use when implementing accessible interfaces, fixing screen reader issues, keyboard navigation, or troubleshooting "focus outline missing", "aria-label required", "insufficient contrast".
Use when building Vue 3 applications with Composition API, Nuxt 3, or Quasar. Invoke for Pinia, TypeScript, PWA, Capacitor mobile apps, Vite configuration.