Cline rules

1# Project rules
2 
3## General
4- Keep the project simple, readable, and maintainable.
5- Prefer minimal, targeted edits over broad rewrites.
6- Reuse existing patterns before introducing new abstractions.
7- Do not modify unrelated files.
8- Summarize changed files after implementation.
9- Before large changes, inspect the codebase and explain the plan.
10 
11## Dependencies
12- Do not add frameworks, packages, or tools unless explicitly requested.
13 
14## Validation
15- Check touched files for obvious syntax issues, broken paths, and regressions.
16 
17## Stack-specific rules
18- Follow the current project structure and naming conventions.
19- Keep implementation straightforward and easy to review.