tailwind-react-firebase-cursorrules-prompt-file — Cursor rule
A Cursor rule that sets conventions for a mobile-first web app built with Tailwind, React and Firebase.
.cursor/rules/tailwind-react-firebase-cursorrules-prompt-file.mdcWhat tailwind-react-firebase-cursorrules-prompt-file does
Drop the file into Cursor as a rule and it lays out how the project should be written. Mobile screens come first, then larger ones, with Tailwind's responsive prefixes (sm:, md:, lg:, xl:) doing the scaling. A design system with shared colors, typography and spacing lives in tailwind.config.js as custom tokens. Accessibility gets its own section: contrast ratios, semantic HTML, ARIA where needed, keyboard navigation.
On performance the rule points to React.lazy() and Suspense for code-splitting, react-window for long lists, and image optimization. Firebase guidance covers security rules, the SDK's offline persistence, and queries that keep read/write operations low. Forms go through Formik or react-hook-form with validation and clear error messages. Interactive elements should be at least 44x44 pixels so they are easy to tap.
One line stands out: when creating a file, don't conflict it with existing .tsx and .jsx files. That assumes your project already carries both, so check your folder structure before you commit to this rule. The file also ends with a ready-made prompt for a language model about a pill-tracking feature with monthly adherence reports. It has nothing to do with your app, but it shows how the author frames requests.
What it helps with
- set one set of layout conventions for a Tailwind and React project
- audit contrast, keyboard access and semantic markup
- split the bundle with
React.lazy()andSuspense - wire up Firebase security rules and offline persistence
- pick a form library and validation approach
Example prompts for the agent
- Check my component against the rules in
.cursor/rules/tailwind-react-firebase-cursorrules-prompt-file.mdc - Build this product card mobile-first, the way the rule describes
- Rewrite this list to use virtualization with
react-window
How to install tailwind-react-firebase-cursorrules-prompt-file
Manually: put the files in place
.cursor/rules/tailwind-react-firebase-cursorrules-prompt-file.mdcFrontmatter: description, globs, alwaysApply
Manually: put the files in place
.claude/rules/tailwind-react-firebase-cursorrules-prompt-file.mdThe paths frontmatter field limits the files: move globs from the source into paths
AGENTS.md
Codex reads AGENTS.md: paste the rule text there
Manually: put the files in place
.github/instructions/tailwind-react-firebase-cursorrules-prompt-file.instructions.mdThe applyTo field sets which files it applies to: move globs from the source into applyTo
Manually: put the files in place
.devin/rules/tailwind-react-firebase-cursorrules-prompt-file.mdManually: put the files in place
.clinerules/tailwind-react-firebase-cursorrules-prompt-file.mdStep by step, with commands for each platform: Cursor rules: .mdc files, four modes and what replaced .cursorrules
Questions about tailwind-react-firebase-cursorrules-prompt-file
How do I install tailwind-react-firebase-cursorrules-prompt-file in Cursor?
Create .cursor/rules/tailwind-react-firebase-cursorrules-prompt-file.mdc in your project root and paste the rule contents into it. Cursor picks it up automatically.
What does this rule do?
It sets conventions for a mobile-first web app on Tailwind, React and Firebase: responsive layout, design tokens, accessibility, performance, forms and Firebase queries.
Does it need anything set up beforehand?
It assumes a project that already has both .tsx and .jsx files, otherwise the instruction about conflicts between them makes no sense. You also need tailwind.config.js for custom tokens.
Source text
tailwind-react-firebase-cursorrules-prompt-file.mdc · CC0-1.0
--- description: "Cursor rules for Tailwind development with React and Firebase integration." globs: **/* alwaysApply: false --- Here are some best practices and rules to follow for creating a high-quality, mobile-first web app with excellent UI/UX using Tailwind, React, and Firebase: Mobile-First Design: Always design and implement for mobile screens first, then scale up to larger screens. Use Tailwind's responsive prefixes (sm:, md:, lg:, xl:) to adjust layouts for different screen sizes. Consistent Design System: Create a design system with consistent colors, typography, spacing, and component styles. Utilize Tailwind's configuration file (tailwind.config.js) to define your custom design tokens. Performance Optimization: Use React.lazy() and Suspense for code-splitting and lazy-loading components. Implement virtualization for long lists using libraries like react-window. Optimize images and use next/image for automatic image optimization in Next.js. Responsive Typography: Use Tailwind's text utilities with responsive prefixes to adjust font sizes across different screens. Consider using a fluid typography system for seamless scaling. Accessibility: Ensure proper color contrast ratios using Tailwind's text-* and bg-* classes. Use semantic HTML elements and ARIA attributes where necessary. Implement keyboard navigation support. Touch-Friendly UI: Make interactive elements (buttons, links) at least 44x44 pixels for easy tapping. Implement touch gestures for common actions (swipe, pinch-to-zoom) where appropriate. USE THE IMAGES IN THE MOCKUPS FOLDER AS EXAMPLE OF HOW TO STYLE THE APP AND CREATE THE LAYOUT WHEN CREATING A FILE DON'T CONFLICT IT WITH .TSX AND .JSX FILES Firebase Best Practices: Implement proper security rules in Firebase. Use Firebase SDK's offline persistence for better performance and offline support. Optimize queries to minimize read/write operations. Error Handling and Feedback: Implement proper error boundaries in React. Provide clear feedback for user actions (loading states, success/error messages). Animation and Transitions: Use subtle animations to enhance UX (e.g., page transitions, micro-interactions). Utilize Tailwind's transition utilities or consider libraries like Framer Motion. Form Handling: Use libraries like Formik or react-hook-form for efficient form management. Implement proper form validation with clear error messages. Code Organization: Follow a consistent folder structure (e.g., components, hooks, pages, services). Use custom hooks to encapsulate and reuse logic. Native-like Features: Implement pull-to-refresh for content updates. Use smooth scrolling and momentum scrolling. Consider using libraries like react-spring for physics-based animations. Here’s a concise prompt for a language model to help you with the logic for creating AI-powered medication insights in your app: Prompt: Design a feature for a pill management app that tracks user interactions with medications (Take/Skip) and generates monthly adherence reports. The app should: User Interface: Display pills for "Morning," "Afternoon," and "Night" with buttons for "Take" and "Skip." Show a confirmation modal for user actions. Data Collection: Log user interactions (pill ID, action, timestamp, notes) in a database. Monthly Report: Aggregate data to calculate total pills scheduled vs. taken, adherence percentage, and trends (e.g., frequently skipped pills). AI Insights: Use basic statistical analysis to generate personalized suggestions based on user feedback (e.g., side effects, missed doses). Dashboard: Create a section for users to view their monthly reports, including adherence percentage, trends, and AI-generated suggestions. This prompt provides a clear and structured request for assistance in developing the feature, focusing on key components and functionality.
© PatrickJS · CC0-1.0 · PatrickJS/awesome-cursorrules