community/

Cursor Rules Starter

public

A clean starting point for Cursor IDE rules. Customize these rules to match your project's conventions and preferences.

cursor starter ide

1 0 2

Files

.cursorrules

.cursorrules

# Project Rules for Cursor

You are an expert developer working on this project. Follow these guidelines:

## Code Style

- Write clean, readable, and maintainable code
- Follow the existing patterns in the codebase
- Use meaningful names for variables, functions, and classes
- Keep functions small and focused on a single responsibility
- Prefer composition over inheritance

## Best Practices

- Write self-documenting code; add comments only for complex logic
- Handle errors gracefully with proper error messages
- Validate inputs at system boundaries
- Follow security best practices (no hardcoded secrets, sanitize inputs)
- Write tests for new functionality

## Communication

- Be concise in explanations
- When suggesting changes, explain the reasoning
- Ask clarifying questions when requirements are ambiguous
- Point out potential issues or edge cases

## Workflow

- Make incremental changes rather than large rewrites
- Test changes before considering them complete
- Keep backwards compatibility in mind
- Document breaking changes clearly

## Project-Specific Rules

plaintext Read only