tech-tailwind
Skill1 starsChanged 28 days agoMITView on GitHub
Technology skill loaded when styling components with Tailwind CSS.
In this repository29 other files it gives its agents.
- exec-accessibilitySkill
- exec-architectureSkill
- exec-code-reviewSkill
- exec-debuggingSkill
- exec-documentationSkill
- exec-performanceSkill
- exec-refactoringSkill
- exec-repo-patternsSkill
- exec-securitySkill
- exec-testingSkill
- exec-ui-uxSkill
- exec-verificationSkill
- tech-dockerSkill
- tech-flutterSkill
- tech-goSkill
- tech-graphqlSkill
- tech-kotlinSkill
- tech-nextjsSkill
- tech-nodeSkill
- tech-postgresSkill
- tech-pythonSkill
- tech-reactSkill
- tech-rustSkill
- tech-swiftSkill
- tech-typescriptSkill
- tech-vueSkill
- linear-spanks-gitSkill
- linear-spanksSkill
- linear-workflowSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
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
- Distinctive: line 11
When applying styles using Tailwind:
- Very specific: line 16
Extraction: Do not prematurely extract classes using @apply.
- Very specific: line 17
State Modifiers: Use hover:, focus:, active:, and disabled: for interactive states natively within the class string.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Tailwind CSS Best Practices
Apply this skill after inspecting repository conventions and supported versions. Treat its rules as defaults unless they protect a concrete safety property; preserve an established project pattern when it conflicts, and record the reason in the implementation plan.
When applying styles using Tailwind:
- Utility-First: Strictly use Tailwind utility classes. Avoid writing custom CSS in stylesheets unless absolutely necessary (e.g., complex animations).
- Arbitrary Values: Minimize the use of arbitrary values (e.g.,
w-[32px]). Use the theme design tokens (e.g.,w-8) to maintain consistency. - Responsiveness: Design mobile-first. Apply base styles for mobile and use
sm:,md:,lg:prefixes for larger screens. - Extraction: Do not prematurely extract classes using
@apply. If a component is reused, extract the React/HTML component itself, not the CSS classes. - State Modifiers: Use
hover:,focus:,active:, anddisabled:for interactive states natively within the class string.
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.