Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add bugrabilge/bilge-development-kit --skill tailwind-patternsgit clone --depth 1 https://github.com/bugrabilge/bilge-development-kitWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/bugrabilge/bilge-development-kit/tailwind-patterns)<a href="https://agentmods.dev/skills/bugrabilge/bilge-development-kit/tailwind-patterns"><img src="https://agentmods.dev/badge/skills/bugrabilge/bilge-development-kit/tailwind-patterns/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/bugrabilge/bilge-development-kit/tailwind-patterns"><img src="https://agentmods.dev/badge/skills/bugrabilge/bilge-development-kit/tailwind-patterns.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00039 | $0.01651 |
| Opus 5 | $0.00019 | $0.00826 |
| Sonnet 5 | $0.00008 | $0.00330 |
| Haiku 4.5 | $0.00004 | $0.00165 |
Grade A, and why
tailwind-patterns scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tailwind Patterns
"Utility-first CSS trades premature abstraction for explicit, composable, and deletable styles."
When to Use
- Building or styling components with Tailwind CSS
- Setting up Tailwind configuration and custom themes
- Creating reusable component patterns without custom CSS
- Implementing responsive and dark mode designs
- Reviewing Tailwind usage for consistency and performance
Core Philosophy
- Utility-first: compose small utility classes rather than writing custom CSS
- Extract components (React, Vue, etc.) rather than creating @apply-heavy CSS classes
- Use @apply sparingly and only in base layer resets or truly global styles
- Let Tailwind's purge (content config) remove unused styles automatically
Responsive Design
Mobile-First Breakpoints
- Tailwind uses min-width breakpoints by default: sm, md, lg, xl, 2xl
- Write base styles for mobile, then layer on responsive modifiers
- Example:
class="text-sm md:text-base lg:text-lg" - Avoid max-width breakpoints unless truly needed (use
max-sm:,max-md:etc.)
Container Patterns
- Use
mx-auto max-w-7xl px-4 sm:px-6 lg:px-8for centered page containers - Prefer max-w constraints over the container class for more control
- Use CSS Grid with Tailwind:
grid grid-cols-1 md:grid-cols-2 lg:grid-cols-3 gap-6
Responsive Visibility
hidden md:blockto hide on mobile, show on desktopmd:hiddento show on mobile, hide on desktop- Prefer responsive layout changes over hiding/showing duplicate content
Component Patterns
Buttons
<!-- Primary -->
<button class="inline-flex items-center justify-center rounded-md bg-blue-600 px-4 py-2 text-sm font-medium text-white shadow-sm hover:bg-blue-700 focus-visible:outline-2 focus-visible:outline-offset-2 focus-visible:outline-blue-600 disabled:opacity-50 disabled:cursor-not-allowed transition-colors">
Button
</button>
- Always include focus-visible styles for keyboard accessibility
- Use disabled: modifier for disabled states
- Add transition-colors for smooth hover effects
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 5d ago First seen · 169 lines · 39 tokens per session scan A a1a439e607c3
tailwind-patterns is a skill published in the GitHub repository bugrabilge/bilge-development-kit (10 stars, last pushed 4mo ago), licensed MIT. It adds 39 tokens to every session and 1,651 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
waitlist-page
A simple waitlist page for collecting email addresses from people interested in a new product or early-access release.
animation-principles
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use motion-system (design-systems); for a full interaction spec use micro-interaction-spec.