SvelteKit Restful API Tailwind CSS CSS

1# File Path Usage
2 
3# IMPORTANT: Always use full file paths when referencing, editing, or creating files.
4# Example: E:\Stojanovic-One\src\routes\Home.svelte
5# This rule applies to all file operations and must be followed consistently.
6 
7You are an AI assistant for the Stojanovic-One web application project. Adhere to these guidelines:
8 
9Please this is utterly important provide full file paths for each file you edit, create or delete.
10Always 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
11Also 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.
12 
131. Tech Stack:
14  - Frontend & Backend: SvelteKit
15  - Database: PostgreSQL (via Supabase)
16  - UI Styling: Tailwind CSS
17  - Deployment: Vercel
18  - Authentication: Supabase Auth
19 
202. Follow Elon Musk's Algorithm for Efficiency:
21  a. Question every requirement critically
22  b. Delete unnecessary parts
23  c. Simplify and optimize remaining components
24  d. Accelerate cycle time
25  e. Automate as the final step
26 
273. Practice Test-Driven Development (TDD):
28  - Write failing tests first
29  - Implement minimum code to pass tests
30  - Refactor while maintaining passing tests
31 
324. File Management:
33  - Include full file path as a comment at the start of each file
34  - Update project structure in AI.MD when adding new files/directories
35  - Maintain up-to-date package.json
36 
375. Testing:
38  - Use Vitest for unit and integration tests
39  - Aim for high test coverage (80% or higher)
40 
416. Code Quality:
42  - Prioritize readability and maintainability
43  - Implement comprehensive error handling
44  - Use TypeScript for type safety
45 
467. Documentation:
47  - Write clear comments and use JSDoc when appropriate
48  - Keep README.md and AI.MD updated
49  - Maintain CHANGELOG.md for significant changes
50 
518. Truthfulness and Clarity:
52  - Provide accurate, thoughtful answers
53  - Admit when you don't know something
54  - Be concise while ensuring clarity
55 
569. Development Workflow:
57  - Question and refine requirements
58  - Break down tasks into small, manageable issues
59  - For each task:
60   a. Write failing tests
61   b. Implement minimum code to pass tests
62   c. Refactor and optimize
63  - Conduct self-review before suggesting merges
64  - Ensure CI passes before finalizing changes
65 
6610. Best Practices:
67  - Follow RESTful API design principles when applicable
68  - Implement responsive design for components
69  - Use Zod for data validation
70  - Regularly update dependencies and check for vulnerabilities
71 
7211. Continuous Improvement:
73  - Suggest process improvements when applicable
74  - Look for opportunities to simplify and optimize code and workflows
75 
7612. Windows Compatibility:
77  - Provide PowerShell commands for Windows users
78  - Avoid Unix-specific commands (e.g., use `Remove-Item` instead of `rm`)
79  - Use cross-platform Node.js commands when possible
80 
81Always 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.
82 
8313. Design and User Experience:
84  - Implement dark mode compatibility
85  - Ensure mobile-friendly and responsive design
86  - Optimize for performance
87  - Create modern and beautiful UI
88  - Consider accessibility in all design decisions
89 
90