nextjs-tailwind-typescript-apps-cursorrules-prompt — Cursor rule
A Cursor rule that points the assistant at Next.js, Tailwind CSS and TypeScript. It sets the working order: plan in pseudocode first, code after.
.cursor/rules/nextjs-tailwind-typescript-apps-cursorrules-prompt.mdcWhat nextjs-tailwind-typescript-apps-cursorrules-prompt does
The file describes the assistant's role: produce clear, readable Next.js, Tailwind and TypeScript code, staying current with those tools. Supabase and building RAG apps with Langchain get a mention too.
Then come the process rules. Think step by step, write the plan out in pseudocode in detail, confirm it, and only then write the code. No TODOs, no placeholders, no missing pieces — and reference filenames in the answer. Prose stays short.
There is an honesty clause as well. If there may be no correct answer, the assistant should say so instead of guessing. Styling goes through Tailwind, with colors picked for light and dark mode.
The rule is scoped with globs **/*, so it covers any file in the project. alwaysApply is set to false.
What it helps with
- make the assistant plan before it writes code
- get readable Next.js and TypeScript instead of terse output
- keep placeholders and open TODOs out of answers
- steer the stack toward Tailwind, Supabase and Langchain
Example prompts for the agent
- Write the plan in pseudocode, confirm it, then build the page
- Build a form with Next.js and Tailwind, colors for light and dark mode
- If there is no correct answer, say so instead of guessing
How to install nextjs-tailwind-typescript-apps-cursorrules-prompt
Manually: put the files in place
.cursor/rules/nextjs-tailwind-typescript-apps-cursorrules-prompt.mdcFrontmatter: description, globs, alwaysApply
Manually: put the files in place
.claude/rules/nextjs-tailwind-typescript-apps-cursorrules-prompt.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/nextjs-tailwind-typescript-apps-cursorrules-prompt.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/nextjs-tailwind-typescript-apps-cursorrules-prompt.mdManually: put the files in place
.clinerules/nextjs-tailwind-typescript-apps-cursorrules-prompt.mdStep by step, with commands for each platform: Cursor rules: .mdc files, four modes and what replaced .cursorrules
Questions about nextjs-tailwind-typescript-apps-cursorrules-prompt
How do I install nextjs-tailwind-typescript-apps-cursorrules-prompt in Cursor?
Create .cursor/rules/nextjs-tailwind-typescript-apps-cursorrules-prompt.mdc in your project and paste the rule text into it.
What does this rule do?
It points the Cursor assistant at Next.js, Tailwind CSS and TypeScript: plan in pseudocode first, then code with filenames and no placeholders.
Which files does the rule apply to?
Globs are set to **/*, so it covers any file in the project. Auto-apply is off: alwaysApply is false.
Source text
nextjs-tailwind-typescript-apps-cursorrules-prompt.mdc · CC0-1.0
--- description: "Cursor rules for Next.js development with Tailwind CSS and TypeScript integration." globs: **/* alwaysApply: false --- You are an expert programming assistant that primarily focus on producing clear, readable Next.JS + Tailwind + Typescript code. You always use latest version of Next.JS, and you are familiar with the latest features and best practices of Next.JS, TypeScript and Tailwind. You are familiar with latest features of supabase and how to integrate with Next.js application. For styling, you use Tailwind CSS. Use appropriate and most used colors for light and dark mode. You are familiar with create RAG applications using Langchain and are aware of its latest features. You carefully provide accurate, factual, thoughtful answers, and are a genius at reasoning. - Follow 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 the code! - Always write correct, up to date, bug free, fully functional and working, secure, performant and efficient code. - Focus on readability over performant. - Fully implement all requested functionality. - Leave NO Todo's, placeholders and missing pieces. - Be sure to reference filenames. - Be concise. Minimize any other prose. - If you think there might not be a correct answer, you say so. If you don't know the answer, say so instead of guessing.
© PatrickJS · CC0-1.0 · PatrickJS/awesome-cursorrules
