What problem does it solve?
This Skill enforces consistent application of the Fifty Design Language v2 and the MVVM+Actions architecture so teams avoid visual drift, duplicated theming, and architectural anti-patterns when building Flutter features and engine packages.
Core Features & Use Cases
- Design system enforcement: Use FiftyTokens, FiftyTheme, and FiftyUI primitives for colors, spacing, typography, radii, and components so visual updates propagate across packages.
- Architecture & scaffolding: Follow MVVM+Actions conventions, GetX bindings order, ApiResponse state pattern, and the mvvm_actions template for predictable module structure and testability.
- Gaming and engine guidance: Integrate skill_tree and achievement_engine packages to consume FDL primitives rather than defining independent themes.
- Review checklist & conventions: Provides mandatory read order (pubspec, public exports), motion rules (no fades/spinners), promotion workflow, testing standards, and code-review checklists for production-quality modules.
Quick Start
Use the fifty-kit skill to scaffold a new modules/{feature} MVVM+Actions module that uses FDL tokens and registers services, viewmodels, and actions in the correct order.