tailwindcss-development
Skill0 starsChanged 5 days agoMITView on GitHub
Always invoke when the user's message includes 'tailwind' in any form. Also invoke for: building responsive grid layouts (multi-column card grids, product grids), flex/grid page structures (dashboards with sidebars, fixed topbars, mobile-toggle navs), styling UI components (cards, tables, navbars, pricing sections, forms, inputs, badges), adding dark mode variants, fixing spacing or typography, and Tailwind v3/v4 work. The core use case: writing or fixing Tailwind utility classes in HTML templates (Blade, JSX, Vue). Skip for backend PHP logic, database queries, API routes, JavaScript with no HTML/CSS component, CSS file audits, build tool configuration, and vanilla CSS.
26 other projects use a version of this, 25 of them edited.
Adopted by
Most recently taken up by
- ownego/token-slayeredited, first seen Nov 8, 2026
- rbaskam/PRismedited, first seen Nov 1, 2026
- relaticle/relaticleedited, first seen Oct 31, 2026
- fanswoo/skillstheir own version, first seen Oct 11, 2026
- RiprLutuk/PasPapanedited, first seen Oct 8, 2026
- trypostit/trypostedited, first seen Oct 8, 2026
Used with
Projects with it also use socialite-development, configuring-horizon and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
ownegoSkillsocialite-development
Manages OAuth social authentication with Laravel Socialite. Activate when adding social login providers; configuring OAuth redirect/callback flows; retrieving authenticated user details; customizing scopes or parameters; setting up community providers; testing with Socialite fakes; or when the user mentions social login, OAuth, Socialite, or third-party authentication.
Also in 11 projects that use this
datashamanSkillconfiguring-horizon
Use this skill whenever the user mentions Horizon by name in a Laravel context. Covers the full Horizon lifecycle: installing Horizon (horizon:install, Sail setup), configuring config/horizon.php (supervisor blocks, queue assignments, balancing strategies, minProcesses/maxProcesses), fixing the dashboard (authorization via Gate::define viewHorizon, blank metrics, horizon:snapshot scheduling), and troubleshooting production issues (worker crashes, timeout chain ordering, LongWaitDetected notifications, waits config). Also covers job tagging and silencing. Do not use for generic Laravel queues without Horizon, SQS or database drivers, standalone Redis setup, Linux supervisord, Telescope, or job batching.
Also in 10 projects that use this
datashamanSkillpassport-development
Develops OAuth2 API authentication with Laravel Passport. Activates when installing or configuring Passport; setting up OAuth2 grants (authorization code, client credentials, personal access tokens, device authorization); managing OAuth clients; protecting API routes with token authentication; defining or checking token scopes; configuring SPA cookie authentication; handling token lifetimes and refresh tokens; or when the user mentions Passport, OAuth2, API tokens, bearer tokens, or API authentication. Make sure to use this skill whenever the user works with OAuth2, API tokens, or third-party API access, even if they don't explicitly mention Passport.
Also in 7 projects that use this
syofyanzuhadSkillwayfinder-development
Use this skill for Laravel Wayfinder which auto-generates typed functions for Laravel controllers and routes. ALWAYS use this skill when frontend code needs to call backend routes or controller actions. Trigger when: connecting any React/Vue/Svelte/Inertia frontend to Laravel controllers, routes, building end-to-end features with both frontend and backend, wiring up forms or links to backend endpoints, fixing route-related TypeScript errors, importing from @/actions or @/routes, or running wayfinder:generate. Use Wayfinder route functions instead of hardcoded URLs. Covers: wayfinder() vite plugin, .url()/.get()/.post()/.form(), query params, route model binding, tree-shaking. Do not use for backend-only task
Also in 5 projects that use this
m3ueSkillai-sdk-development
TRIGGER when working with ai-sdk which is Laravel official first-party AI SDK. Activate when building, editing AI agents, chatbots, text generation, image generation, audio/TTS, transcription/STT, embeddings, RAG, vector stores, reranking, structured output, streaming, conversation memory, tools, queueing, broadcasting, and provider failover across OpenAI, Anthropic, Gemini, Azure, Groq, xAI, DeepSeek, Mistral, Ollama, ElevenLabs, Cohere, Jina, and VoyageAI. Invoke when the user references ai-sdk, the `Laravel\Ai\` namespace, or this project's AI features — not for Prism PHP or other AI packages used directly.
Also in 9 projects that use this
whisper-moneySkillcashier-stripe-development
Handles Laravel Cashier Stripe integration including subscriptions, webhooks, Stripe Checkout, invoices, charges, refunds, trials, coupons, metered billing, and payment failure handling. Triggered when a user mentions Cashier, Billable, IncompletePayment, stripe_id, newSubscription, Stripe subscriptions, or billing. Also applies when setting up webhooks, handling SCA/3DS payment failures, testing with Stripe test cards, or troubleshooting incomplete subscriptions, CSRF webhook errors, or migration publish issues.
Also in 5 projects that use this
Other versions26 projects use a version of this.
Word for word · 0
None found.
Edited · 25
- coollabsio/coolify★ 66k58% same
- anonaddy/anonaddy★ 4.9k55% same
- yaojingang/GEOFlow★ 4.1k63% same
- Relaticle/relaticle★ 1.8k55% same
- relaticle/relaticle★ 1.8k55% same
- nasirkhan/laravel-starter★ 1.4k58% same
- Blair2004/NexoPOS★ 1.3k45% same
- filamentphp/demo★ 1.2k44% same
- whisper-money/whisper-money★ 1.2k63% same
- WINBIGFOX/TimeScribe★ 93349% same
15 more not listed
Wrote their own version · 1
- fanswoo/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- impeccableSkill
- inertia-vue-developmentSkill
- laravel-best-practicesSkill
- tailwindcss-developmentSkill
- impeccableSkill
- inertia-vue-developmentSkill
- laravel-best-practicesSkill
- impeccableSkill
The file
We split this skill into the rules it gives an agent
9 rules. 2 are common, 5 are distinctive, and 2 are very specific to this project.
2
Common
Most of the 26 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Use search-docs for detailed Tailwind CSS v4 patterns and documentation.
- Common: line 17
Use Tailwind CSS classes to style HTML.
- Common: line 19
Consider class placement, order, priority, and defaults.
- Distinctive: line 26
Import with a single CSS import:
- Distinctive: line 35
When listing items, use gap utilities for spacing.
- Very specific: line 47
If existing pages and components support dark mode, new pages and components must support it the same way, typically using the dark: …
- Distinctive: line 81
Check browser for visual rendering
- Distinctive: line 83
Verify dark mode if project uses it
- Distinctive: line 89
Not checking existing project conventions before adding new utilities
“Common” is measured: kept by at least 6 in 10 of the 26 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Tailwind CSS Development
Documentation
Use search-docs for detailed Tailwind CSS v4 patterns and documentation.
Basic Usage
- Use Tailwind CSS classes to style HTML. Check and follow existing Tailwind conventions in the project before introducing new patterns.
- Offer to extract repeated patterns into components that match the project's conventions (e.g., Blade, JSX, Vue).
- Consider class placement, order, priority, and defaults. Remove redundant classes, add classes to parent or child elements carefully to reduce repetition, and group elements logically.
Tailwind CSS v4 Specifics
- This project runs Tailwind CSS v4 (
@tailwindcss/vite). Verify you're using only classes v4 supports. - Configuration is CSS-first in
resources/css/app.css: design tokens live in@theme inline, content sources in@source, and custom utilities are declared with@utility(a class must be declared that way before it can be used in@apply). - There is no
tailwind.config.js; do not create one. Tailwind v4 also scans project files for class names, so stray config-like files can add unused utilities. - Import with a single CSS import:
<!-- v4 Import Syntax -->@import 'tailwindcss';Spacing
When listing items, use gap utilities for spacing; don't use margins.
<!-- Gap Utilities --><div class="flex gap-8">
<div>Item 1</div>
<div>Item 2</div>
</div>Dark Mode
If existing pages and components support dark mode, new pages and components must support it the same way, typically using the dark: variant:
<!-- Dark Mode --><div class="bg-white dark:bg-gray-900 text-gray-900 dark:text-white">
Content adapts to color scheme
</div>Common Patterns
Flexbox Layout
<!-- Flexbox Layout --><div class="flex items-center justify-between gap-4">
<div>Left content</div>
<div>Right content</div>
</div>Grid Layout
<!-- Grid Layout --><div class="grid grid-cols-1 md:grid-cols-2 lg:grid-cols-3 gap-6">
<div>Card 1</div>
<div>Card 2</div>
<div>Card 3</div>
</div>Verification
- Check browser for visual rendering
- Test responsive breakpoints
- Verify dark mode if project uses it
Common Pitfalls
- Using margins for spacing between siblings instead of gap utilities
- Forgetting to add dark mode variants when the project uses dark mode
- Not checking existing project conventions before adding new utilities
- Overusing inline styles when Tailwind classes would suffice
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

