tailwind-expert
Use when implementing tailwind functionality with production-grade patterns and safeguards.
- License 许可
- MIT
- 最近更新
- 2026-04-11
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- tailwind-expert
- metadata
- { "hermes": { "tags": [ "codex-agent", "general" ], "source": "codex-field-kit/general" } }
- description
- Use when implementing tailwind functionality with production-grade patterns and safeguards.
03 SKILL.md 正文
Tailwind Expert
Focus Areas
- Understanding the utility-first approach of Tailwind
- Customizing Tailwind configuration for specific projects
- Leveraging Tailwind's responsive design capabilities
- Utilizing Tailwind's typographic utilities effectively
- Implementing custom themes with Tailwind
- Integrating Tailwind with CSS processors like PostCSS
- Managing design tokens with Tailwind
- Rapid prototyping with Tailwind's utility classes
- Optimizing Tailwind for large-scale applications
- Adopting Tailwind best practices for maintainable code
Approach
- Begin by exploring Tailwind's extensive utility classes
- Customize Tailwind's default theme for project-specific needs
- Use Tailwind's responsive grid system for layout
- Simplify styling through Tailwind's built-in utilities
- Manage component spacing with Tailwind's margin and padding utilities
- Ensure performance with PurgeCSS to remove unused styles
- Enhance component appearance with Tailwind's shadow utilities
- Optimize typography with Tailwind's font utility classes
- Leverage Tailwind's color palette for consistent design
- Adopt atomic design principles using Tailwind classes
Quality Checklist
- Tailwind configuration is tailored to project needs
- Responsive design is thoroughly tested across devices
- Consistent use of spacing and typography utilities
- Style clashes are minimized with proper utility usage
- Tailwind's design tokens are effectively managed
- Unused styles are purged for optimal performance
- Code readability is maintained with clear class organization
- Tailwind updates are smoothly integrated into the workflow
- Cross-browser compatibility is ensured with Tailwind utilities
- API and documentation are referenced for best practices
Output
- Styled components utilizing Tailwind's utility classes
- Responsive layouts implemented with Tailwind's grid system
- Consistent design theme across the application
- Optimized CSS output by purging unused styles
- Style guides using Tailwind's default and extended themes
- Comprehensive documentation for Tailwind usage in the project
- Scalable and maintainable CSS codebase with Tailwind
- Thoroughly tested responsive design with Tailwind breakpoints
- Efficient and readable code adhering to Tailwind's principles
- Pre-configured Tailwind setup ready for further customization
04 同仓库更多 Skills
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
swarm-planner
[EXPLICIT INVOCATION ONLY] Creates dependency-aware implementation plans optimized for parallel multi-agent execution.
super-swarm-spark
Only to be triggered by explicit super-swarm-spark commands.
role-creator
Create and install Codex custom agent roles in ~/.codex/config.toml, generate role config files, enforce supported keys, and guide users through required role inputs (model, reasoning effort, developer_instructions).
read-github
Read and search GitHub repository documentation via gitmcp.io MCP service. **WHEN TO USE:** - User provides a GitHub URL - User mentions a specific repo in owner/repo format - User asks "what does this repo do?", "read the docs for X repo", or similar - User wants to search code or docs within a repo
planner
Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: "make a plan", "create a plan", "plan this out", "plan the implementation", "help me plan", "design a plan", "draft a plan", "write a plan", "outline the steps", "break this down into tasks", "what's the plan for", or any similar planning request. Also triggers on explicit "/planner" or "/plan" commands.