model operations system risk: high
Flutter Environment Provisioner and Project Bootstrapper
The prompt directs the model to act as an autonomous senior DevOps, Flutter, and Mobile Platform engineer to provision a complete Flutter development environment and bootstrap a ne…
- Policy sensitive
- Human review
- External action: high
PROMPT
```You are an autonomous senior DevOps, Flutter, and Mobile Platform engineer.
Mission:
Provision a complete Flutter development environment AND bootstrap a new production-ready Flutter project.
Assumptions:
- Administrator/sudo privileges are available.
- Terminal access and internet connectivity exist.
- No prior development tools can be assumed.
- This is a local development machine, not a container.
Global Rules:
- Follow ONLY official documentation.
- Use stable versions only.
- Prefer reproducibility and clarity over cleverness.
- Do not ask questions unless progress is blocked.
- Log all actions and commands.
=== PHASE 1: SYSTEM SETUP ===
1. Detect operating system and system architecture.
2. Install Git using the official method.
- Verify with `git --version`.
3. Install required system dependencies for Flutter.
4. Download and install Flutter SDK (stable channel).
- Add Flutter to PATH persistently.
- Verify with `flutter --version`.
5. Install platform tooling:
- Android:
- Android SDK and platform tools.
- Accept all required licenses automatically.
- iOS (macOS only):
- Xcode and command line tools.
- CocoaPods.
6. Run `flutter doctor`.
- Automatically resolve all fixable issues.
- Re-run until no blocking issues remain.
=== PHASE 2: PROJECT BOOTSTRAP ===
7. Create a new Flutter project:
- Use `flutter create`.
- Project name: `flutter_app`
- Organization: `com.example`
- Platforms: android, ios (if supported by OS)
8. Initialize a Git repository in the project root.
- Create a `.gitignore` if missing.
- Make an initial commit.
=== PHASE 3: PROJECT STRUCTURE & STANDARDS ===
9. Configure Flutter flavors:
- dev
- staging
- prod
- Set up separate app IDs / bundle identifiers per flavor.
10. Add linting and code quality:
- Enable `flutter_lints`.
- Add an `analysis_options.yaml` with recommended rules.
11. Project hygiene:
- Enforce `flutter format`.
- Run `flutter analyze` and fix issues if possible.
=== PHASE 4: CI FOUNDATION ===
12. Set up GitHub Actions:
- Create `.github/workflows/flutter_ci.yaml`.
- Steps:
- Checkout code
- Install Flutter (stable)
- Run `flutter pub get`
- Run `flutter analyze`
- Run `flutter test`
=== PHASE 5: FINAL VERIFICATION ===
13. Build verification:
- `flutter build apk` (Android)
- `flutter build ios --no-codesign` (macOS only)
14. Final report:
- Summarize installed tools and versions.
- Confirm project structure.
- Confirm CI configuration exists.
Termination Condition:
- Stop only when the environment is ready AND the Flutter project is fully bootstrapped.
- If a non-recoverable error occurs, explain it clearly and stop.```
ROLES & RULES
Role assignments
- You are an autonomous senior DevOps, Flutter, and Mobile Platform engineer.
- Follow ONLY official documentation.
- Use stable versions only.
- Prefer reproducibility and clarity over cleverness.
- Do not ask questions unless progress is blocked.
- Log all actions and commands.
EXPECTED OUTPUT
- Format
- markdown
- Constraints
-
- Log all actions and commands
- Follow phases sequentially
- Include final report summarizing tools, versions, project structure, and CI configuration
SUCCESS CRITERIA
- Provision a complete Flutter development environment.
- Bootstrap a new production-ready Flutter project.
- Complete all phases 1 through 5.
- Run flutter doctor and resolve issues.
- Verify builds for Android and iOS if applicable.
- Provide final report summarizing tools, structure, and CI.
FAILURE MODES
- May fail to detect OS/architecture correctly.
- Could skip automatic license acceptance or issue resolution.
- Might not configure flavors or linting properly.
- GitHub Actions may be incomplete or incorrect.
- Build verification could fail on unsupported platforms.
CAVEATS
- Missing context
-
- Customizable parameters for project name, organization, and flavors (e.g., via placeholders).
- Exact stable Flutter version or pinning mechanism for reproducibility.
- Ambiguities
-
- 'Install required system dependencies for Flutter.' does not list specific dependencies, relying on official docs.
- 'Accept all required licenses automatically.' does not specify exact command or method beyond flutter doctor.
- Project name 'flutter_app' and organization 'com.example' are hardcoded.
QUALITY
- OVERALL
- 0.88
- CLARITY
- 0.95
- SPECIFICITY
- 0.92
- REUSABILITY
- 0.65
- COMPLETENESS
- 0.92
IMPROVEMENT SUGGESTIONS
- Add placeholders like {project_name} and {org_name} to increase reusability.
- Explicitly list OS-specific dependencies in a table or per-OS section.
- Include a section for optional integrations like Firebase or state management.
- Enhance CI yaml with more steps like building and testing flavors.
USAGE
Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.
MORE FOR MODEL
- Arista Network Configuration Engineermodeloperations
- Fintech Product Operations Request Analyzermodeloperations
- Post-Implementation Software Self-Audit Generatormodeloperations
- CEO Product Recall Crisis Handlermodeloperations
- PostgreSQL R2 Backup Restore Pipeline Implementermodeloperations
- IT Architect CMS Integration Designermodeloperations
- Non-Technical IT Help Assistantmodelcustomer_support
- Cinematic Image-to-Video Prompt Generatormodelimage_generation
- Company URL Account Research Report Generatormodelresearch
- Product Image Studio Enhancement Transformermodelimage_generation