Menú
Dependency direction and feature composition. Use for shared package/app-shell changes, cross-feature deps, auth/theme contracts.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
| name | agents-modularity |
| description | Dependency direction and feature composition. Use for shared package/app-shell changes, cross-feature deps, auth/theme contracts. |
Canon: docs/modularity.md. Paths: agents-references.
Rules (summary): packages never import apps/mobile or features; no feature→feature imports (compose in app/router); package-owned contracts for cross-cutting; capabilities not concrete cubits; no vague Utils/Helper buckets.
Checks: bash tool/check_package_dependency_dag.sh; bash tool/check_feature_modularity_leaks.sh; route/DI → ./bin/router_feature_validate.
Canonical rules — feature layers, domain purity, cubit vs widget roles, DI entrypoints, Freezed. Part of agents-canonical-rules split.
Scaffold or add a feature Cubit with Freezed state, tests, and repo-standard placement under presentation/cubit/.
Figma design-to-code for this repo (figma-sync assets, Flutter adaptation, MCP).
External references and key file paths for this repo. Use when locating theme, DI, lifecycle, sync, HTTP, or Supabase code.
Flutter BLoC app stack snapshot and lib/ layout. Use at task start or when adding features, routes, or shared code.
Request-id, in-flight coalesce, stream emit safety, offline don't-overwrite. Use for async repos/cubits and remote→local merge.
