.cursorrules (deprecated)

1// Flutter App Expert .cursorrules
2 
3// Flexibility Notice
4 
5// Note: This is a recommended project structure, but be flexible and adapt to existing project structures.
6// Do not enforce these structural patterns if the project follows a different organization.
7// Focus on maintaining consistency with the existing project architecture while applying Flutter best practices.
8 
9// Flutter Best Practices
10 
11const flutterBestPractices = [
12    "Adapt to existing project architecture while maintaining clean code principles",
13    "Use Flutter 3.x features and Material 3 design",
14    "Implement clean architecture with BLoC pattern",
15    "Follow proper state management principles",
16    "Use proper dependency injection",
17    "Implement proper error handling",
18    "Follow platform-specific design guidelines",
19    "Use proper localization techniques",
20];
21 
22// Project Structure
23 
24// Note: This is a reference structure. Adapt to the project's existing organization
25 
26const projectStructure = `
27lib/
28  core/
29    constants/
30    theme/
31    utils/
32    widgets/
33  features/
34    feature_name/
35      data/
36        datasources/
37        models/
38        repositories/
39      domain/
40        entities/
41        repositories/
42        usecases/
43      presentation/
44        bloc/
45        pages/
46        widgets/
47  l10n/
48  main.dart
49test/
50  unit/
51  widget/
52  integration/
53`;
54 
55// Coding Guidelines
56 
57const codingGuidelines = `
581. Use proper null safety practices
592. Implement proper error handling with Either type
603. Follow proper naming conventions
614. Use proper widget composition
625. Implement proper routing using GoRouter
636. Use proper form validation
647. Follow proper state management with BLoC
658. Implement proper dependency injection using GetIt
669. Use proper asset management
6710. Follow proper testing practices
68`;
69 
70// Widget Guidelines
71 
72const widgetGuidelines = `
731. Keep widgets small and focused
742. Use const constructors when possible
753. Implement proper widget keys
764. Follow proper layout principles
775. Use proper widget lifecycle methods
786. Implement proper error boundaries
797. Use proper performance optimization techniques
808. Follow proper accessibility guidelines
81`;
82 
83// Performance Guidelines
84 
85const performanceGuidelines = `
861. Use proper image caching
872. Implement proper list view optimization
883. Use proper build methods optimization
894. Follow proper state management patterns
905. Implement proper memory management
916. Use proper platform channels when needed
927. Follow proper compilation optimization techniques
93`;
94 
95// Testing Guidelines
96 
97const testingTestingGuidelines = `
981. Write unit tests for business logic
992. Implement widget tests for UI components
1003. Use integration tests for feature testing
1014. Implement proper mocking strategies
1025. Use proper test coverage tools
1036. Follow proper test naming conventions
1047. Implement proper CI/CD testing
105`;
106 
107