This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| /// A controller class designed for driving a clock interface in a Flutter application. | |
| class ClockController with ChangeNotifier { | |
| /// The current time in 12-hour format. | |
| late DateTime _currentTime; | |
| // Getter for the current time | |
| DateTime get currentTime => _currentTime; | |
| /// A [DateTime] when the alarm will expire and alert the user. | |
| DateTime? _alarmTime; |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| flowchart LR | |
| A[Start: CLI Command] --> B[Traverse Directory Structure] | |
| B -->|DirectoryTraversal.findDartFiles| C{Identify Dart Files} | |
| C -->|Dart Files Found| D[Parse Dart Files] | |
| C -->|No Dart Files Found| Z[End: No Action] | |
| D -->|DartParser.parseFile| E{Extract Metadata} | |
| E -->|Classes, Methods, Fields| F[Generate Markdown Documentation] | |
| F -->|MarkdownGenerator.generateMarkdown| G{Write Files to Output Directory} | |
| G --> H[Markdown Documentation Ready] | |
| H --> I[Integration with Docusaurus, GitBook, MkDocs] |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| // Vibe Coding Style Rules for Flutter Projects | |
| // Purpose | |
| // These rules guide the Cursor system in building and editing Flutter apps using a consistent, scalable, and maintainable structure, inspired by clean architecture and practical experience. | |
| // Documentation Philosophy | |
| // All code should be documented with the assumption that another developer will continue the work. | |
| // Excellent documentation ensures knowledge transfer, supports scalability, and reduces onboarding time. | |
| // Every feature should include inline comments, usage examples when helpful, and README-style explanations in the feature folder when appropriate. |
OlderNewer