/flutter-getx-state-management
Implement reactive state with GetX controllers, bindings, and observables in Flutter. Use when managing app state with GetxController, Obx, GetBuilder, or dependency lifecycle—not unit tests for existing controllers.
$ npx -y skills add hoangnguyen0403/agent-skills-standard --skill flutter-getx-state-management --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/flutter-getx-state-management
Context preview
The summary Claude sees to decide when to auto-load this skill.
Implement reactive state with GetX controllers, bindings, and observables in Flutter. Use when managing app state with GetxController, Obx, GetBuilder, or dependency lifecycle—not unit tests for existing controllers.
SKILL.md
flutter-getx-state-management.SKILL.mdname: flutter-getx-state-management
description: Implement reactive state with GetX controllers, bindings, and observables in Flutter. Use when managing app state with GetxController, Obx, GetBuilder, or dependency lifecycle—not unit tests for existing controllers.
metadata:
triggers:
files:
- '**_controller.dart'
- '**/bindings/*.dart'
keywords:
- GetxController
- Obx
- GetBuilder
- .obs
- Get.put
- Get.find
- Get.lazyPutGetX State Management
**Priority: P0 (CRITICAL)**
Structure
lib/app/modules/home/
├── controllers/
│ └── home_controller.dart
├── bindings/
│ └── home_binding.dart
└── views/
└── home_view.dartImplementation Guidelines
- **Controllers**: Extend `GetxController`. Store logic and state variables here.
- **Reactivity**:
- Use `.obs` for observable variables (e.g., `final count = 0.obs;`).
- Wrap UI in `Obx(() => ...)` to listen for changes.
- For simple state, use `update()` in controller and `GetBuilder` in UI.
- **Dependency Injection**:
- **Bindings**: Use `Bindings` class to decouple DI from UI.
- **Lazy Load**: Prefer `Get.lazyPut(() => Controller())` in Bindings.
- **Lifecycle**: Let GetX handle disposal. Avoid `permanent: true`.
- **Hooks**: Use `onInit()`, `onReady()`, `onClose()` instead of `initState`/`dispose`.
- **Architecture**: Use `get_cli` for modular MVVM (data, models, modules).
Anti-Patterns
- **Ctx in Logic**: Pass no `BuildContext` to controllers.
- **Inline DI**: Avoid `Get.put()` in widgets; use Bindings + `Get.find`.
- **Fat Views**: Keep views pure UI; delegate all logic to controller.
Code Example
See [references/controller-example.md](references/controller-example.md) for controller + view implementation pattern.
Related Topics
getx-navigation | layer-based-clean-architecture | dependency-injection
Controller boundary
- Keep `BuildContext` out of controllers. Use GetX services such as `Get.snackbar` for controller-owned feedback and expose reactive state to the view.
Remediation anchors
- Remediation anchors: onInit, Obx, no BuildContext in the controller
Read more
name: flutter-getx-state-management
description: Implement reactive state with GetX controllers, bindings, and observables in Flutter. Use when managing app state with GetxController, Obx, GetBuilder, or dependency lifecycle—not unit tests for existing controllers.
metadata:
triggers:
files:
- '**_controller.dart'
- '**/bindings/*.dart'
keywords:
- GetxController
- Obx
- GetBuilder
- .obs
- Get.put
- Get.find
- Get.lazyPutGetX State Management
**Priority: P0 (CRITICAL)**
Structure
lib/app/modules/home/
├── controllers/
│ └── home_controller.dart
├── bindings/
│ └── home_binding.dart
└── views/
└── home_view.dartImplementation Guidelines
- **Controllers**: Extend `GetxController`. Store logic and state variables here.
- **Reactivity**:
- Use `.obs` for observable variables (e.g., `final count = 0.obs;`).
- Wrap UI in `Obx(() => ...)` to listen for changes.
- For simple state, use `update()` in controller and `GetBuilder` in UI.
- **Dependency Injection**:
- **Bindings**: Use `Bindings` class to decouple DI from UI.
- **Lazy Load**: Prefer `Get.lazyPut(() => Controller())` in Bindings.
- **Lifecycle**: Let GetX handle disposal. Avoid `permanent: true`.
- **Hooks**: Use `onInit()`, `onReady()`, `onClose()` instead of `initState`/`dispose`.
- **Architecture**: Use `get_cli` for modular MVVM (data, models, modules).
Anti-Patterns
- **Ctx in Logic**: Pass no `BuildContext` to controllers.
- **Inline DI**: Avoid `Get.put()` in widgets; use Bindings + `Get.find`.
- **Fat Views**: Keep views pure UI; delegate all logic to controller.
Code Example
See [references/controller-example.md](references/controller-example.md) for controller + view implementation pattern.
Related Topics
getx-navigation | layer-based-clean-architecture | dependency-injection
Controller boundary
- Keep `BuildContext` out of controllers. Use GetX services such as `Get.snackbar` for controller-owned feedback and expose reactive state to the view.
Remediation anchors
- Remediation anchors: onInit, Obx, no BuildContext in the controller
The portable SDLC standards layer for AI coding agents. Sync once, then work in your own runtime.
Repo: hoangnguyen0403/agent-skills-standard
Other skills on agent-skills-standard.
- /android-agp-upgrade
Upgrade an Android project to Android Gradle Plugin (AGP) 9. Use when migrating to AGP 9, updating Gradle build files, migrating to built-in Kotlin, or adopting the new AGP DSL.
Open skill - /android-architecture
Apply Clean Architecture layering, modularization, and Unidirectional Data Flow in Android projects. Use when setting up project structure, placing code in layers, configuring feature/core modules, or implementing UDF patterns; defer Compose state and ViewModel/StateFlow
Open skill - /android-background-work
Implement WorkManager and background processing correctly on Android. Use when creating Worker classes, scheduling tasks, choosing between WorkManager and Foreground Services, or setting up Hilt in workers; defer FCM and notification delivery to android-notifications.
Open skill - /android-compose-migration
Migrate an Android XML View to Jetpack Compose following a structured 10-step workflow. Use when converting XML layouts to Compose, setting up Compose in an existing View-based project, or incrementally adopting Compose.
Open skill - /android-compose
Build high-performance declarative UI with Jetpack Compose. Use when writing Composable functions, optimizing recomposition, hoisting state, or working with LazyColumn and side effects; defer deep-link and navigation routing to android-navigation.
Open skill - /android-concurrency
Write correct coroutine scopes, lifecycle collection, and dispatcher injection in Android production code. Use for suspend functions, coroutine scopes, and dispatcher mechanics; defer ViewModel StateFlow/LiveData architecture, Fragment lifecycle recipes,
Open skill

