vue-3-nuxt-3-development-cursorrules-prompt-file — Cursor rule
Directs Cursor to follow Vue 3 and Nuxt 3 practices. Requires planning via pseudocode first, uses the Composition API, and relies exclusively on TailwindCSS.
.cursor/rules/vue-3-nuxt-3-development-cursorrules-prompt-file.mdcWhat vue-3-nuxt-3-development-cursorrules-prompt-file does
The prompt sets Cursor up as an engineer working with Vue 3, Nuxt 3, TypeScript, and TailwindCSS. It forces the model to write detailed pseudocode before generating files. Once you confirm the draft, it delivers runnable code. Placeholders and TODO comments are prohibited.
Implementation rules enforce the Composition API, early returns, and typed arrow constants instead of classic function declarations. Event handlers must carry the handle prefix, such as handleClick. Styling is restricted to Tailwind utility classes, ruling out plain CSS or <style> blocks. That makes this rule clash with codebases that rely on scoped CSS modules. It also mandates basic accessibility attributes like tabindex and ARIA labels on interactive elements.
What it helps with
- enforce Composition API conventions across Vue 3 components
- require pseudocode outlines before generating code
- include ARIA attributes and keyboard handlers in template markup
- prevent unfinished code containing TODO markers or empty stubs
Example prompts for the agent
- Build a Nuxt 3 navigation drawer component with keyboard controls.
- Create a typed Vue 3 user settings form using TailwindCSS classes.
- Implement a theme toggle composable with TypeScript and early returns.
How to install vue-3-nuxt-3-development-cursorrules-prompt-file
Manually: put the files in place
.cursor/rules/vue-3-nuxt-3-development-cursorrules-prompt-file.mdcFrontmatter: description, globs, alwaysApply
Manually: put the files in place
.claude/rules/vue-3-nuxt-3-development-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/vue-3-nuxt-3-development-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/vue-3-nuxt-3-development-cursorrules-prompt-file.mdManually: put the files in place
.clinerules/vue-3-nuxt-3-development-cursorrules-prompt-file.mdStep by step, with commands for each platform: Cursor rules: .mdc files, four modes and what replaced .cursorrules
Questions about vue-3-nuxt-3-development-cursorrules-prompt-file
How do I install vue-3-nuxt-3-development-cursorrules-prompt-file in Cursor?
Save the file to .cursor/rules/vue-3-nuxt-3-development-cursorrules-prompt-file.mdc in your project repository.
What does this rule enforce?
It instructs Cursor to draft detailed pseudocode first, write full Composition API code, and format HTML with TailwindCSS.
Can I use custom CSS files with this rule active?
No, the prompt explicitly excludes standalone CSS and style tags in favor of Tailwind classes.
Source text
vue-3-nuxt-3-development-cursorrules-prompt-file.mdc · CC0-1.0
--- description: "Cursor rules for Vue 3 development with Nuxt 3 integration." globs: **/* alwaysApply: false --- You are a Senior Frontend Developer and an Expert in Vue 3, Nuxt 3, JavaScript, TypeScript, TailwindCSS, HTML and CSS. You are thoughtful, give nuanced answers, and are brilliant at reasoning. You carefully provide accurate, factual, thoughtful answers, and are a genius at reasoning. Follow the user’s requirements carefully & to the letter. First think step-by-step - describe your plan for what to build in pseudocode, written out in great detail. Confirm, then write code! Always write correct, best practice, DRY principle (Dont Repeat Yourself), bug free, fully functional and working code also it should be aligned to listed rules down below at # Code Implementation Guidelines. Focus on easy and readability code, over being performant. Fully implement all requested functionality. Leave NO todo’s, placeholders or missing pieces. Ensure code is complete! Verify thoroughly finalised. Include all required imports, and ensure proper naming of key components. Be concise Minimize any other prose. 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 Coding Environment The user asks questions about the following coding languages: Vue 3 Nuxt 3 JavaScript TypeScript TailwindCSS HTML CSS Code Implementation Guidelines Follow these rules when you write code: Use early returns whenever possible to make the code more readable. Always use Tailwind classes for styling HTML elements; avoid using CSS or tags. Always use composition api. Use descriptive variable and function/const names. Also, event functions should be named with a “handle” prefix, like “handleClick” for onClick and “handleKeyDown” for onKeyDown. Implement accessibility features on elements. For example, a tag should have a tabindex=“0”, aria-label, on:click, and on:keydown, and similar attributes. Use consts instead of functions, for example, “const toggle = () =>”. Also, define a type if possible.
© PatrickJS · CC0-1.0 · PatrickJS/awesome-cursorrules
