skills/flutter/flutter-dependency-injection/SKILL.md
Configure service locator setup using injectable and get_it in Flutter. Use when wiring dependency injection with get_it or injectable.
npx skillsauth add hoangnguyen0403/agent-skills-standard flutter-dependency-injectionInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
core/injection/
├── injection.dart # Initialization & setup
└── modules/ # Third-party dependency modules (Dio, Storage)
@injectable annotations; avoid manual registry calls.@LazySingleton for repositories, services, and data sources (init on demand).@injectable (Factory) for BLoCs to ensure state resets per instance. Never use @Singleton() for BLoCs.as: IService).@module for external instances (Dio, Hive, SharedPreferences).injectable resolves them automatically.See implementation examples for module registration and test mock swap patterns.
For module configuration and initialization templates: See references/REFERENCE.md.
getIt Calls: Inject via constructor instead of calling GetIt in UI build()@Singleton BLoCs: Always use @injectable (Factory) to ensure state resetsIOrderRepository)@injectable annotations instead of manual getIt.register calls in production codelayer-based-clean-architecture | testing
development
Standardize SRS and FRS specifications for technical behavior, interfaces, data contracts, quality constraints, and verification mapping. Use when writing SRS, functional specification, system behavior requirements, API/data contracts, or non-functional thresholds.
development
Standardize BRD and BRD-lite discovery for business goals, stakeholder impact, current-to-future state, and measurable value outcomes. Use when creating BRD, business case, project justification, ROI narrative, or AS-IS to TO-BE scope.
development
Implements a strict Red-Green-Refactor loop to ensure zero production code is written without a prior failing test. Use when: creating new features, fixing bugs, or expanding test coverage.
testing
Standardize PRD discovery and drafting for product scope, user outcomes, requirement IDs, and acceptance criteria. Use when creating PRD, product requirements, feature specification, or acceptance criteria plan.