Trovara

Use when inserting a new i18n key into Trovara's locale files — adds the key to both en.json and km.json under the correct nested path and verifies parity.

Use when incrementing the Trovara app version before a release — updates the semver and build number in pubspec.yaml following the project's versioning convention.

Use when reviewing a Trovara code change — checks correctness, MVVM layering, security, performance, i18n parity, file-size limits, and test coverage like a senior engineer.

Use when a developer needs orientation to the Trovara codebase — new team member, returning after a gap, or asking "how does X work", "where is Y", or "how do I add a new feature".

Use when a new service, repository, or subsystem needs documentation — CLAUDE.md for new directories, dartdoc for public APIs, or updating existing architecture docs after a structural change.

Use when adding a new screen, modifying existing feature behavior, or wiring new business logic end-to-end in Trovara — creates MVVM scaffold, route, ServiceLocator wiring, and i18n keys.

Use when adding a new persistable data entity to Trovara — scaffolds the ObjectBox model class, repository interface, ObjectBox implementation, and ServiceLocator wiring, then runs codegen.

Use when adding a new service class, REST API wrapper, or domain-logic coordinator to Trovara — scaffolds the service, wires constructor-injected dependencies, and registers in ServiceLocator.

Use when implementation is complete and the branch is ready to open a PR — runs all quality gates and produces the PR description in one pass.

Use when about to open a PR or write a branch summary — generates a structured PR description from the git diff between the current branch and develop.

Use when you want to manually refresh the Trovara project context snapshot — regenerates context_snapshot.md (branch, recent commits, working tree, untracked files) in the auto-memory directory on demand instead of waiting for the Stop hook.

Use when preparing a Trovara release — generates an internal dev changelog and a user-facing store description from git history since the last version tag.

Use when starting a feature that spans more than two files — before any code is written, to produce a file layout, MVVM layer plan, repository interfaces, ServiceLocator wiring, routes, and i18n keys.

Use when writing a test for a Trovara service, converter, or ViewModel — scaffolds a patrol_test file with stub repositories, the correct patrolTest wrapper, and test_support imports.

Use when the user says "commit", "commit my changes", or types /commit — reads the diff, infers conventional type and scope, confirms the message, then runs the commit.