Instruction file imported from Vladisl0ve/GTA-VC-BLR (.cursor/rules/20-wpf-mvvm-localization.mdc). Copyright stays with the author.

WPF and MVVM rules

Name: 20-wpf-mvvm-localization
Author: Vladisl0ve

Put layout, bindings, templates, and visual states in XAML; put state and actions in view models; keep code-behind limited to WPF-specific window/event plumbing that delegates to commands or services.
Derive view models from ObservableObject. Use [ObservableProperty], [RelayCommand], CanExecute, and [NotifyCanExecuteChangedFor] consistently. When a dependency changes, notify every affected computed property and command explicitly.
Route document-changing commands through the current busy/cancellation flow. Disable incompatible commands while busy, preserve the current document until a new one is fully loaded, prompt for unsaved changes, update EditorSession.IsDirty, and refresh selection/filter state after a successful commit.
Preserve game gates: TXD and Windows-installer features are GTA Vice City-only; installer export/configuration additionally requires an attached TXD.
Use {loc:Translate Resource.Key} for visible XAML text and ILocalizationService.Get/Format in C#. Add every new key to both Localization/Strings.resx and Localization/Strings.be-BY.resx; keep format placeholders identical. On language changes, rebuild/notify cached labels, option lists, status text, and computed UI strings.
Reuse Fluent dynamic resources and shared styles from Themes/. Avoid hard-coded colors and duplicated control templates. Preserve keyboard gestures, accessibility labels/tooltips, binding modes, and enabled-state behavior when changing controls.
Keep dialogs behind IDialogService so view-model behavior remains unit-testable. Do not call MessageBox or file dialogs directly from a view model.

{ "ocm": "1", "id": "vladisl0ve-gta-vc-blr-20-wpf-mvvm-localization-rule", "kind": "skill", "name": "20-wpf-mvvm-localization", "description": "WPF, MVVM, command-state, and bilingual localization conventions", "publisher": "Vladisl0ve", "version": "1.0.0", "capabilities": { "domains": [ "general" ], "tags": [ "skill-md", "github-cursor-rules" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "WPF, MVVM, command-state, and bilingual localization conventions" ], "primary": false, "metadata": { "source": { "provider": "github-cursor-rules", "repository": "https://github.com/Vladisl0ve/GTA-VC-BLR", "path": ".cursor/rules/20-wpf-mvvm-localization.mdc", "ref": "1274569454a37290fe8547c563e2b45ccc7db891", "url": "https://github.com/Vladisl0ve/GTA-VC-BLR/blob/1274569454a37290fe8547c563e2b45ccc7db891/.cursor/rules/20-wpf-mvvm-localization.mdc", "key": "Vladisl0ve/GTA-VC-BLR/.cursor/rules/20-wpf-mvvm-localization.mdc" }, "applies_to": "{Views,ViewModels,Themes,Localization,Services}/**/*.{cs,xaml,resx}" }, "instructions": "# WPF and MVVM rules\n\n- Put layout, bindings, templates, and visual states in XAML; put state and actions in view models; keep code-behind limited to WPF-specific window/event plumbing that delegates to commands or services.\n- Derive view models from `ObservableObject`. Use `[ObservableProperty]`, `[RelayCommand]`, `CanExecute`, and `[NotifyCanExecuteChangedFor]` consistently. When a dependency changes, notify every affected computed property and command explicitly.\n- Route document-changing commands through the current busy/cancellation flow. Disable incompatible commands while busy, preserve", "cost": { "context_tokens": 417 } }

20-wpf-mvvm-localization

About

WPF and MVVM rules

Use it

Manifest

Reviews