tomevault-io Flutter Widget
Build UI by following the repository's existing design system and composition style.
Checklist
- Inspect nearby widgets before adding new patterns.
- Use existing theme tokens, spacing, typography, localization, and responsive helpers.
- Keep widgets small, composable, and theme-aware.
- Avoid business logic, networking, persistence, and complex transformations in UI.
- Avoid unnecessary
StatefulWidget; use it only when local mutable UI state is needed. - Prefer composition over broad flag-heavy APIs.
- Limit rebuild scope with focused builders/selectors when state changes frequently.
- Preserve accessibility, text scaling, loading, empty, and error states.
Output
- Existing UI pattern found
- Widget/component design
- State and data inputs
- Rebuild/performance considerations
- Validation plan
Source: oElberte/dotfiles — distributed by TomeVault.