solidjs-tailwind-cursorrules-prompt-file

solidjs-tailwind-cursorrules-prompt-file is a cursor rule for Cursor from PatrickJS/awesome-cursorrules. It costs 274 tokens per session, scanned A, original, CC0-1.0.

Coding guidance for Solid.js interfaces styled with Tailwind CSS. Tailwind CSS is a utility-based system for applying layout, colors, spacing, responsive behavior, and dark mode in web projects.

In plain words
What is it for?
Use it to build Solid.js components with Tailwind classes, create reusable styles, configure responsive and dark-mode behavior, and organize CSS layers.
Why use it?
It keeps component code and styling conventions consistent while supporting responsive layouts and production CSS builds.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc). Also seen: mentions Cursor.

Good fit Use it to build Solid.js components with Tailwind classes, create reusable styles, configure responsive and dark-mode behavior, and organize CSS layers.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/patrickjs/awesome-cursorrules/solidjs-tailwind-cursorrules-prompt-file
About the project

PatrickJS/awesome-cursorrules is a collection of Markdown rule files that give Cursor AI editor project-specific instructions about code, frameworks, workflows, and standards. Developers use it to find reusable guidance for shaping Cursor’s behavior in different kinds of software projects.

PatrickJS/awesome-cursorrules · 40,734 stars · on GitHub

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/PatrickJS/awesome-cursorrules

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for solidjs-tailwind-cursorrules-prompt-file

README.md
[![agentmods](https://agentmods.dev/badge/rules/patrickjs/awesome-cursorrules/solidjs-tailwind-cursorrules-prompt-file.svg)](https://agentmods.dev/rules/patrickjs/awesome-cursorrules/solidjs-tailwind-cursorrules-prompt-file)
Your own site
<a href="https://agentmods.dev/rules/patrickjs/awesome-cursorrules/solidjs-tailwind-cursorrules-prompt-file"><img src="https://agentmods.dev/badge/rules/patrickjs/awesome-cursorrules/solidjs-tailwind-cursorrules-prompt-file.svg" alt="Measured on agentmods" height="20"></a>
Per session 274 This file is loaded in full into every session.
When invoked 274 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00274 $0.00274
Opus 5 $0.00137 $0.00137
Sonnet 5 $0.00055 $0.00055
Haiku 4.5 $0.00027 $0.00027

Measured 4d ago against content hash 95bba76097f5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

solidjs-tailwind-cursorrules-prompt-file scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

rules/solidjs-tailwind-cursorrules-prompt-file.mdc · 49 lines

What it actually says

// 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 `;
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 4d ago First seen · 49 lines · 274 tokens per session scan A 95bba76097f5

Subscribe to this mod's changes

solidjs-tailwind-cursorrules-prompt-file is a cursor rule published in the GitHub repository PatrickJS/awesome-cursorrules (40,734 stars, last pushed 3mo ago), licensed CC0-1.0. It adds 274 tokens to every session, about $0.0014 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.