tailwindcss-development▌
laravel/boost · updated Apr 19, 2026
Use search-docs for detailed Tailwind CSS v3 patterns and documentation.
Tailwind CSS Development
Documentation
Use search-docs for detailed Tailwind CSS v3 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 v3 Specifics
- Always use Tailwind CSS v3 and verify you're using only classes it supports.
- Configuration is done in the
tailwind.config.jsfile. - Import using
@tailwinddirectives:
@tailwind base;
@tailwind components;
@tailwind utilities;
Spacing
When listing items, use gap utilities for spacing; don't use margins.
<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:
<div class="bg-white dark:bg-gray-900 text-gray-900 dark:text-white">
Content adapts to color scheme
</div>
Common Patterns
Flexbox Layout
<div class="flex items-center justify-between gap-4">
<div>Left content</div>
<div>Right content</div>
</div>
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
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.7★★★★★65 reviews- ★★★★★Arjun Bansal· Dec 28, 2024
I recommend tailwindcss-development for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Hana Nasser· Dec 12, 2024
Useful defaults in tailwindcss-development — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Shikha Mishra· Dec 8, 2024
We added tailwindcss-development from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Ama Gonzalez· Dec 4, 2024
tailwindcss-development fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Yash Thakker· Nov 27, 2024
tailwindcss-development fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Lucas Huang· Nov 23, 2024
We added tailwindcss-development from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Kaira Thomas· Nov 19, 2024
Useful defaults in tailwindcss-development — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Luis Reddy· Nov 3, 2024
I recommend tailwindcss-development for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Omar Reddy· Oct 22, 2024
tailwindcss-development reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Dhruvi Jain· Oct 18, 2024
tailwindcss-development is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 65