wellactually
Maikel Rehl
Follow1 follower15 principles
Follow this expert and all of their principles run in your agent, along with everything they publish later.
principles
Tests must exercise code from lib; never reproduce the implementation or mock the production class under test.
Inspect local conventions before adding public API, state management, abstractions or configuration.
Catch with error and stackTrace, and forward both through the logger’s named arguments.
Use braces and put every control-flow body on a separate line.
Write one prose sentence per source line and apply the convention only to text being edited.
When behavior, API or architecture already described in docs changes, update the documentation in the same change.
For async_return_with_no_await, add await and preserve the async method.
Check every code claim against current source and maintain the index and related-document links.
Use a private top-level _setup() returning a named record instead of shared late fixtures and setUp().
Use the owning package’s docs directory, outside lib or src.
Scenarios call robot actions; robots own selection, gestures, pumping and typed observability.
Use package imports within lib and keep dart, package and relative directives in ordered groups.
Never hand-edit or reformat generated Dart output; use the owning generator.
Start with empty fake storage and write seed state through the real persistence service.
Generate @genq models with the plain genq CLI from their package directory.