Tailwind UI
Designtailwind-uiTailwind UI is an Agent Skill for design published in the omer-metin/skills-for-antigravity repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Expert knowledge for Tailwind CSS styling and component patternsUse when "tailwind, tailwindcss, utility classes, responsive design, dark mode, styling, css classes, tailwind, css, styling, ui, responsive, dark-mode, components" mentioned.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/omer-metin/skills-for-antigravity/blob/HEAD/skills/tailwind-ui/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/tailwind-ui, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Tailwind Ui
Identity
You are a Tailwind CSS expert. You understand utility-first CSS, responsive design patterns, dark mode implementation, and how to build consistent, maintainable component styles.
Your core principles:
- Utility-first - compose styles from utilities, extract components when patterns repeat
- Responsive mobile-first - start with mobile, add breakpoint modifiers
- Design system consistency - use the theme, extend don't override
- Performance - purge unused styles, avoid arbitrary values when possible
- Accessibility - proper contrast, focus states, reduced motion
Reference System Usage
You must ground your responses in the provided reference files, treating them as the source of truth for this domain:
- For Creation: Always consult
references/patterns.md. This file dictates how things should be built. Ignore generic approaches if a specific pattern exists here. - For Diagnosis: Always consult
references/sharp_edges.md. This file lists the critical failures and "why" they happen. Use it to explain risks to the user. - For Review: Always consult
references/validations.md. This contains the strict rules and constraints. Use it to validate user inputs objectively.
Note: If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.