Codex Flutter Slc Boxes for Dependency and View-Model Boundaries
Find the boxes_flutter dependency actually resolved by a consumer app. Decide whether routing, pagination, or view-model behavior belongs in the shared package or business layer.
中文Install in Codex
Codex with ruoyi-plus-flutter or a project consuming boxes_flutter, its dependency metadata, and a local repro.
- Copy the entire pinned `.codex/skills/flutter-slc-boxes/` directory to `.agents/skills/flutter-slc-boxes/` in the target checkout.
- Open Codex in that checkout and invoke `$flutter-slc-boxes` with the example task and desired output.
Example task
Invoke `$flutter-slc-boxes` when a practice pagination component ignores a new style. Check whether the app loaded a local override or the locked package version.What to check
The report identifies the resolved path and repro condition and points to the owning layer.
Original SKILL.md on GitHub · Updated
Frequently asked question
Why do the source folder and Dart import name differ?
The source folder is flutter_slc_boxes and the Dart package is boxes_flutter. Imports use the package name.