Home / Cursor rules / Solidjs Tailwind
Solidjs Tailwind
Cursor rules for Solid.js development with Tailwind CSS integration.
Cursor rules (.mdc)Public domain (CC0)
–unranked
Install
mkdir -p .cursor/rules && curl -sL https://raw.githubusercontent.com/PatrickJS/awesome-cursorrules/b044f956f021b6e8877f16781bcfc466a6a120e9/rules/solidjs-tailwind-cursorrules-prompt-file.mdc -o .cursor/rules/solidjs-tailwind.mdcDownloads the file at commit b044f956f021 into .cursor/rules/.
To remove it later:
rm .cursor/rules/solidjs-tailwind.mdcContext cost: ≈313 tokens when used.
Rules file
--- description: "Cursor rules for Solid.js development with Tailwind CSS integration." globs: **/* alwaysApply: false --- // Solid.js with Tailwind CSS .cursorrules // Prefer functional components const preferFunctionalComponents = true; // Solid.js and Tailwind CSS best practices const solidjsTailwindBestPractices = [ "Use createSignal() for reactive state", "Implement Tailwind CSS classes for styling", "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", ]; // Folder structure const folderStructure = ` src/ components/ pages/ styles/ App.jsx index.jsx public/ index.html tailwind.config.js postcss.config.js `; // Additional instructions const additionalInstructions = ` 1. Use JSX for component templates 2. Implement proper Tailwind CSS purging for production builds 3. Utilize Solid Router for routing when applicable 4. Use Tailwind's @layer directive for custom styles 5. Implement utility-first CSS approach 6. Follow both Solid.js and Tailwind naming conventions 7. Use JIT (Just-In-Time) mode for faster development `;
Security
Scanned Nov 4, 2026 at commit b044f956f021, with Cisco's open-source skill-scanner.
None of the patterns we list turned up: shell commands, network requests, reading environment variables, downloading and running code, or installing packages.
A scan lists patterns in the code. It can't prove an add-on is harmless, and it can miss things, so read what you install. How we scan