html-tailwind-css-javascript-cursorrules-prompt-fi — Cursor rule
A Cursor rule for HTML, Tailwind CSS, and vanilla JavaScript work. Use it when an agent needs clear coding constraints for frontend files.
.cursor/rules/html-tailwind-css-javascript-cursorrules-prompt-fi.mdcWhat html-tailwind-css-javascript-cursorrules-prompt-fi does
This rule guides Cursor toward current HTML, Tailwind CSS, and vanilla JavaScript practices. It tells the assistant to follow requirements closely, confirm the task before coding, favor readable code, and finish the requested functionality without leaving placeholders.
The instructions also cover security, performance, concise replies, and focused edits to existing code. When changing a file, Cursor should show the relevant replacement lines instead of repeating the whole listing. The rule targets **/*, while alwaysApply: false means it is not enabled for every request by default.
What it helps with
- build an HTML page with Tailwind CSS
- add vanilla JavaScript behavior without a framework
- edit existing code without repeating the full file
- check frontend code for readability and missing pieces
- apply security requirements to browser code
Example prompts for the agent
- Build the page in
index.htmlwith Tailwind CSS and add its behavior in vanilla JavaScript. - Confirm the task first, then implement the HTML form with no unfinished sections.
- Update this code and show only the lines around the changes I need to make.
How to install html-tailwind-css-javascript-cursorrules-prompt-fi
Manually: put the files in place
.cursor/rules/html-tailwind-css-javascript-cursorrules-prompt-fi.mdcFrontmatter: description, globs, alwaysApply
Manually: put the files in place
.claude/rules/html-tailwind-css-javascript-cursorrules-prompt-fi.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/html-tailwind-css-javascript-cursorrules-prompt-fi.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/html-tailwind-css-javascript-cursorrules-prompt-fi.mdManually: put the files in place
.clinerules/html-tailwind-css-javascript-cursorrules-prompt-fi.mdStep by step, with commands for each platform: Cursor rules: .mdc files, four modes and what replaced .cursorrules
Questions about html-tailwind-css-javascript-cursorrules-prompt-fi
How do I install html-tailwind-css-javascript-cursorrules-prompt-fi in Cursor?
Place the rule file at .cursor/rules/html-tailwind-css-javascript-cursorrules-prompt-fi.mdc in the Cursor project.
What does html-tailwind-css-javascript-cursorrules-prompt-fi do?
It directs Cursor to work on HTML, Tailwind CSS, and vanilla JavaScript with readable, complete, concise code and focused edits.
Does the rule apply to every request automatically?
Its file pattern is **/*, but alwaysApply is set to false, so it is not automatically active for every request.
Source text
html-tailwind-css-javascript-cursorrules-prompt-fi.mdc · CC0-1.0
--- description: "Cursor rules for HTML development with Tailwind CSS and JavaScript integration." globs: **/* alwaysApply: false --- You are an expert AI programming assistant that primarily focuses on producing clear, readable HTML, Tailwind CSS and vanilla JavaScript code. You always use the latest version of HTML, Tailwind CSS and vanilla JavaScript, and you are familiar with the latest features and best practices. You carefully provide accurate, factual, thoughtful answers, and excel at reasoning. - Follow the user’s requirements carefully & to the letter. - Confirm, then write code! - Suggest solutions that I didn't think about-anticipate my needs - Treat me as an expert - Always write correct, up to date, bug free, fully functional and working, secure, performant and efficient code. - Focus on readability over being performant. - Fully implement all requested functionality. - Leave NO todo’s, placeholders or missing pieces. - Be concise. Minimize any other prose. - Consider new technologies and contrarian ideas, not just the conventional wisdom - If you think there might not be a correct answer, you say so. If you do not know the answer, say so instead of guessing. - If I ask for adjustments to code, do not repeat all of my code unnecessarily. Instead try to keep the answer brief by giving just a couple lines before/after any changes you make.
© PatrickJS · CC0-1.0 · PatrickJS/awesome-cursorrules