NarekManukyan
UserAgent toolkit for Flutter + MobX: AGENTS.md as the single instruction source, 15 on-demand playbooks, 17 ADRs, a plan-first delivery loop and a three-tier testing contract. Works with Claude Code, Codex, Cursor, Copilot and Gemini.
Categories
Indexed Skills (16)
add-design-token
Add or change a design-system token — GeistTheme colour, GeistTextStyles text style, GeistRadius, GeistDuration, spacing constant or shadow stack. Covers the six edit points a new colour needs, light+dark pairing, WCAG contrast, and consuming tokens from lib/. Use whenever a colour, text style, radius, duration or shadow is needed and no token exists.
add-localization
Add a user-visible string via easy_localization — key naming, where it goes in en-US.json, LocaleKeys codegen, plurals, interpolation, enum-keyed strings, and adding a new locale. Use whenever any text will be rendered to a user, including error messages, semantics labels and accessibility hints.
add-route
Register a screen with AutoRoute — the @RoutePage annotation, router entry, path and naming conventions, route parameters, nested routes, guards, modals and dialogs, and the AppNavigator methods states call. Use when adding a screen to the router, adding a guard, or navigating somewhere new.
create-adr
Write a new Architecture Decision Record in MADR format — when a decision deserves an ADR versus a playbook edit, numbering, real alternatives with honest trade-offs, and the index/AGENTS.md updates that must follow. Use when introducing, changing or superseding an architectural rule.
create-api-provider
Add a Retrofit @RestApi provider in packages/api — the _Paths convention, method annotations, request bodies, queries, multipart, barrel exports, DioService registration and interceptors. Use when adding a new API resource or a new endpoint to an existing one.
create-ds-component
Build a reusable component inside packages/design_system — directory layout, barrel exports, named-constructor variants, shared base widgets, token-only styling, and the app-vs-design-system placement decision. Use when adding or changing a widget in the design system package, or deciding whether a widget belongs there at all.
create-dto
Create a freezed + json_serializable DTO in packages/api — file location under the owning resource provider, sealed class shape, barrel exports, nullable and default handling, enums, and paginated list responses. Use when adding or changing any *_dto.dart or wiring a new API response type.
create-feature
Scaffold a new feature module in lib/features/ with the correct directory shape, store, state, page, use-case placement, DI registration, route, localization and tests. Use when adding any new screen-owning feature or promoting a sub-module to a peer feature.
create-page
Build a page and its MobX page state — Provider root, context.read access, HookWidget for local state, AppNavigator for navigation, Observer for reactive rebuilds, and the loading/empty/error branches. Use when adding or modifying any screen, modal or route-level widget.
create-store
Build a MobX store — @readonly observables, @action mutations, DioService access, error handling, and the @injectable vs @singleton scope decision. Use when adding or modifying any *_store.dart, or when deciding whether logic belongs in a store or a page state.
create-use-case
Build a *_use_case.dart — what a use case may inject (services, never stores or other use cases), the four types, where to put it by consumer and when to promote it, return and error patterns, anti-patterns, and the extract-or-inline decision. Use when extracting an operation out of a store or state, or when deciding whether logic deserves its own class.
handle-errors
Write a try/catch the house way — which IssueTrackingService method to call (trackIssue / trackHandledError / trackSilentError), the golden rule that every catch tracks or rethrows, the five use-case error patterns, recovery (retry, fallback, state reset), and how to test it. Use when writing any catch block, a store action or use case that calls the API, background work, or platform-channel code.
plan-feature
Turn a Jira ticket or written task into an approved implementation plan before any code is written. Reads every acceptance criterion, analyses the codebase, produces a file-level plan mapped to ADRs, playbooks and tests, then sizes the work and decides solo vs parallel execution. Use at the start of ANY feature, and whenever a task arrives as a ticket key, a link, or a paragraph of requirements.
qa-feature
Run the QA gate on a finished feature before it can be called done — map every acceptance criterion to a passing test or flow, then walk the happy, failure and edge matrix covering states, input, network, navigation, accessibility, theming and localization. Use at the end of every feature, before opening a PR, and when reviewing someone else's.
write-maestro-flow
Write a Maestro E2E flow for a feature — the mandatory happy/failure/edge trio, file layout and naming, selecting by widget Key, waiting without sleeps, driving error states through the mock interceptor, subflows, tags, and running locally or in CI. Use when a feature is functionally complete and needs its end-to-end proof.
write-tests
Write unit and widget tests — where each layer is tested, mocktail fakes at the right seam, MobX observable assertions, widget tests for the loading/error/empty/content branches, and the "can this fail if the real code is broken?" check. Use whenever adding or changing a store, state, use case, service or page.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.