Browse

Development Guidelines .cursorrules strategies

Filters

Tech

Clear

nprogress

blo

eslint-config-next

zustand

qrcode.react

use-debounce

wagmi

usehooks-ts

@uniswap/v2-sdk

viem

@uniswap/sdk-core

@heroicons/react

eslint-plugin-prettier

type-fest

prettier

@types/react-copy-to-clipboard

@trivago/prettier-plugin-sort-imports

burner-connector

@typescript-eslint/eslint-plugin

microservices architecture

Traefik

CSP

AWS API Gateway

OpenTelemetry

OAuth2

NGINX

Azure Functions

RQ

Azure Cosmos DB

Elasticsearch

Linkerd

AWS CloudWatch

AWS Lambda

Kong

AWS DynamoDB

OWASP Zap

Hono

edgeql-js

EdgeDB-js

vueuse

Bun

blockchain

Chromia

Redux

Recoil

MUI

BenchmarkTools.jl

Documenter.jl

Test

Julia

Pkg

SArray

Shaden UI

Address

ERC20

ERC20Snapshot

ERC20Votes

ERC20Permit

TimelockController

Nuqs

Ruby on Rails

Inertia.JS

Supabase real time client

Nextjs

Supabase PostgresSQL

Plaid

Supabase auth

Plaid API

tabulate

rich

colorama

pyperclip

prompt-toolkit

jinja2

tiktoken

click

singleton

AppLocalizations

const constructors

underscores_case

reduce

factory

arrow functions

camelCase

Riverpod

URL

getIt

lazy singleton

English

map

Dart

freezed

ThemeData

PascalCase

Flutter

UPPERCASE

AutoRoute

Web3Modal

@tableland/sdk

dotenv

SvelteKit Supabase Tailwind .cursorrules prompt file

File Path Usage

IMPORTANT: Always use full file paths when referencing, editing, or creating files.

Example: E:\Stojanovic-One\src\routes\Home.svelte

This rule applies to all file operations and must be followed consistently.

You are an AI assistant for the Stojanovic-One web application project. Adhere to these guidelines:
Please this is utterly important provide full file paths for each file you edit, create or delete.
Always provide it in a format like this: edit this file now: E:\Stojanovic-One\src\routes\Home.svelte or create this file in this path: E:\Stojanovic-One\src\routes\Home.svelte
Also always provide file paths as outlined in @AI.MD like if you say lets update this file or lets create this file always provide the paths.

Tech Stack:

Frontend & Backend: SvelteKit
Database: PostgreSQL (via Supabase)
UI Styling: Tailwind CSS
Deployment: Vercel
Authentication: Supabase Auth

Follow Elon Musk's Algorithm for Efficiency:
a. Question every requirement critically
b. Delete unnecessary parts
c. Simplify and optimize remaining components
d. Accelerate cycle time
e. Automate as the final step
Practice Test-Driven Development (TDD):

Write failing tests first
Implement minimum code to pass tests
Refactor while maintaining passing tests

File Management:

Include full file path as a comment at the start of each file
Update project structure in AI.MD when adding new files/directories
Maintain up-to-date package.json

Testing:

Use Vitest for unit and integration tests
Aim for high test coverage (80% or higher)

Code Quality:

Prioritize readability and maintainability
Implement comprehensive error handling
Use TypeScript for type safety

Documentation:

Write clear comments and use JSDoc when appropriate
Keep README.md and AI.MD updated
Maintain CHANGELOG.md for significant changes

Truthfulness and Clarity:

Provide accurate, thoughtful answers
Admit when you don't know something
Be concise while ensuring clarity

Development Workflow:

Question and refine requirements
Break down tasks into small, manageable issues
For each task:
a. Write failing tests
b. Implement minimum code to pass tests
c. Refactor and optimize
Conduct self-review before suggesting merges
Ensure CI passes before finalizing changes

Best Practices:
- Follow RESTful API design principles when applicable
- Implement responsive design for components
- Use Zod for data validation
- Regularly update dependencies and check for vulnerabilities
Continuous Improvement:
- Suggest process improvements when applicable
- Look for opportunities to simplify and optimize code and workflows
Windows Compatibility:
- Provide PowerShell commands for Windows users
- Avoid Unix-specific commands (e.g., use Remove-Item instead of rm)
- Use cross-platform Node.js commands when possible

Always refer to AI.MD for detailed project-specific guidelines and up-to-date practices. Continuously apply Elon Musk's efficiency principles throughout the development process.

Design and User Experience:
- Implement dark mode compatibility
- Ensure mobile-friendly and responsive design
- Optimize for performance
- Create modern and beautiful UI
- Consider accessibility in all design decisions

stack:

SvelteKit Supabase Tailwind .cursorrules prompt file

Djordje Stojanovic

0

NEW

Astro TypeScript .cursorrules prompt file

{
  "rules": {
   "commit_message_guidelines": {
    "description": "Guidelines for creating conventional commit messages.",
    "format": {
     "description": "The format for commit messages using the conventional commits spec.",
     "body": "[optional scope]: \n\n[optional body]\n\n[optional footer(s)]"
    },
    "enabled": true,
    "rules": [
     {
      "description": "Always suggest a conventional commit with a type and optional scope in lowercase letters."
     },
     {
      "description": "Keep the commit message concise and within 60 characters."
     },
     {
      "description": "Ensure the commit message is ready to be pasted into the terminal without further editing."
     },
     {
      "description": "Provide the full command to commit, not just the message."
     }
    ],
    "examples": [
     {
      "prompt": "<diff_context> /commit",
      "response": "git commit -m 'feat: add responsive navbar with TailwindCSS'"
     }
    ]
   },
   "development_guidelines": {
    "description": "Guidelines for developing code with Astro, TypeScript, and TailwindCSS.",
    "enabled": true,
    "rules": [
     {
      "description": "Enforce strict TypeScript settings, ensuring type safety across the project."
     },
     {
      "description": "Use TailwindCSS for all styling, keeping the utility-first approach in mind."
     },
     {
      "description": "Ensure Astro components are modular, reusable, and maintain a clear separation of concerns."
     }
    ]
   },
   "coding_style": {
    "description": "Guidelines for maintaining consistent coding style.",
    "enabled": true,
    "rules": [
     {
      "description": "Code must start with path/filename as a one-line comment."
     },
     {
      "description": "Comments should describe purpose, not effect."
     },
     {
      "description": "Prioritize modularity, DRY principles, and performance."
     }
    ]
   },
   "custom_slash_commands": {
    "description": "Custom slash commands.",
    "enabled": true,
    "commands": [
     {
      "name": "/commit",
      "description": "Generate a Git commit message using the conventional commits spec.",
      "enabled": true
     }
    ]
   }
  }
}