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 phuonghx/aim-cli --skill tailwind-patternsgit clone --depth 1 https://github.com/phuonghx/aim-cliWrote 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/phuonghx/aim-cli/tailwind-patterns)<a href="https://agentmods.dev/skills/phuonghx/aim-cli/tailwind-patterns"><img src="https://agentmods.dev/badge/skills/phuonghx/aim-cli/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/phuonghx/aim-cli/tailwind-patterns"><img src="https://agentmods.dev/badge/skills/phuonghx/aim-cli/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.00105 | $0.01678 |
| Opus 5.5 | $0.00042 | $0.00671 |
| Sonnet 5.5 | $0.00021 | $0.00336 |
| Haiku 4.5 | $0.00011 | $0.00168 |
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 1mo 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tailwind CSS v4 Patterns
Version 4 moves Tailwind's center of gravity into CSS itself. Configuration, tokens, and modern features all live in your stylesheet, and the JavaScript config file becomes optional.
What is different in v4
| Topic | v3 | v4 |
|---|---|---|
| Where config lives | tailwind.config.js |
@theme block in CSS |
| Compiler | PostCSS-based | A faster, Rust-based engine |
| On-demand generation | JIT mode you enabled | Always on, built in |
| Extending the system | JS plugins | Native CSS features |
| Tokens | Internal | Emitted as --* custom properties |
The mental shift: describe your design system in CSS, lean on real CSS variables, and prefer the platform's own capabilities (nesting, container queries) over plugins.
Theme tokens in CSS
Declare your scales once inside @theme; Tailwind turns each into both a utility and a
custom property you can read anywhere.
@theme {
/* semantic colors, expressed in OKLCH for even perceptual steps */
--color-brand: oklch(0.72 0.16 255);
--color-canvas: oklch(0.99 0 0);
--color-canvas-night: oklch(0.16 0 0);
/* a deliberate spacing rhythm */
--spacing-tight: 0.25rem;
--spacing-snug: 0.5rem;
--spacing-base: 1rem;
--spacing-loose: 2rem;
/* type families */
--font-body: "Inter", system-ui, sans-serif;
--font-code: "JetBrains Mono", ui-monospace, monospace;
}
Add tokens alongside the defaults when you want to grow the system; replace a whole
scale only when you intend to retire Tailwind's defaults for it. Reach for semantic
names (brand, canvas) so intent survives a redesign.
Two kinds of responsiveness
Viewport breakpoints answer the question "how wide is the screen?" Container queries answer "how wide is this component's box?" Reusable components should usually depend on the latter, so they adapt wherever they are dropped.
| Tool | Reacts to | Best for |
|---|---|---|
sm: md: lg: |
The viewport | Page-level layout decisions |
@container + @sm: @md: |
The nearest sized ancestor | Self-contained, reusable components |
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.
- 1mo ago First seen · 163 lines · 105 tokens per session scan A ec6fdcf5fb85
tailwind-patterns is a skill published in the GitHub repository phuonghx/aim-cli (1 stars, last pushed 3mo ago), licensed MIT. It adds 105 tokens to every session and 1,678 once invoked, about $0.0004 per session on Opus 5.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
design-critique
Use this skill to audit an interface that already exists and say precisely why it looks generated, templated, or unfinished — a scored rubric across composition, typography, color, states, accessibility and copy, ending in a ranked fix list. Triggers: user says "review the design", "critique this UI", "why does this…
design-craft
Design or substantially improve user-facing interfaces with a product-specific visual direction, content hierarchy, and rendered critique. Use for new screens, landing pages, redesigns, typography/layout work, or UI that feels generic or AI-generated. For small fixes, preserve the existing design without starting a…
von-restorff-effect
Apply the Von Restorff Effect — the element that differs from its neighbours is the one remembered. Use when a single action must dominate. For overall ordering rather than single-element emphasis, use visual-hierarchy.
handoff-spec
Write the implementation handoff — measurements, behaviours, assets, states, and edge cases. Use when engineering picks up the work. For verifying the result afterwards use design-qa-checklist; for reusable library components use component-spec (design-systems).
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.
readable-measure
Set line length and measure for comfortable reading across type sizes and breakpoints. Use when tuning body text. Covers measure only — for the full size and weight scale, use typography-scale.