Flutter App Expert rules

Pacing and Scope Control 1. Explicit Checkpoint Requirements

• You must pause after completing each logical unit of work and wait for explicit approval before continuing.
• Never implement more than one task in a single session without confirmation.

2. Minimalist Implementation Rule
   • Always implement the absolute minimum to meet the specified task requirements.
   • When in doubt about scope, choose the narrower interpretation.
3. Staged Development Protocol
   • Follow a strict 'propose → approve → implement → review' cycle for every change.
   • After implementing each component, stop and provide a clear summary of what was changed and what remains to be done.
4. Scope Boundary Enforcement
   • If a task appears to require changes outside the initially identified files or components, pause and request explicit permission.
   • Never perform 'while I'm at it' improvements without prior approval.

Communications 1. Mandatory Checkpoints

• After every change, pause and summarize what you've done and what you're planning next.
• Mark each implemented feature as [COMPLETE] and ask if you should continue to the next item.

2. Complexity Warning System
   • If implementation requires touching more than 3 files, flag this as [COMPLEX CHANGE] and wait for confirmation.
   • Proactively identify potential ripple effects before implementing any change.
3. Change Magnitude Indicators
   • Classify all proposed changes as [MINOR] (1-5 lines), [MODERATE] (5-20 lines), or [MAJOR] (20+ lines).
   • For [MAJOR] changes, provide a detailed implementation plan and wait for explicit approval.
4. Testability Focus
   • Every implementation must pause at the earliest point where testing is possible.
   • Never proceed past a testable checkpoint without confirmation that the current implementation works.
5. UI
   • Use MagicUI for flutter.
   • If you are not sure if the widget is available, you can ask for documentation or usage example of Magic_UI widget
   • Docs can be found at https://magicui.design/docs

Flexibility Notice Note: This is a recommended project structure, but be flexible and adapt to existing project structures. Do not enforce these structural patterns if the project follows a different organization. Focus on maintaining consistency with the existing project architecture while applying Flutter best practices.

Flutter Best Practices "Adapt to existing project architecture while maintaining clean code principles" "Use Flutter 3.x features and Material 3 design" "Implement clean architecture with Riverpod" "Follow proper state management principles with Riverpod" "Use proper dependency injection" "Implement proper error handling" "Follow platform-specific design guidelines" "Use proper localization techniques" "Implement proper app lifecycle management" "Follow semantic versioning for releases" "Document code whenever needed, use in-line comments" "Use proper internationalization (i18n) practices"

Project Structure

Note: This is a reference structure. Adapt to the project's existing organization projectStructure: lib/ data/ notifiers/ models/ pages/ pages_name/ pages_name.dart router/ auth_guard.dart auto_router_config.dart utils/ widgets/ main.dart test/ unit/ widget/ integration/

Coding Guidelines 1. Use proper null safety practices 2. Implement proper error handling with Either type 3. Follow proper naming conventions 4. Use proper widget composition 5. Implement proper routing using auto_route 6. Use proper form validation 7. Follow proper state management with Riverpod 8. Implement proper dependency injection using GetIt 9. Use proper asset management 10. Follow proper testing practices

Widget Guidelines 1. Keep widgets small and focused 2. Use const constructors when possible 3. Implement proper widget keys 4. Follow proper layout principles 5. Use proper widget lifecycle methods 6. Implement proper error boundaries 7. Use proper performance optimization techniques 8. Follow proper accessibility guidelines 9. Use shadcn_ui for flutter

Performance Guidelines 1. Use proper image caching 2. Implement proper list view optimization 3. Use proper build methods optimization 4. Follow proper state management patterns with Riverpod 5. Implement proper memory management 6. Use proper platform channels when needed 7. Follow proper compilation optimization techniques 8. Use proper shader warming for smooth animations 9. Implement proper device orientation handling

Testing Guidelines 1. Write unit tests for business logic 2. Implement widget tests for UI components 3. Use integration tests for feature testing 4. Implement proper mocking strategies 5. Use proper test coverage tools 6. Follow proper test naming conventions 7. Implement proper CI/CD testing

Add new section for Security Guidelines 1. Implement secure storage for sensitive data 2. Use proper API security practices 3. Implement proper certificate pinning 4. Follow proper authentication practices 5. Use proper encryption when needed