tailwind
Tailwind CSS
Act as a frontend engineer reviewing Tailwind CSS usage for consistency, maintainability, and best practices.
Review: $ARGUMENTS
TailwindCSS {
Layout {
Use gap-* on parent containers instead of margins on children. Gaps are consistent and don't leak spacing.
Use stack utilities (v-stack, h-stack, center, spacer, z-stack) when the project defines them — prefer these over raw flex flex-col / flex flex-row.
Switch layout direction at breakpoints for responsive stacks: v-stack lg:h-stack gap-4.
}
ClassNameHandling {
Always use cn() (clsx + tailwind-merge) to merge class names in components. External className props go last so consumers can override.
Type className props properly: ClassName for single-element components, ClassNameRecord<"root" | "label" | "input"> for multi-element components.
}
More from iulspop/aidd-skills
svg-to-react
Converts SVG files into optimized React TypeScript components with proper accessibility attributes, currentColor fills, and consistent naming conventions. Use when adding icons or SVG assets to a React project.
29security-check
Security audit for web applications based on OWASP Top 10 and common vulnerabilities. Use when auditing code for security issues, reviewing auth/authz, or before production deployment.
26documentation
Generates clear, example-driven documentation with runnable code samples and progressive complexity. Use when writing API docs, guides, READMEs, or any technical documentation.
25better-writer
Rewrites text to be clearer, simpler, and more engaging using Scott Adams' writing principles and persuasive techniques. Use when editing marketing copy, blog posts, emails, or any business text that needs to be punchier.
23brainstorm
Facilitates solution ideation with clear trade-offs and a final recommendation. Use when exploring architectural decisions, evaluating technology choices, or comparing implementation approaches before writing code.
23unit-tests
Generates well-structured unit tests using Vitest with the "given/should" prose format. Use when writing tests for new code, adding coverage to existing code, or following TDD practices.
22