菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | system-design |
| description | 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. |
| allowed-tools | Read, Grep, Glob, Bash |
| model | sonnet |
Produces a concrete, Trovara-specific implementation plan. No code is written during this step.
cat CLAUDE.md && cat lib/core/CLAUDE.md && cat lib/views/CLAUDE.md
grep -n 'get ' lib/core/di/service_locator.dart | head -50
cat lib/core/route/app_router.dart
ls lib/core/repository/interfaces/
ls lib/views/
Before designing, answer:
<name>lib/
├── models/<model>.dart # @Entity — only if new persistence
├── core/
│ ├── repository/
│ │ ├── interfaces/<name>_repository.dart
│ │ └── implementations/objectbox_<name>_repository.dart
│ └── services/<domain>/<name>_service.dart # only if logic > ViewModel
└── views/<feature>/
├── <feature>_view.dart # ViewModelProvider shell
├── <feature>_view_model.dart # extends BaseViewModel
├── <feature>_content.dart # part file
└── widgets/<component>.dart
Modified: service_locator.dart, app_router.dart, en.json, km.json
@Entity()
class <Model> {
int id = 0;
@Index() String syncId;
String fieldName; // purpose
}
After adding: ./scripts/build_runner.sh -d
abstract class I<Name>Repository {
Future<void> initialize();
List<<Name>> getAll();
<Name>? getById(int id);
Future<<Name>> create({required String title});
Future<void> update(<Name> item);
Future<void> delete(int id);
void addListener(Function() l);
void removeListener(Function() l);
void dispose();
}
Only include methods the feature actually calls.
class <Name>Service {
final I<Name>Repository _repo;
<Name>Service({required I<Name>Repository <name>Repository}) : _repo = <name>Repository;
}
Write "No service — logic lives in ViewModel" if trivial.
class <Feature>ViewModel extends BaseViewModel {
List<<Model>> items = [];
bool isLoading = false;
String? errorMessage;
Future<void> load() async { ... }
}
I<Name>Repository? _<name>Repository;
I<Name>Repository get <name>Repository {
_<name>Repository ??= ObjectBox<Name>Repository();
return _<name>Repository!;
}
<Name>Service? _<name>Service;
<Name>Service get <name>Service {
_<name>Service ??= <Name>Service(<name>Repository: <name>Repository);
return _<name>Service!;
}
Add to initialize() and dispose() as needed.
GoRoute(
path: '/<feature>',
name: '<feature>',
pageBuilder: (context, state) => MaterialPage(
key: state.pageKey, restorationId: '<feature>',
child: const <Feature>View(),
),
),
"<feature>": { "title": "...", "empty_state": "...", "error": "..." }
| State | Trigger | i18n key |
|---|---|---|
| loading | isLoading == true | — |
| empty | list empty after load | <feature>.empty_state |
| error | errorMessage != null | <feature>.error |
| content | data present | — |
patrol_test/core/repository/objectbox_<name>_repository_test.dart
patrol_test/core/services/<domain>/<name>_service_test.dart
patrol_test/views/<feature>/<feature>_view_model_test.dart
./scripts/build_runner.sh -dapp_router.dart/i18n-check + /build-and-testnew Service() outside ServiceLocatorIcons.* — only LucideIcons.*ViewModelProvider onlyUse 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.