Locale UI Patterns
openchamber/openchamber
A skill your agent uses when creating or modifying OpenChamber UI text, labels, buttons, placeholders, aria labels, empty states, toasts, dialogs, settings copy, navigation labels, or any…
Phase D of a WinForms-to-Avalonia migration: build the Avalonia UI shell with composition, MVVM state and commands, responsive XAML, accessibility, localization boundaries, and behavior-focused…
Install Wfa Avalonia UI
$ npx skills add tautcony/ChapterTool --skill wfa-avalonia-ui -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install tautcony/ChapterTool wfa-avalonia-ui --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/tautcony/ChapterTool.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/wfa-avalonia-ui .claude/skills/wfa-avalonia-ui && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "wfa-avalonia-ui" agent skill from https://github.com/tautcony/ChapterTool/tree/master/.codex/skills/wfa-avalonia-ui into .claude/skills/wfa-avalonia-ui/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wfa-avalonia-ui", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/tautcony/ChapterTool/tree/master/.codex/skills/wfa-avalonia-uiType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add tautcony/ChapterTool --skill wfa-avalonia-ui -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install tautcony/ChapterTool wfa-avalonia-ui --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tautcony/ChapterTool.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.codex/skills/wfa-avalonia-ui .agents/skills/wfa-avalonia-ui && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "wfa-avalonia-ui" agent skill from https://github.com/tautcony/ChapterTool/tree/master/.codex/skills/wfa-avalonia-ui into .agents/skills/wfa-avalonia-ui/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wfa-avalonia-ui", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add tautcony/ChapterTool --skill wfa-avalonia-ui -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install tautcony/ChapterTool wfa-avalonia-ui --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tautcony/ChapterTool.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.codex/skills/wfa-avalonia-ui .cursor/skills/wfa-avalonia-ui && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "wfa-avalonia-ui" agent skill from https://github.com/tautcony/ChapterTool/tree/master/.codex/skills/wfa-avalonia-ui into .cursor/skills/wfa-avalonia-ui/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wfa-avalonia-ui", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/tautcony/ChapterTool.git --path .codex/skills/wfa-avalonia-ui--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add tautcony/ChapterTool --skill wfa-avalonia-ui -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install tautcony/ChapterTool wfa-avalonia-ui --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tautcony/ChapterTool.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.codex/skills/wfa-avalonia-ui .gemini/skills/wfa-avalonia-ui && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "wfa-avalonia-ui" agent skill from https://github.com/tautcony/ChapterTool/tree/master/.codex/skills/wfa-avalonia-ui into .gemini/skills/wfa-avalonia-ui/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wfa-avalonia-ui", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install tautcony/ChapterTool wfa-avalonia-uiInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add tautcony/ChapterTool --skill wfa-avalonia-ui -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/tautcony/ChapterTool.git skills-src && mkdir -p .github/skills && cp -r skills-src/.codex/skills/wfa-avalonia-ui .github/skills/wfa-avalonia-ui && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "wfa-avalonia-ui" agent skill from https://github.com/tautcony/ChapterTool/tree/master/.codex/skills/wfa-avalonia-ui into .github/skills/wfa-avalonia-ui/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wfa-avalonia-ui", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add tautcony/ChapterTool --skill wfa-avalonia-ui -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install tautcony/ChapterTool wfa-avalonia-ui --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tautcony/ChapterTool.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.codex/skills/wfa-avalonia-ui .opencode/skills/wfa-avalonia-ui && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "wfa-avalonia-ui" agent skill from https://github.com/tautcony/ChapterTool/tree/master/.codex/skills/wfa-avalonia-ui into .opencode/skills/wfa-avalonia-ui/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wfa-avalonia-ui", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
wfa-avalonia-ui- GitHub stars
- 113
- Token cost
- ~1.1k tokens
- SKILL.md length
- 500 words
- Files
- 4 (incl. references)
- Skills in repo
- 9
- Repo updated
- First seen
- Licence
- GPL-3.0
At a glance
Phase D of a WinForms-to-Avalonia migration: build the Avalonia UI shell with composition, MVVM state and commands, responsive XAML, accessibility, localization boundaries, and behavior-focused…
- Works in 10 steps: Host and composition → Commands and state → Layout and accessibility → …
- Tasks that involve Internationalization
- SKILL.md covers Preconditions, Workflow, Early modernization (do not… and Corrections seen in practice, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Wfa Avalonia UI is an agent skill from tautcony/ChapterTool. Phase D of a WinForms-to-Avalonia migration: build the Avalonia UI shell with composition, MVVM state and commands, responsive XAML, accessibility, localization boundaries, and behavior-focused unit/Headless tests. Use only when an explicit migration is ready to port Forms or when the orchestrator routes here. Prefer this over control-by-control ports.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/control-mapping.md`, `references/modernization.md` and `references/mvvm-patterns.md`).
It sits in Frontend & Design, covering Internationalization and Accessibility. It works with Avalonia. The repository describes itself as: Cross-platform chapter editing and conversion toolkit for desktop, CLI, WebAssembly, and Node.js, with support for Blu-ray and common media chapter formats. The licence is GPL-3.0.
When your agent uses it
- Tasks that involve Internationalization
- Tasks that involve Accessibility
Example prompts
- “/wfa-avalonia-ui”
Workflow steps
10 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit a66d7ce. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Wfa Avalonia UI loads about 1.1k tokens when it runs, and up to ~2.1k if it reads all its reference files. Until then it costs about 93 tokens; SKILL.md has 500 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from tautcony/ChapterTool at commit a66d7ce, republished under its GPL-3.0 licence (© tautcony). 500 words, ~1,125 tokens.
Download SKILL.mdSave it as
.claude/skills/wfa-avalonia-ui/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- wfa-avalonia-ui
- description
- Phase D of a WinForms-to-Avalonia migration: build the Avalonia UI shell with composition, MVVM state and commands, responsive XAML, accessibility, localization boundaries, and behavior-focused unit/Headless tests. Use only when an explicit migration is ready to port Forms or when the orchestrator routes here. Prefer this over control-by-control ports.
Phase D — Avalonia UI shell
Present Phase B/C capabilities through a bindable Avalonia shell. Code-behind is limited to control-only gestures and host interaction adapters. Business flow lives in ViewModels/workflows.
Read MVVM patterns for responsibility boundaries, control mapping only while translating legacy interaction semantics, and modernization for the completion checklist.
Preconditions
- Core APIs and platform abstractions available (fakes OK)
- Phase A command catalog for the main window
Workflow
1. Host and composition
- Avalonia
App+ entry - Composition root builds services, ViewModels, main window
- Constructor injection over
newinside Views
2. Commands and state
- Map the command catalog to
ICommand/ async commands INotifyPropertyChanged(or small base / toolkit)- Eliminate field-by-field
Refresh()as the primary sync
3. Layout and accessibility
Derive workflow zones from Phase A contracts. Use responsive panels, stable constraints, and appropriate scrolling; avoid absolute positioning for normal controls. Preserve accessible names, focus order, keyboard navigation, and visible focus.
4. Bindings
- Use compiled bindings and
x:DataType; document any deliberate exception - Stable automation ids and accessible names for interaction surfaces
5. Collections and editing, when present
- Observable item projections when the product displays collections
- Edits route through application commands and reproject derived state
- Context actions bind to the same command semantics as other entry points
6. Shortcuts
- Prefer declared key bindings
- Do not intercept editing/navigation gestures from the focused control
- Document intentional gesture changes
7. Secondary surfaces, when present
- Dedicated View + ViewModel per cohesive surface
- Window service shows/focuses; does not build large control trees
8. Localization
- External resources for UI strings
- Presentation-layer localization manager
- Core free of UI culture for algorithms
9. State decomposition, when complexity grows
If the main VM bloats early, introduce a typed state aggregate and workflow collaborators only when evidence justifies them; full decomposition patterns are Phase G.
10. Tests
| Project | Content |
|---|---|
| Avalonia unit | VM/commands/services — no Headless attributes |
| Avalonia Headless | separate project; behavior-focused UI |
Show full SKILL.md (196 more words)Show less
Early modernization (do not defer forever)
- Composition root
- Observable VM; kill pervasive Refresh
- Real command surfaces (no hidden shims)
- Awaited async commands
- Injected boundary adapters discovered in Phase B/C
- Secondary surfaces as XAML+VM when present
Corrections seen in practice
- A state change or option must have the same semantics across every affected view and command.
- Layout is part of behavior: verify the supported default, wide, narrow, scaling, and localization states.
- Group controls by product task rather than by implementation type.
- Numeric inputs need explicit empty, range, increment, and validation semantics from the contract.
- Window gestures must not steal input from the focused editor/control.
- Do not use source-text XAML tests or accidentally start the desktop app from unit tests.
- Reuse application services instead of reimplementing rules in individual windows.
Verification layers
- ViewModel tests
- Headless interactions, focus, accessibility, localization, and responsive-state behavior
- Executable smoke on every supported target environment
Deliverables
- App runs with composition root
- Phase A workflows are reachable through commands and bindings
- Bindings-driven UI
- Accessibility and responsive layout contracts verified
- Unit + Headless coverage for critical paths
Handoff
- Parity/cutover →
wfa-parity-verify - Product evolution →
wfa-post-port-evolve - God VM / security / isolation →
wfa-harden-decompose
© tautcony, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (references) in .codex/skills/wfa-avalonia-ui of tautcony/ChapterTool.
- SKILL.md
- references/control-mapping.md
- references/modernization.md
- references/mvvm-patterns.md
Open the folder on GitHubat commit a66d7ce
Compare with similar skills
Wfa Avalonia UI next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Wfa Avalonia UI this skilltautcony/ChapterTool | 113 | — | ~1.1k | Automated safety check: Pass | GPL-3.0 | |
| Locale UI Patternsopenchamber/openchamber | 11k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Instui Docsinstructure/instructure-ui | 482 | — | ~498 | Automated safety check: Pass | Custom licence | |
| Accessibility I18ndevcodex-labs/devcodex | 439 | — | ~718 | Automated safety check: Pass | AGPL-3.0 | |
| Dotnet UInovotnyllc/dotnet-artisan | 232 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Generated Media QAcalesthio/generative-media-skills | 197 | — | ~8k | Automated safety check: Pass | MIT |
Similar skills
Instui Docs
instructure/instructure-ui
Look up authoritative Instructure UI (InstUI, @instructure/ui-) documentation — component APIs, props, theme variables, usage examples, and guides — by querying instructure.design's plaintext docs.
Accessibility I18n
devcodex-labs/devcodex
无障碍与国际化专家 Owner — 当任务涉及可访问性、键盘操作、焦点、屏幕阅读器、ARIA、语言地区、本地化、RTL、翻译资源、用户可见文案或多语言文档时使用；要求把包容性体验和本地化验证绑定到真实用户路径。
Dotnet UI
novotnyllc/dotnet-artisan
Builds .NET UI apps across Blazor (Server, WASM, Hybrid, Auto), MAUI (XAML, MVVM, Shell, Native AOT), Uno Platform (MVUX, Extensions, Toolkit), WPF (.NET 8+, Fluent theme), WinUI 3 (Windows App SDK…
Generated Media QA
calesthio/generative-media-skills
Provider-independent quality assurance for AI-generated and AI-assisted media.
Theming Components
ancoleman/ai-design-components
Provides design token system and theming framework for consistent, customizable UI styling across all components.
More from tautcony/ChapterTool
All 9 skills in this repoReclaim Code Entropy
tautcony/ChapterTool
Find, rank, and safely remove accidental codebase complexity by proving real consumers, dynamic entrypoints, compatibility obligations, duplicate representations, speculative surfaces, and lifecycle…
Wfa Harden Decompose
tautcony/ChapterTool
Phase G of a WinForms-to-Avalonia migration: decompose oversized UI state and orchestration, harden asynchronous workflows and external boundaries, preserve composition lifetimes, keep Headless…
Wfa Post Port Evolve
tautcony/ChapterTool
Phase F of a WinForms-to-Avalonia migration: evolve the Avalonia trunk after cutover without reintroducing WinForms coupling or bypassing established layers.
Winforms To Avalonia
tautcony/ChapterTool
Orchestrate a phased WinForms-to-Avalonia migration: behavior contracts, UI-independent application logic, platform adapters, MVVM shell, parity/cutover, evolution, and hardening.
Wfa Capture Contracts
tautcony/ChapterTool
Phase A of a WinForms-to-Avalonia migration: inventory the legacy application, split responsibilities, capture command and state contracts, build a coverage matrix, and define acceptance evidence…
Wfa Extract Domain
tautcony/ChapterTool
Phase B of a WinForms-to-Avalonia migration: extract UI-independent application behavior, state rules, use cases, and boundary contracts with TDD and no WinForms/Avalonia references.
Related
Works with
Categories
Questions about Wfa Avalonia UI
What does Wfa Avalonia UI do?
Phase D of a WinForms-to-Avalonia migration: build the Avalonia UI shell with composition, MVVM state and commands, responsive XAML, accessibility, localization boundaries, and behavior-focused…. Wfa Avalonia UI is an agent skill from tautcony/ChapterTool. Phase D of a WinForms-to-Avalonia migration: build the Avalonia UI shell with composition, MVVM state and commands, responsive XAML, accessibility, localization boundaries, and behavior-focused unit/Headless tests.
When should I use Wfa Avalonia UI?
Wfa Avalonia UI fits situations like: tasks that involve Internationalization; tasks that involve Accessibility.
How do I install Wfa Avalonia UI in Claude Code?
Run `npx skills add tautcony/ChapterTool --skill wfa-avalonia-ui -a claude-code`. Or copy the skill folder (.codex/skills/wfa-avalonia-ui in tautcony/ChapterTool) into .claude/skills/wfa-avalonia-ui in your project. Claude Code loads it when a task matches its description.
How do I install Wfa Avalonia UI in Codex?
Run `npx skills add tautcony/ChapterTool --skill wfa-avalonia-ui -a codex`. Or copy the skill folder (.codex/skills/wfa-avalonia-ui in tautcony/ChapterTool) into .agents/skills/wfa-avalonia-ui in your project. Codex loads it when a task matches its description.
Can I use Wfa Avalonia UI in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add tautcony/ChapterTool --skill wfa-avalonia-ui -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/wfa-avalonia-ui, .gemini/skills/wfa-avalonia-ui, .github/skills/wfa-avalonia-ui and .opencode/skills/wfa-avalonia-ui in your project.
What does Wfa Avalonia UI need to run?
SKILL.md names no scripts, command-line tools or credentials: Wfa Avalonia UI is instructions for the agent only.
Does Wfa Avalonia UI access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Wfa Avalonia UI safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Wfa Avalonia UI use?
Wfa Avalonia UI is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Wfa Avalonia UI use?
About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 942 tokens, read only when the agent opens those files.
What are the alternatives to Wfa Avalonia UI?
Skills that share tags, products or a category with Wfa Avalonia UI: Locale UI Patterns (openchamber/openchamber, 11k stars), Instui Docs (instructure/instructure-ui, 482 stars), Accessibility I18n (devcodex-labs/devcodex, 439 stars) and Dotnet UI (novotnyllc/dotnet-artisan, 232 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Wfa Avalonia UI?
tautcony (a GitHub user) maintains it in tautcony/ChapterTool, which has 113 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 10, 2026.
Source: tautcony/ChapterTool on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.