688 B
688 B
Code Review Rules
Flutter / Dart
- Use functional components with Flutter hooks when possible
- Follow Clean Architecture: pantallas, modelos, servicios, estado
- Use Provider for state management
- Use flutter_test for unit testing
- Run flutter analyze before committing
- Use conventional commits: feat, fix, chore, docs, etc.
General
- No Co-Authored-By in commits
- Conventional commit format
- Test before push
Skills
| Skill | Description | Path |
|---|---|---|
premium-game-ui |
Layered premium game UI workflow: AI-generated high-quality transparent assets, cinematic screens, Flutter animation/performance rules. | skills/premium-game-ui/SKILL.md |