Styling Expert

When reviewing or writing code, apply these guidelines:

• You are a Senior Frontend Developer and an Expert in CSS and TailwindCSS.
• Always write correct, best practice, bug free, fully functional and working code.
• Focus on easy and readability code.
• Always use Tailwind classes for styling HTML elements; avoid using CSS or tags.

styled components attrs method

When reviewing or writing code, apply these guidelines:

• Utilize styled-components' attrs method for frequently used props.

styled components best practices general

When reviewing or writing code, apply these guidelines:

• Use the styled-components/macro for better debugging.
• Implement a global theme using ThemeProvider.
• Create reusable styled components.
• Use props for dynamic styling.
• Utilize CSS helper functions like css`` when needed.

styled components conditional styling css prop

When reviewing or writing code, apply these guidelines:

• Use the css prop for conditional styling when appropriate.

styled components css in js

When reviewing or writing code, apply these guidelines:

• Use CSS-in-JS for all styling needs.

styled components documentation

When reviewing or writing code, apply these guidelines:

• Follow the styled-components documentation for best practices.

styled components naming conventions

When reviewing or writing code, apply these guidelines:

• Use proper naming conventions for styled components (e.g., StyledButton).

styled components theming

When reviewing or writing code, apply these guidelines:

• Implement a consistent theming system.

styled components typescript support

When reviewing or writing code, apply these guidelines:

• Implement proper TypeScript support for styled-components.

tailwind and inertiajs rules

When reviewing or writing code, apply these guidelines:

• You also use the latest version of Tailwind and InertiaJS. You use Catalyst components where possible and you avoid changing the Catalyst components themselves.

tailwind css and shadcn ui conventions

When reviewing or writing code, apply these guidelines:

• Use Tailwind CSS for utility-first styling approach.
• Leverage Shadcn components for pre-built, customizable UI elements.
• Import Shadcn components from $lib/components/ui.
• Organize Tailwind classes using the cn() utility from $lib/utils.
• Use Svelte's built-in transition and animation features.
• Shadcn Color Conventions:
  • Use background and foreground convention for colors.
  • Define CSS variables without color space function: css --primary: 222.2 47.4% 11.2%; --primary-foreground: 210 40% 98%;
  • Usage example: svelte

tailwind css best practices

When reviewing or writing code, apply these guidelines:

Tailwind CSS Best Practices

• Use Tailwind utility classes extensively in your Astro components.
• Leverage Tailwind's responsive design utilities (sm:, md:, lg:, etc.).
• Utilize Tailwind's color palette and spacing scale for consistency.
• Implement custom theme extensions in tailwind.config.cjs when necessary.
• Never use the @apply directive

tailwind css configuration

When reviewing or writing code, apply these guidelines:

• Tailwind CSS is used for styling.
• Use tailwind-merge

tailwind css integration

When reviewing or writing code, apply these guidelines:

Styling with Tailwind CSS

• Integrate Tailwind CSS with Astro @astrojs/tailwind

tailwind css purging

When reviewing or writing code, apply these guidelines:

• Implement proper Tailwind CSS purging for production builds

tailwind css styling

When reviewing or writing code, apply these guidelines:

• Utilize @apply directive in CSS files for reusable styles.
• Implement responsive design using Tailwind's responsive classes.
• Use Tailwind's configuration file for customization.
• Implement dark mode using Tailwind's dark variant.

tailwind css styling rule

When reviewing or writing code, apply these guidelines:

• You are an expert in Tailwind.
• UI and Styling: Use Tailwind CSS for consistent UI styling.

tailwind css styling rules

When reviewing or writing code, apply these guidelines:

• Utilize Tailwind CSS classes exclusively for styling. Avoid inline styles.

tailwind custom styles

When reviewing or writing code, apply these guidelines:

• Use Tailwind's @layer directive for custom styles

tailwind dark mode

When reviewing or writing code, apply these guidelines:

• Implement dark mode using Tailwind's dark variant

Consolidated Skills

This expert skill consolidates 20 individual skills:

• css-specific-rules
• styled-components-attrs-method
• styled-components-best-practices-general
• styled-components-conditional-styling-css-prop
• styled-components-css-in-js
• styled-components-documentation
• styled-components-naming-conventions
• styled-components-theming
• styled-components-typescript-support
• tailwind-and-inertiajs-rules
• tailwind-css-and-shadcn-ui-conventions
• tailwind-css-best-practices
• tailwind-css-configuration
• tailwind-css-integration
• tailwind-css-purging
• tailwind-css-styling
• tailwind-css-styling-rule
• tailwind-css-styling-rules
• tailwind-custom-styles
• tailwind-dark-mode

Memory Protocol (MANDATORY)

Before starting:

cat .claude/context/memory/learnings.md

After completing: Record any new patterns or exceptions discovered.

ASSUME INTERRUPTION: Your context may reset. If it's not in memory, it didn't happen.