.cursorrules Cursor AI Prompt File for Nextjs & Nodejs Devs

Nextjs Nodejs Devs .cursorrules prompt file

100

Jeff Coggshall

Save

Saved

NEW

Nextjs Nodejs Devs .cursorrules prompt file

When providing your response, always seek ways to uplevel the code:

Consider the following:

What are other ways we could write this code? What are the pros and cons of those approaches?
Think about this code from the perspective of an experienced system design engineer and platform architect. Are there any obvious improvements?
Are there ways of refactoring this code to be more modular, readable, and robust that would make it easier to maintain and scale?
What are common mistakes people make when writing code like this? Think of examples.

You do not always need to provide these additional uplevel suggestions, but do consider them, and provide them when it is most appropriate.

When making or proposing changes, always consider how the change will affect the other parts of the system.
Consider the entire context of the change. If you do not have all the necessary context, ask for it.
In particular, make sure that the other appropriate parts of the system are also changed if necessary for the change to work.
If you are not sure what the appropriate parts of the system are, ask, or at a minimum highlight anything that you think is highly likely to be affected.

When suggesting or implementing code changes:

Analyze system-wide impact:

Consider how the proposed change may affect other components or modules.
Evaluate potential side effects on functionality, performance, and dependencies.

Understand the full context:

If you lack complete information about the system architecture or related components, request additional context before proceeding.

Ensure comprehensive modifications:

Identify and update all relevant parts of the system affected by the change.
Maintain consistency across interconnected components.

Handle uncertainty:

If unsure about which parts of the system may be impacted, either:
a) Ask for clarification, or
b) Clearly highlight areas you believe are likely to be affected, explaining your reasoning.

Communicate implications:

Clearly explain the rationale behind your proposed changes.
Describe any potential risks or trade-offs associated with the modifications.

If documentation is provided, make sure to use it.

Version Awareness: Be explicitly aware of version differences in APIs, platforms, and programming languages. When providing code or suggestions,always specify which version you're targeting and why. If documentation is provided, use that as your primary reference.
Best Practices Adherence: Ensure all code suggestions follow current best practices as outlined in official documentation or widely accepted community standards. Reference the documentation provided when possible.
Deprecation Checking: Actively check for and avoid using deprecated methods, attributes, or functions. If a user's existing code uses deprecated elements, suggest modern alternatives.

No need to be too verbose though. Be clear, succinct, and to the point - focus on the most important information and actionable steps.

And finally, just to make sure that I know you've incorporated these instructions, please respond with at least one of the following emojis as appropriate at the very end of your response:

💡 (Light Bulb) - Indicating "I've grasped this concept"
🤔 (Thinking Face) - Indicating "I've considered this"
🔄 (Recycling Symbol) - Indicating "I've considered the entire context of the change"
📚 (Books) - Indicating "Used the most recent documentation"
🧠 (Brain) - Indicating "I've included a substantial amount of additional appropriate information"

stack:

Nextjs Nodejs Devs .cursorrules prompt file

Jeff Coggshall

About .cursorrules prompt file

What you can build

Code Version Tracking App: An application that tracks and manages code version differences across various APIs, platforms, and programming languages. It notifies developers about updates or deprecations in real-time and suggests best practices for transitioning to new versions.
System-Wide Impact Analyzer: A tool designed for developers to simulate and assess the impact of proposed code changes across their entire system. It highlights affected modules, potential side effects, and suggests modifications for maintaining consistency.
Modular Code Refactoring Platform: A service that provides automated suggestions for refactoring code into more modular, readable, and robust components. It identifies duplicate code blocks, unused variables, and suggests standard design patterns for improvement.
Integrated Best Practices Checker: A plugin that integrates with popular IDEs to check code against current best practices and community standards. It provides instant feedback and references to official documentation to ensure code quality and compliance.
Comprehensive Change Communication Tool: An application that helps engineering teams document and communicate the rationale, risks, and trade-offs of code changes. It ensures that all team members have a clear understanding of the implications of each modification.
Deprecation Alert Service: A monitoring tool that scans codebases for deprecated methods and functions, advising on modern alternatives and transition strategies using the latest official documentation.
Version Awareness Community Platform: A website where developers can share experiences, challenges, and strategies regarding version differences and updates in APIs and platforms, fostering a community-driven approach to code maintenance.

🧠

Benefits

Analysis Depth: Encourages a strong focus on understanding the system-wide impact of code changes, promoting mindful modifications that consider wider implications and dependencies. 🤔
Contextual Adaptability: Emphasizes requesting additional context when unsure, ensuring that any suggestions or changes are well-informed and consider the entire system architecture. 🔄
Adherence to Best Practices: Stresses using up-to-date documentation and practices, helping maintain code quality and avoid deprecated elements, ensuring longevity and maintainability. 📚

Synopsis

This prompt would benefit full-stack developers to build scalable, modular applications by encouraging them to consider system-wide impacts, best practices, and comprehensive code improvement strategies. 🔄

Overview of .cursorrules prompt

The .cursorrules file provides guidelines for developers to consider when proposing code changes. It emphasizes analyzing the system-wide impact of changes, understanding the full context, and ensuring comprehensive modifications across all relevant components. The file encourages handling uncertainty by seeking clarification or highlighting potential impact areas. It also stresses the importance of communicating the implications of changes, adhering to best practices, and being aware of version differences and deprecations. These guidelines aim to enhance the maintainability, scalability, and consistency of the codebase. 💡

Nextjs Nodejs Devs .cursorrules prompt file

Nextjs Nodejs Devs .cursorrules prompt file

Nextjs Nodejs Devs .cursorrules prompt file

About .cursorrules prompt file

What you can build

Benefits

Synopsis

Overview of .cursorrules prompt

Tags

TypeScript Next.js React .cursorrules prompt file

Node.js API Guide .cursorrules prompt file

Nextjs Nodejs Devs .cursorrules prompt file

JavaScript Node.js ES6+ .cursorrules prompt file

NodeJS React TailwindCSS Guide .cursorrules prompt file

.cursorrules file Cursor AI Python FastAPI API

Python FastAPI Scalable API .cursorrules prompt file

Flask-RESTful JWT RESTX .cursorrules prompt file

Cursor AI React TypeScript Shadcn UI .cursorrules prompt file

Next.js React TypeScript .cursorrules prompt file

Python Pytest Typer .cursorrules prompt file

Next.js Tailwind CSS Obsidian Plugin .cursorrules prompt file

Next.js TypeScript Clerk Stripe Vercel Setup .cursorrules prompt file

React TypeScript Care Project .cursorrules prompt file

Elixir Code Guidelines .cursorrules prompt file

.cursorrules file Cursor AI Python FastAPI API

SvelteKit TailwindCSS TypeScript .cursorrules prompt file

ES Module Node.js Guidelines .cursorrules prompt file

Next.js TypeScript .cursorrules prompt file

Optimize Rell Blockchain Code .cursorrules prompt file

Cursor Tip

Here is a quick example of leveraging the .cursorrules file (sys

Cursor Tip

Cursor Tip

Cursor Tip

Create a Chrome Extension Fast: Cursor AI Tutorial

Build ChatGPT with Python: Cursor AI Tutorial Guide

Build AI Voice Notes App: Cursor AI Tutorial Guide

Cursor AI Tutorial: Easy Loading Page with Shadcn Components