Agent skills
Skills you can use with AI coding agents, indexed from public GitHub repositories.
-
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.
wieslawsoltes/development-plugin-for-avalonia 57
-
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.
wieslawsoltes/development-plugin-for-avalonia 57
-
avalonia-platform-services
Integrate or troubleshoot Avalonia platform services such as storage provider, clipboard, launcher, drag/drop, screens, and top-level runtime helpers. Use for file pickers, external-open flows, clipboard or data-transfer bugs, multi-screen behavior, or platform service abstractions.
wieslawsoltes/development-plugin-for-avalonia 57
-
avalonia-12-migration
Plan and execute migration from Avalonia 11.3.12 to Avalonia 12 using the repository's dedicated migration lane. Use for breaking-change review, source-backed API delta lookup, migration sequencing, and upgrades that should stay grounded in the current published Avalonia 12 documentation and generated artifacts.
wieslawsoltes/development-plugin-for-avalonia 57
-
avalonia-layout-and-virtualization
Design or optimize Avalonia panels, measure and arrange behavior, custom layout controls, item virtualization, recycling, and large-data presentation. Use for `MeasureOverride` or `ArrangeOverride` work, invalidation bugs, virtualized item surfaces, or custom panel authoring.
wieslawsoltes/development-plugin-for-avalonia 57
-
avalonia-threading-and-dispatcher
Design or review Avalonia reactive flows, dispatcher usage, timers, async UI coordination, and thread-affinity boundaries. Use for `Dispatcher.UIThread`, background work handoff, timer selection, reactive pipeline fixes, or UI-thread correctness bugs.
wieslawsoltes/development-plugin-for-avalonia 57
-
avalonia-bindings-and-xaml
Implement or troubleshoot Avalonia compiled bindings, runtime XAML loading, converters, markup extensions, binding notifications, dynamic resources, and AOT-safe XAML patterns. Use for `x:DataType`, `CompiledBinding`, converter wiring, `AvaloniaRuntimeXamlLoader`, resource lookup issues, or runtime markup refactors.
wieslawsoltes/development-plugin-for-avalonia 57
-
winforms-to-avalonia
Port WinForms applications and patterns to Avalonia, including layout, control migration, owner-draw replacement, application lifetime, resources, and workflow shells. Use for `Control` or `Form` migration, `DataGridView` and `ListView` replacement, `OnPaint` ports, dialog or tray flows, or WinForms-to-Avalonia modernization work.
wieslawsoltes/development-plugin-for-avalonia 57
-
avalonia-rendering-and-graphics
Implement or review Avalonia animations, compositor usage, custom drawing, Skia rendering, geometry, hit testing, and advanced rendering interop. Use for transitions, frame-loop work, `Render` overrides, custom visuals, drawing optimizations, or OpenGL or Vulkan hosting boundaries.
wieslawsoltes/development-plugin-for-avalonia 57
-
html-css-to-avalonia
Port HTML or CSS mental models, layouts, controls, theming, and modern web UI patterns to Avalonia. Use for website-to-desktop translation, CSS-to-Avalonia styling work, responsive layout conversion, custom-element or Shadow DOM mapping, or web-style design-system migration into Avalonia.
wieslawsoltes/development-plugin-for-avalonia 57
-
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.
wieslawsoltes/development-plugin-for-avalonia 57
-
avalonia-input-and-commands
Implement or debug Avalonia routed input, focus management, keyboard navigation, commands, gestures, drag/drop workflows, text editing behavior, and interaction routing. Use for `ICommand`, `KeyBinding`, routed events, focus bugs, drag/drop, scroll interaction, or text input edge cases.
wieslawsoltes/development-plugin-for-avalonia 57
-
avalonia-bootstrap-and-lifetime
Design or troubleshoot Avalonia startup wiring, `AppBuilder` configuration, application lifetimes, platform bootstrap, XAML compiler setup, and AOT-friendly build configuration. Use for desktop or single-view startup, `App.axaml` / `App.xaml.cs` composition, platform entrypoints, trimming or NativeAOT readiness, or startup refactors.
wieslawsoltes/development-plugin-for-avalonia 57
-
wpf-to-avalonia
Port WPF applications and patterns to Avalonia, including dependency-property mapping, bindings, resources, templates, layout, rendering, and shell behavior. Use for `DependencyProperty`, routed-command, trigger, `Frame` or `Page`, `OnRender`, `HwndHost`, or other WPF-to-Avalonia migration work.
wieslawsoltes/development-plugin-for-avalonia 57
-
avalonia-views-and-templating
Build or refactor Avalonia view composition, view-location strategies, templates, templated content, and tree-inspection patterns. Use for view locator work, `DataTemplate` or `IDataTemplate` selection, templated parent issues, logical or visual tree traversal, or content-template architecture.
wieslawsoltes/development-plugin-for-avalonia 57
-
avalonia-fluent-design
Build or refine Avalonia UIs that follow Microsoft Fluent guidance with `FluentTheme`, palette customization, density tuning, Fluent shells, iconography, motion, and language-system patterns. Use for FluentTheme adoption, brand mapping onto Fluent tokens, Fluent shell design, or Fluent-specific accessibility and motion work.
wieslawsoltes/development-plugin-for-avalonia 57
-
rtl-document-translation
Translate structured documents (DOCX) to RTL languages (Arabic, Hebrew, Urdu) while preserving exact formatting, table structures, colors, and layouts. Handles quote normalization, multi-pass translation matching, and RTL-specific formatting patterns.
belumume/claude-skills 44
-
document-quality-standards
Use when creating or editing documents (DOCX, PDF, XLSX, PPTX) that need professional output. Adds visual verification, typography hygiene, and formula patterns to the document-skills plugin.
belumume/claude-skills 44
-
ralph-loop
Activate autonomous Ralph Wiggum loop mode for iterative task completion. Use when you have a well-defined task with clear completion criteria that benefits from persistent, autonomous execution.
belumume/claude-skills 44
-
project-retrospective
belumume/claude-skills 44
-
docx-advanced-patterns
Advanced python-docx patterns for handling nested tables, complex cell structures, and content extraction beyond basic .text property. Complements the official docx skill with specialized techniques for forms, checklists, and complex layouts.
belumume/claude-skills 44
-
obsidian-study-vault-builder
Build comprehensive, mobile-compatible Obsidian study vaults from academic course materials with checkpoint-based workflow, error pattern recognition, and quality assurance. Battle-tested patterns from 828KB/37-file projects. Works across all subjects - CS, medicine, business, self-study.
belumume/claude-skills 44
-
rlm-orchestrator
Implement RLM-style (Recursive Language Model) orchestration for complex tasks. This skill should be used when facing large context requirements, multi-part tasks that would benefit from parallel execution, or when context rot is a concern. Automatically decomposes tasks, spawns parallel subagents, aggregates results, and iterates until completion. Inspired by the RLM research paper (arXiv:2512.24601).
belumume/claude-skills 44
-
deep-brainstorming
Use when brainstorming a product or feature where multiple valid technology choices exist and the wrong one is costly, when the user asks for 'objectively best' or 'highest quality', or when the domain has tools/frameworks where marketing or popularity biases could mislead research agents. Also use when starting architecture decisions, evaluating tech stacks, or when the user mentions bias, vendor lock-in, hallucinated benchmarks, or wants research-backed decisions rather than default recommendations.
belumume/claude-skills 44