tailwind-patterns

Generate Tailwind patterns for accessible, responsive Rails 8.x ERB and ViewComponents with Turbo/Hotwire UI compatibility.

1|Updated Jan 8, 2026
One-click install
npx skills add https://github.com/LaunchPadLab/ai-bank --skill tailwind-patterns-launchpadlab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tailwind-patterns
Source: https://github.com/LaunchPadLab/ai-bank/tree/main/claude/skills/tailwind-patterns
Command: npx skills add https://github.com/LaunchPadLab/ai-bank --skill tailwind-patterns-launchpadlab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you avoid inconsistent, inaccessible, or hard-to-maintain Tailwind CSS markup in Rails 8.x views by giving proven patterns for responsive layout, semantics, styling consistency, and interactive states.

Core Features & Use Cases

  • Mobile-first responsive design: Use Tailwind breakpoints (sm/md/lg/xl/2xl) to structure grids, typography, and spacing for all screen sizes.
  • Semantic HTML and accessibility: Prefer proper elements, labels, ARIA attributes (including aria-current), visible focus rings, and screen-reader-only text.
  • Consistent visual system: Apply a structured color palette, typography scale, spacing conventions, and reusable card/button patterns.
  • Rails/Turbo/Hotwire-friendly UI: Pair styling with Turbo frames/streams and ViewComponent-based reuse for maintainable components.

Quick Start

Ask your AI to generate a Rails 8.x ERB ViewComponent for a responsive, accessible dashboard card grid using Tailwind classes based on the tailwind-patterns reference and including hover, focus, and loading-friendly Turbo UI considerations.

Frequently Asked Questions about tailwind-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build accessible Rails UIs with Tailwind CSS without creating inconsistent markup?

Standardize Tailwind CSS utility patterns for Rails 8.x ERB views and ViewComponents to ensure accessible, responsive layouts with consistent semantic markup, ARIA attributes, and focus states. This prevents hard-to-maintain styling by enforcing mobile-first grids and reusable component-oriented patterns.

What's the best way to structure responsive Tailwind CSS grids in Rails ViewComponents?

Structure responsive Tailwind CSS grids in Rails ViewComponents by applying mobile-first breakpoints (sm, md, lg, xl, 2xl) for typography and spacing. This approach ensures consistent layout across screen sizes while maintaining semantic HTML and accessible interaction states within your ERB views.

Does Tailwind CSS work with Turbo and Hotwire for interactive Rails UI patterns?

Tailwind CSS works with Turbo and Hotwire by pairing utility classes with Turbo frames and streams for maintainable Rails UI. You can build loading-friendly interactions and reusable ViewComponent-based patterns that maintain consistent visual styling across dynamic page updates.

Can I use Tailwind CSS to enforce accessibility standards like ARIA and focus states in Rails?

Tailwind CSS can enforce accessibility standards in Rails by applying ARIA attributes, including aria-current, visible focus rings, and screen-reader-only text. Pairing these utilities with semantic HTML elements ensures screen reader compatibility and keyboard navigation across ViewComponents.

How do I maintain a consistent visual system using Tailwind CSS in a Rails application?

Maintain a consistent visual system in Rails by applying a structured Tailwind CSS color palette, typography scale, and spacing conventions. Using reusable card and button patterns within ViewComponents ensures styling consistency across all ERB views and UI components.

Why does my Tailwind CSS markup become hard to maintain in Rails ERB views?

Tailwind CSS markup becomes hard to maintain in Rails ERB views due to inconsistent utility usage and lack of standardized patterns. Applying proven component-oriented styling rules for responsive design, semantics, and interaction states resolves this fragmentation and improves accessibility.