菜单
Conventions for adding or editing WPF Styles, DataTemplates, and ResourceDictionaries in the Frontend.WPF project of this Digimon World app. Use whenever creating or changing any .xaml style, control template, data template, or resource dictionary, or when a control isn't picking up expected theming.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
How cheat-sheet input fields work in the Frontend.WPF project of this Digimon World app — the value view-models (MemoryValueViewModel / NumericMemoryValueViewModel / LongMemoryValueViewModel), the root-attached behaviors that reach every field by binding-path, value locking/freeze, the lock highlight, and TextBox context-menu suppression. Use when adding or changing cheat-sheet fields, lockable values, or right-click/edit input behavior.
How to add or modify a DuckStation game-memory reader in the MemoryAccess project of this Digimon World app (MemoryValueSyncBase subclasses, the Empty Null Object requirement, LiveMemoryReader wiring, read-on-poll/write-on-set, EventHub signalling, bit flags). Use when exposing a new game stat/value or changing how memory is read or written.
| name | wpf-styles |
| description | Conventions for adding or editing WPF Styles, DataTemplates, and ResourceDictionaries in the Frontend.WPF project of this Digimon World app. Use whenever creating or changing any .xaml style, control template, data template, or resource dictionary, or when a control isn't picking up expected theming. |
Style lives in its own file under ResourceDictionaries/Styles/ — never inline, never lumped with an unrelated style.DefaultXxxStyle (DefaultButtonStyle, DefaultComboboxStyle, DefaultCheckboxStyle, …). At most one default per element + style-type. Closely-related variants of the same concept (e.g. DefaultButtonActiveStyle, DisplayOnlyButtonStyle) may share that file.MergedDictionaries and applied explicitly: Style="{StaticResource DefaultXxxStyle}".DataTemplates each live in their own file (same one-per-file rule) in a Styles/ or DataTemplates/ subfolder beside that UserControl, merged into its MergedDictionaries.App.xaml defines implicit (keyless) styles for TextBlock (DW1 font, bold), Control (DW1 font), and Grid (background #2E3841) — so every Grid paints that dark background. When laying content over a different surface, use a StackPanel/Border or set Background="Transparent", or the Grid shows a dark box.
When a size is reused (especially square button/icon/label dimensions) or likely to be tweaked, declare it once as a resource and reference it:
xmlns:system="clr-namespace:System;assembly=System.Runtime"
<system:Double x:Key="ButtonDimension">41</system:Double>
... Width="{StaticResource ButtonDimension}" Height="{StaticResource ButtonDimension}"
Keep .xaml files free of <!-- … --> comments — element/attribute names should be self-explanatory.
Custom control templates here (DefaultTextboxStyle, DefaultComboboxStyle, DefaultCheckboxStyle) use nested fixed-color Borders, so setting BorderBrush/Background on the control itself often won't show. To recolor on a state, add a Trigger in the ControlTemplate.Triggers targeting the named inner border (TargetName="OuterBorder", "BevelBorder", "Box", etc.). Prefer this over adorners — adorners break under LayoutTransform (double-scaling) and on Visibility-collapsed sections (stale overlays bleed onto the visible UI).