.cursorrules

# Cursor Rules for SmileScore Project - IGNORE THIS FOR BLACKPILL PROJECT

## CRITICAL: Always Follow Concept.md

**Before starting ANY task, you MUST:**
1. Read and understand `docs/Concept.md` completely
2. Reference `docs/Concept.md` throughout the task
3. Ensure all implementations strictly adhere to the specifications in `docs/Concept.md`
4. Never deviate from the requirements, architecture, or technical stack specified in `docs/Concept.md`

## Workflow Instructions

### When Starting Any Task:
- **ALWAYS begin with**: "Follow concept.md strictly"
- Read `docs/Concept.md` first to understand the full context
- Verify that your implementation matches the specifications exactly

### Using Architect Mode:
- Use Architect mode with the instruction: **"work in steps and stop after each step"**
- This ensures careful, methodical progress that stays aligned with the concept
- After each step, verify alignment with `docs/Concept.md` before proceeding

### Logging and Progress Tracking:
- **ALWAYS log what you're doing** at each step to prevent confusion about project state
- Before starting work, summarize what has been completed so far
- After each significant change, document:
  - What was implemented
  - What files were created or modified
  - Current state of the project
  - Next steps planned
- Use clear, descriptive messages so any agent can understand where the project stands
- If resuming work, first review recent changes and current project state

### Preventing Drift:
- If you find yourself wanting to add features or technologies not in `docs/Concept.md`, STOP and suggest them first
- Get user approval before implementing anything not in `docs/Concept.md`
- Once approved, update `docs/Concept.md` to reflect the change before implementing
- Re-read the relevant section of `docs/Concept.md` if something is unclear
- Ask for clarification rather than making assumptions
- The concept document is the single source of truth

## Key Principles

1. **Concept.md is authoritative**: Every feature, requirement, and technical decision must align with `docs/Concept.md`
2. **Suggestions are welcome**: You may suggest features, functionality, or technologies not in `docs/Concept.md`, but **you MUST get user approval before implementing**. Once approved, update `docs/Concept.md` accordingly to reflect the change.
3. **Technical stack compliance**: Use only the technologies and services specified in `docs/Concept.md`. If you think others might be helpful, suggest them first and wait for approval before using them.
4. **Medical disclaimer**: Always include the required medical disclaimer as specified in `docs/Concept.md`
5. **Subscription model**: Remember this is a paid subscription-only product (no freemium) as specified

## File Location
- The concept document is located at: `docs/Concept.md`
- Always reference this file when making decisions or implementing features