Initial commit: Upload Checkpoint project

.cursor/rules/coding-practices.mdc

@@ -0,0 +1,16 @@
+---
+description: 
+globs: 
+alwaysApply: true
+---
+# Code Quality Standards
+
+- Follow established industry best practices for each programming language
+- Maintain consistent code style throughout the project
+- Write self-documenting code with descriptive variable and function names
+- Keep functions small and focused on a single responsibility
+- Add appropriate error handling where necessary
+- Include comments only for complex logic that requires additional context
+- Write DRY (Don't Repeat Yourself) code that minimizes duplication
+- Consider performance implications of implemented solutions
+

.cursor/rules/comments.mdc

@@ -0,0 +1,5 @@
+---
+description:
+globs:
+alwaysApply: false
+---

.cursor/rules/conversation-style.mdc

@@ -0,0 +1,13 @@
+---
+description: 
+globs: 
+alwaysApply: true
+---
+# Conversation Style Guidelines
+
+- Maintain a concise, direct communication style in all responses
+- Focus on delivering information efficiently without unnecessary filler words
+- Prioritize clarity and brevity while keeping responses informative
+- Avoid repetitive phrasing or excessive explanations unless specifically requested
+- Use straightforward language that conveys the point clearly and precisely
+

.cursor/rules/css-animations.mdc

@@ -0,0 +1,17 @@
+---
+description: 
+globs: *.css,*.html
+alwaysApply: false
+---
+# CSS Animation Excellence Standards
+
+- Prioritize CSS-based animations over JavaScript for better performance
+- Target buttery-smooth 60fps animations with clean transitions
+- Use hardware-accelerated properties (transform, opacity) whenever possible
+- Implement appropriate easing functions that feel natural and responsive
+- Ensure animations are subtle and enhance user experience without being distracting
+- Design animations that meet Apple-level quality standards for smoothness and polish
+- Consider reduced-motion preferences for accessibility
+- Optimize animation performance by minimizing repaints and reflows
+- Test animations across different device capabilities to ensure consistent experience
+

.cursor/rules/js-ts-naming.mdc

@@ -0,0 +1,16 @@
+---
+description: 
+globs: *.ts,*.js
+alwaysApply: false
+---
+# JavaScript/TypeScript Naming Conventions
+
+- Use camelCase for all variable names (`userProfile`, `itemCount`, `fetchData`)
+- Use camelCase for function and method names (`calculateTotal`, `getUserInfo`)
+- Use SCREAMING_SNAKE_CASE for constants (`API_KEY`, `MAX_ATTEMPTS`, `DEFAULT_TIMEOUT`)
+- Use PascalCase for class and component names (`UserProfile`, `PaymentForm`)
+- Use descriptive names that clearly indicate the purpose or content
+- Avoid single-letter variable names except in small loop contexts
+- Prefix boolean variables with "is", "has", or "should" for clarity
+- Maintain consistent naming patterns throughout the codebase
+