Agent skill

avalonia-controls-and-windowing

Build or troubleshoot Avalonia controls, control themes, windows, popups, menus, tray integration, native menus, top-level services, and notification surfaces. Use for templated control authoring, popup behavior, custom chrome, dialog flows, menu systems, or per-control API guidance.

Stars 57
Forks 6

Install this agent skill to your Project

npx add-skill https://github.com/wieslawsoltes/development-plugin-for-avalonia/tree/main/skills/avalonia-controls-and-windowing

SKILL.md

Avalonia Controls and Windowing

Start with:

  • ../../references/10-templated-controls-and-control-themes.md
  • ../../references/13-windowing-and-custom-decorations.md
  • ../../references/48-toplevel-window-and-runtime-services.md

Load these based on the requested surface:

  • ../../references/25-popups-flyouts-tooltips-and-overlays.md
  • ../../references/52-controls-reference-catalog.md
  • ../../references/53-menu-controls-contextmenu-and-menuflyout-patterns.md
  • ../../references/54-native-menu-and-native-menubar-integration.md
  • ../../references/55-tray-icons-and-system-tray-integration.md
  • ../../references/56-managed-notifications-and-window-notification-manager.md

Workflow

  1. Separate control contract, template, and host surface concerns.
  2. Pick the right top-level surface: window, popup, flyout, native menu, tray, or in-app notification.
  3. Use the controls catalog only as a quick lookup after the workflow docs have narrowed the direction.
  4. Validate platform-specific window or popup behavior explicitly.

Rules

  • Keep template parts and visual states documented in the implementation.
  • Avoid mixing shell, popup, and notification logic into one control when host services are a better fit.
  • Treat per-platform chrome and tray behavior as opt-in integration work.

Expand your agent's capabilities with these related and highly-rated skills.

wieslawsoltes/development-plugin-for-avalonia

development-plugin-for-avalonia

Repo-local umbrella skill for building, reviewing, designing, porting, and migrating Avalonia applications with modern XAML/C# patterns on Avalonia 11.3.12. Use when working inside this repository and the request is broad Avalonia work; route quickly to the focused plugin skills for startup, bindings, styling, controls, layout, rendering, testing, design systems, or HTML/WinForms/WPF/WinUI/Avalonia 12 migration work.

57 6
Explore
wieslawsoltes/development-plugin-for-avalonia

avalonia-styling-and-resources

Build or troubleshoot Avalonia styles, themes, resources, property-system usage, theme variants, resource packaging, and custom theme architecture. Use for selector fixes, attached properties, resource lookup problems, theme switching, library resource packaging, or code-only theme work.

57 6
Explore
wieslawsoltes/development-plugin-for-avalonia

avalonia-design-systems

Design polished Avalonia design systems with reusable tokens, typography, spacing, shell composition, dense workflow UX, motion, and governance rules. Use for professional UI direction, design-token architecture, responsive layout systems, information architecture, or high-quality desktop workflow design.

57 6
Explore
wieslawsoltes/development-plugin-for-avalonia

avalonia-testing-diagnostics-and-performance

Validate Avalonia applications with headless tests, render or UI tests, diagnostics tooling, troubleshooting workflows, and performance reviews. Use for test strategy, DevTools or profiler usage, performance regressions, rendering investigations, or production hardening passes.

57 6
Explore
wieslawsoltes/development-plugin-for-avalonia

avalonia-accessibility-and-validation

Design or review Avalonia validation, data-error presentation, accessibility semantics, automation properties, focus order, and testable UI metadata. Use for validation pipelines, screen-reader support, keyboard-only UX, automation-tree issues, or accessibility hardening.

57 6
Explore
wieslawsoltes/development-plugin-for-avalonia

winui-to-avalonia

Port WinUI or Windows App SDK applications to Avalonia, including shell design, dependency-property patterns, theme resources, composition, commands, dialogs, and platform integration. Use for `NavigationView`, `ContentDialog`, `ThemeResource`, `VisualStateManager`, `ItemsRepeater`, `AppWindow`, or broader WinUI-to-Avalonia migration work.

57 6
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results