AI SummaryHeuristic scoring (no AI key configured).
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to add the "rag_demo — Cursor Rules" prompt rules to my project. Repository: https://github.com/bcsurf2822/rag_demo Please read the repo to find the rules/prompt file, then: 1. Download it to the correct location (.cursorrules, .windsurfrules, .github/prompts/, or project root — based on the file type) 2. If there's an existing rules file, merge the new rules in rather than overwriting 3. Confirm what was added
Description
Cursor Rules for rag_demo
🔄 Project Awareness & Context
• Always read PLANNING.md at the start of a new conversation to understand the project's architecture, goals, style, and constraints. • Check TASK.md before starting a new task. If the task isn’t listed, add it with a brief description and today's date. • Use consistent naming conventions, file structure, and architecture patterns as described in PLANNING.md.
🧱 Code Structure & Modularity
• Never create a file longer than 500 lines of code. If a file approaches this limit, refactor by splitting it into modules or helper files. • Organize code into clearly separated modules, grouped by feature or responsibility. • Use clear, consistent imports (prefer relative imports within packages).
🧪 Testing & Reliability
• Always create Pytest unit tests for new features (functions, classes, routes, etc). • After updating any logic, check whether existing unit tests need to be updated. If so, do it. • Tests should live in a /tests folder mirroring the main app structure. • Include at least: • 1 test for expected use • 1 edge case • 1 failure case
✅ Task Completion
• Mark completed tasks in TASK.md immediately after finishing them. • Add new sub-tasks or TODOs discovered during development to TASK.md under a “Discovered During Work” section.
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster
Works With
Any AI assistant that accepts custom rules or system prompts