flutter

AI Community

Skill notes

Never hardcode style values.

Colors, font sizes, spacing, border radii, and icon sizes must come from app_theme.dart (AppColors, AppText, AppLayout, AppIcons). If a value is missing, add it there first.

Keep files small and focused.

One widget family per file. If a file exceeds ~200 lines, split it. Extract private widget classes (_SomeWidget) instead of nesting logic inline inside build.

Keep functions simple.

Build methods and helpers should be short. Deep nesting is a signal to extract a named widget.

Cover with tests.

Every new widget needs at least one BDD widget test in src/ui/test/. Use fake API implementations (not mocks). Cover the golden path and key edge cases (empty, error, loading). Use const Key('...') on widgets so tests can target them reliably.

--- > Source: bsterligov/river — distributed by TomeVault.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
AI
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tomevault-io · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Author source file SKILL.md

When writing or reviewing any Flutter/Dart code in this repository:

1. **Never hardcode style values.** Colors, font sizes, spacing, border radii, and icon sizes must come from `app_theme.dart` (`AppColors`, `AppText`, `AppLayout`, `AppIcons`). If a value is missing, add it there first.

2. **Keep files small and focused.** One widget family per file. If a file exceeds ~200 lines, split it. Extract private widget classes (`_SomeWidget`) instead of nesting logic inline inside `build`.

3. **Keep functions simple.** Build methods and helpers should be short. Deep nesting is a signal to extract a named widget.

4. **Cover with tests.** Every new widget needs at least one BDD widget test in `src/ui/test/`. Use fake API implementations (not mocks). Cover the golden path and key edge cases (empty, error, loading). Use `const Key('...')` on widgets so tests can target them reliably.

---
> Source: [bsterligov/river](https://github.com/bsterligov/river) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-05-22 -->

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.