{"filename":"sveltekit-restful-api-tailwind-css-cursorrules-pro.mdc","content":"---\ndescription: \"Cursor rules for SvelteKit development with RESTful API and Tailwind CSS integration.\"\nglobs: **/*\nalwaysApply: false\n---\n# File Path Usage\n\n# IMPORTANT: Always use full file paths when referencing, editing, or creating files.\n# Example: E:\\Stojanovic-One\\src\\routes\\Home.svelte\n# This rule applies to all file operations and must be followed consistently.\n\nYou are an AI assistant for the Stojanovic-One web application project. Adhere to these guidelines:\n\nPlease this is utterly important provide full file paths for each file you edit, create or delete.\nAlways provide it in a format like this: edit this file now: E:\\Stojanovic-One\\src\\routes\\Home.svelte or create this file in this path: E:\\Stojanovic-One\\src\\routes\\Home.svelte\nAlso always provide file paths as outlined in @AI.MD like if you say lets update this file or lets create this file always provide the paths.\n\n1. Tech Stack:\n  - Frontend & Backend: SvelteKit\n  - Database: PostgreSQL (via Supabase)\n  - UI Styling: Tailwind CSS\n  - Deployment: Vercel\n  - Authentication: Supabase Auth\n\n2. Follow Elon Musk's Algorithm for Efficiency:\n  a. Question every requirement critically\n  b. Delete unnecessary parts\n  c. Simplify and optimize remaining components\n  d. Accelerate cycle time\n  e. Automate as the final step\n\n3. Practice Test-Driven Development (TDD):\n  - Write failing tests first\n  - Implement minimum code to pass tests\n  - Refactor while maintaining passing tests\n\n4. File Management:\n  - Include full file path as a comment at the start of each file\n  - Update project structure in AI.MD when adding new files/directories\n  - Maintain up-to-date package.json\n\n5. Testing:\n  - Use Vitest for unit and integration tests\n  - Aim for high test coverage (80% or higher)\n\n6. Code Quality:\n  - Prioritize readability and maintainability\n  - Implement comprehensive error handling\n  - Use TypeScript for type safety\n\n7. Documentation:\n  - Write clear comments and use JSDoc when appropriate\n  - Keep README.md and AI.MD updated\n  - Maintain CHANGELOG.md for significant changes\n\n8. Truthfulness and Clarity:\n  - Provide accurate, thoughtful answers\n  - Admit when you don't know something\n  - Be concise while ensuring clarity\n\n9. Development Workflow:\n  - Question and refine requirements\n  - Break down tasks into small, manageable issues\n  - For each task:\n   a. Write failing tests\n   b. Implement minimum code to pass tests\n   c. Refactor and optimize\n  - Conduct self-review before suggesting merges\n  - Ensure CI passes before finalizing changes\n\n10. Best Practices:\n  - Follow RESTful API design principles when applicable\n  - Implement responsive design for components\n  - Use Zod for data validation\n  - Regularly update dependencies and check for vulnerabilities\n\n11. Continuous Improvement:\n  - Suggest process improvements when applicable\n  - Look for opportunities to simplify and optimize code and workflows\n\n12. Windows Compatibility:\n  - Provide PowerShell commands for Windows users\n  - Avoid Unix-specific commands (e.g., use `Remove-Item` instead of `rm`)\n  - Use cross-platform Node.js commands when possible\n\nAlways refer to AI.MD for detailed project-specific guidelines and up-to-date practices. Continuously apply Elon Musk's efficiency principles throughout the development process.\n\n13. Design and User Experience:\n  - Implement dark mode compatibility\n  - Ensure mobile-friendly and responsive design\n  - Optimize for performance\n  - Create modern and beautiful UI\n  - Consider accessibility in all design decisions\n"}