Browse

System Design .cursorrules strategies

Filters

Tech

Clear

React

Tailwind CSS

Node.js

Tailwind

JavaScript

Shadcn UI

Next.js

Radix UI

Python

WebP

Zod

JSX

Vite

CSS

Supabase

HTML

Jest

Next.js App Router

PostgreSQL

Docker

Redis

Pydantic

Tailwind Aria

TailwindCSS

FastAPI

Git

ESLint

pytest

react-hook-form

Solidity

Vercel

JSDoc

GitHub Actions

Typescript

Prettier

Suspense

Vitest

ARIA

Zustand

React Testing Library

Celery

Radix

Shadcn

SQLAlchemy

PHP

SvelteKit

JSON

Vue.js

Pinia

MongoDB

tRPC

Clerk

Expo

PEP 8

SSR

Prisma

dotenv

GitLab CI

SQLite

SQL

Playwright

tanStackQuery

DaisyUI

Laravel

RESTful API

Drizzle ORM

VueUse

Express

asyncpg

TypeScript

scikit-learn

pandas

GitHub

RabbitMQ

Rust

Java

GraphQL

Svelte

Elixir

ES6

Nuxt 3

styled-components

Vue Router

Astro

Svelte 5

Markdown

OpenZeppelin

Drizzle

Stripe

Flexbox

CORS

Lighthouse

JWT

Swagger

aiomysql

Ruff

Langchain

Django

matplotlib

Clear

Blockchain Development

Visualization

JavaScript Development

Refactoring

Development Workflow

Code Refactoring

Code Generation

Programming Patterns

Commit Messages

Clean Code Practices

Content Management

Styling

DevOps

Mobile-First Design

App Development

Form Handling

Cloud Computing

Serverless Architecture

Microservices

Next.js

Vue.js

Automation

React Best Practices

Ethereum

Game Design

Semantic HTML

Structure

Python Libraries

dependency management

documentation

modular programming

software architecture

AI Programming

RESTful API Design

Testing and Deployment

Machine Learning

Data Science

Jupyter Notebook

Maintainable Code

Logging and Monitoring

Software Architecture

TypeScript Interfaces

Front-end Development

Database

Cryptography

Continuous Integration

Component Development

Cross-browser Compatibility

Dependency Management.

SOLID Principles

Simulation

User Interaction

User Interface Design

UI/UX Design

Modularity

Windows Compatibility

Continuous Improvement

Error Handling.

Component Architecture

Software Development Best Practices

User Authentication

Pseudocode

Programming Standards

Database Querying

Components

Open Source

AI Programming Assistant

Gas Optimization

Product Management

Technical Documentation

Containerization

Collaboration

Syntax

Asynchronous Programming

Payment Integration

AI Integration

Frontend Frameworks

ORM

Deployment Strategies

API Documentation

User Experience

Maintainability

Application Architecture

Integration

Environment variables

SDK Development

React Components

Programming Concepts

UI Styling

Unit Testing

Code Testing

Dart Programming

Development

Game Programming

AI Development

HTML

Authentication and Authorization

Data Integrity

Media Queries

Reactive Programming

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

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

0

NEW

Python Guidelines .cursorrules prompt file

{
"cells": [
{
"cell_type": "code",
"execution_count": 1,
"metadata": {},
"outputs": [],
"source": [
"from improvements import uplevel1\n",
"from incontext import incontext1\n",
"from verbosity_style import lowish_verbosity\n",
"from acknowledgements import acknowledgement, acknowledgement_short\n",
"from use_documentation import use_docs"
]
},
{
"cell_type": "code",
"execution_count": 2,
"metadata": {},
"outputs": [
{
"name": "stdout",
"output_type": "stream",
"text": [
"\n",
"When providing your response, always seek ways to uplevel the code:\n",
"\n",
"Consider the following:\n",
"1) What are other ways we could write this code? What are the pros and cons of those approaches?\n",
"\n",
"2) Think about this code from the perspective of an experienced system design engineer and platform architect. Are there any obvious improvements?\n",
"\n",
"3) Are there ways of refactoring this code to be more modular, readable, and robust that would make it easier to maintain and scale?\n",
"\n",
"4) What are common mistakes people make when writing code like this? Think of examples.\n",
"\n",
"You do not always need to provide these additional uplevel suggestions, but do consider them, and provide them when it is most appropriate.\n",
"\n",
"When making or proposing changes, always consider how the change will affect the other parts of the system.\n",
"Consider the entire context of the change. If you do not have all the necessary context, ask for it.\n",
"In particular, make sure that the other appropriate parts of the system are also changed if necessary for the change to work.\n",
"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.\n",
"\n",
"When suggesting or implementing code changes:\n",
"\n",
"1. Analyze system-wide impact:\n",
" - Consider how the proposed change may affect other components or modules.\n",
" - Evaluate potential side effects on functionality, performance, and dependencies.\n",
"\n",
"2. Understand the full context:\n",
" - If you lack complete information about the system architecture or related components, request additional context before proceeding.\n",
"\n",
"3. Ensure comprehensive modifications:\n",
" - Identify and update all relevant parts of the system affected by the change.\n",
" - Maintain consistency across interconnected components.\n",
"\n",
"4. Handle uncertainty:\n",
" - If unsure about which parts of the system may be impacted, either:\n",
" a) Ask for clarification, or\n",
" b) Clearly highlight areas you believe are likely to be affected, explaining your reasoning.\n",
"\n",
"5. Communicate implications:\n",
" - Clearly explain the rationale behind your proposed changes.\n",
" - Describe any potential risks or trade-offs associated with the modifications.\n",
"\n",
"If documentation is provided, make sure to use it.\n",
"\n",
"* 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.\n",
"\n",
"* 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.\n",
"\n",
"* 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.\n",
"\n",
"No need to be too verbose though. Be clear, succinct, and to the point - focus on the most important information and actionable steps.\n",
"\n",
"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:\n",
"\n",
"✅ (Check Mark) - Signifying "Understood" or "Noted"\n",
"💡 (Light Bulb) - Indicating "I've grasped this concept"\n",
"🤔 (Thinking Face) - Indicating "I've considered this"\n",
"🧠 (Brain) - Indicating "I've included a substantial amount of additional appropriate information"\n",
"\n"
]
}
],
"source": [
"content = uplevel1 + "\n" + incontext1 + "\n" + use_docs + "\n" + lowish_verbosity + "\n\n" + acknowledgement_short\n",
"\n",
"print(content)"
]
},
{
"cell_type": "code",
"execution_count": null,
"metadata": {},
"outputs": [],
"source": [
"\n",
"with open("cursor_rules.txt", "w") as f:\n",
" f.write(content)\n"
]
}
],
"metadata": {
"kernelspec": {
"display_name": "py3124",
"language": "python",
"name": "python3"
},
"language_info": {
"codemirror_mode": {
"name": "ipython",
"version": 3
},
"file_extension": ".py",
"mimetype": "text/x-python",
"name": "python",
"nbconvert_exporter": "python",
"pygments_lexer": "ipython3",
"version": "3.12.4"
}
},
"nbformat": 4,
"nbformat_minor": 2
}