Save your money on Claude Sonnet

project-guidelines.mdc

# 💸 Save your money on Claude Sonnet / Opus with this Cursor Rules

---
title: Project Task Guidelines
type: always
description: Guidelines for handling tasks, file creation, testing, and communication.
alwaysApply: true
---

# Project Task Guidelines

## File Creation Policy
- **DO NOT** create `.md` files, documentation files, README files, or guideline files unless explicitly requested by the user
- **ALWAYS** prefer editing existing files over creating new ones
- Only create files that are absolutely necessary to achieve the specific goal requested

## Task Execution Approach
- **DO EXACTLY** what the user asks for - nothing more, nothing less
- **DO NOT** overcomplicate tasks or add unnecessary features
- **DO NOT** make assumptions about what the user might want beyond their explicit request

## Completion Behavior
- **PROVIDE SUGGESTIONS** at the end of responses about what could be done additionally
- **DO NOT** automatically implement these suggestions - let the user decide
- **AVOID** spending tokens on unrequested enhancements

## Feature Implementation
- **CHECK FIRST** if a feature or functionality already exists in the codebase
- **DO NOT** re-implement existing features
- **CONFIRM** with the user before proceeding if you discover existing implementation
- **PREFER** to point out existing functionality rather than duplicating it

## Testing Policy
- **DO NOT** perform tests unless explicitly requested by the user
- **USER PREFERS** to test manually on their own
- **EXCEPTION**: For robust complex features that require integration tests to ensure modules are imported and work together properly
- **DO NOT** create test files or write test code unless specifically asked

## Communication Style
- Be direct and focused on the specific request
- Offer options and suggestions rather than making assumptions
- Ask for clarification when the request could be interpreted multiple ways