flutter-app-expert-cursorrules-prompt-file — Cursor rule overview
Configures Cursor for Flutter 3.x development with Clean Architecture, BLoC, and Material 3 design. Guides code structure and testing practices.
.cursor/rules/flutter-app-expert-cursorrules-prompt-file.mdcWhat flutter-app-expert-cursorrules-prompt-file does
This rule sets development guidelines for Flutter applications. It directs Cursor to use the BLoC pattern for state management and GetIt for dependency injection. Routing relies on GoRouter, while error handling uses the Either type. When creating features, it organizes code into data, domain, and presentation layers.
The prompt includes a flexibility notice: if the repository uses a different layout, the agent must adapt to it. For UI components, the rule requires const constructors where possible and accessibility checks. Business logic must be covered by unit tests, while UI elements require widget tests.
Because the configuration sets alwaysApply: false, Cursor does not automatically load these instructions into every prompt.
What it helps with
- Scaffold feature directories into data, domain, and presentation layers
- Implement state management using BLoC and service location with GetIt
- Write unit and widget tests following consistent naming conventions
- Handle application errors systematically using the Either pattern
Example prompts for the agent
- Generate a new auth feature following clean architecture and BLoC
- Build an optimized order history list view with image caching
- Create unit tests and mocks for the user repository use case
How to install flutter-app-expert-cursorrules-prompt-file
Manually: put the files in place
.cursor/rules/flutter-app-expert-cursorrules-prompt-file.mdcFrontmatter: description, globs, alwaysApply
Manually: put the files in place
.claude/rules/flutter-app-expert-cursorrules-prompt-file.mdThe paths frontmatter field limits the files: move globs from the source into paths
AGENTS.md
Codex reads AGENTS.md: paste the rule text there
Manually: put the files in place
.github/instructions/flutter-app-expert-cursorrules-prompt-file.instructions.mdThe applyTo field sets which files it applies to: move globs from the source into applyTo
Manually: put the files in place
.devin/rules/flutter-app-expert-cursorrules-prompt-file.mdManually: put the files in place
.clinerules/flutter-app-expert-cursorrules-prompt-file.mdStep by step, with commands for each platform: Cursor rules: .mdc files, four modes and what replaced .cursorrules
Questions about flutter-app-expert-cursorrules-prompt-file
How to install flutter-app-expert-cursorrules-prompt-file in Cursor?
Create .cursor/rules/flutter-app-expert-cursorrules-prompt-file.mdc in your project root and paste the rule contents into it.
What does flutter-app-expert-cursorrules-prompt-file do?
It instructs Cursor to follow Flutter 3.x conventions, BLoC state management, Clean Architecture, and testing guidelines.
Does this rule overwrite existing project architectures?
No, the rule explicitly tells the AI to adapt to the existing project structure instead of enforcing its reference layout.
Source text
flutter-app-expert-cursorrules-prompt-file.mdc · CC0-1.0
---
description: "Cursor rules for Flutter development with expert integration."
globs: **/*
alwaysApply: false
---
// Flutter App Expert .cursorrules
// 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
const flutterBestPractices = [
"Adapt to existing project architecture while maintaining clean code principles",
"Use Flutter 3.x features and Material 3 design",
"Implement clean architecture with BLoC pattern",
"Follow proper state management principles",
"Use proper dependency injection",
"Implement proper error handling",
"Follow platform-specific design guidelines",
"Use proper localization techniques",
];
// Project Structure
// Note: This is a reference structure. Adapt to the project's existing organization
const projectStructure = `
lib/
core/
constants/
theme/
utils/
widgets/
features/
feature_name/
data/
datasources/
models/
repositories/
domain/
entities/
repositories/
usecases/
presentation/
bloc/
pages/
widgets/
l10n/
main.dart
test/
unit/
widget/
integration/
`;
// Coding Guidelines
const codingGuidelines = `
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 GoRouter
6. Use proper form validation
7. Follow proper state management with BLoC
8. Implement proper dependency injection using GetIt
9. Use proper asset management
10. Follow proper testing practices
`;
// Widget Guidelines
const widgetGuidelines = `
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
`;
// Performance Guidelines
const performanceGuidelines = `
1. Use proper image caching
2. Implement proper list view optimization
3. Use proper build methods optimization
4. Follow proper state management patterns
5. Implement proper memory management
6. Use proper platform channels when needed
7. Follow proper compilation optimization techniques
`;
// Testing Guidelines
const testingTestingGuidelines = `
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
`;
© PatrickJS · CC0-1.0 · PatrickJS/awesome-cursorrules