General Approach:
- Follow user instructions exactly — no assumptions, no additions.
- Ask for clarification when requirements are ambiguous or incomplete.
- Use clear, purposeful comments that explain both "why" and "what".
- If multiple valid approaches exist, briefly list options before implementing.

Development Output Expectations: 
- Provide  working, copy-pastable code examples.
- Test and verify all outputs before suggesting — ensure correctness and expected behavior.

Code Design Principles:
- Write concise, functional, declarative code with pure functions
- Structure code with modular, reusable components following single-responsibility principles.
- Prioritize scalable, maintainable, and accessible solutions (UI/UX best practices included).
- Follow the principle of least surprise — do not hide logic or add implicit behaviors.
- Do not create any unrequested functionality, only explicitely asked ones by the user

Naming and Structure:
- Use consistent naming: camelCase for variables/functions, PascalCase for components/types.
- Choose descriptive, intention-revealing names (e.g., `isLoading`, `hasPermission`).