avalonia-extensions: Skill for Claude Code

.github/skills/winui-control-theming/SKILL.md

winui-control-theming is a skill for Claude Code, Codex from Devolutions/avalonia-extensions. It costs 71 tokens per session (3,698 once invoked), scanned A, original, MIT.

A set of guidelines for creating or refining WinUI-styled control templates and theme resources in an Avalonia application. Avalonia is a cross-platform framework for building .NET user interfaces, while WinUI is Microsoft's Windows interface design system.

In plain words
What is it for?
Use it when adding a WinUI-like control, moving Fluent styling from another app, choosing brush names, or deciding whether a resource belongs in shared theme resources or a control file.
Why use it?
It keeps controls visually and structurally consistent by reusing recognized WinUI resource names and separating shared colors from control-specific settings.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

This is Devolutions/avalonia-extensions's own configuration. It tells Claude Code and Codex how to work on avalonia-extensions itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything avalonia-extensions configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Devolutions/avalonia-extensions. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Devolutions/avalonia-extensions/master/.github/skills/winui-control-theming/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/Devolutions/avalonia-extensions

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for winui-control-theming

README.md
[![agentmods](https://agentmods.dev/badge/skills/devolutions/avalonia-extensions/winui-control-theming/github.svg)](https://agentmods.dev/skills/devolutions/avalonia-extensions/winui-control-theming)
Your own site
<a href="https://agentmods.dev/skills/devolutions/avalonia-extensions/winui-control-theming"><img src="https://agentmods.dev/badge/skills/devolutions/avalonia-extensions/winui-control-theming/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for winui-control-theming

Your own site · 80×15
<a href="https://agentmods.dev/skills/devolutions/avalonia-extensions/winui-control-theming"><img src="https://agentmods.dev/badge/skills/devolutions/avalonia-extensions/winui-control-theming.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 71 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,698 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00071 $0.03698
Opus 5.5 $0.00028 $0.01479
Sonnet 5.5 $0.00014 $0.00740
Haiku 4.5 $0.00007 $0.00370

Measured 28d ago against content hash 8c22f0b2d469, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

winui-control-theming scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 28d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.github/skills/winui-control-theming/SKILL.md · 291 lines

How it starts

The opening of the file, as written. The whole thing — 291 lines — stays where its author put it; the contents beside it link to each section on GitHub.

WinUI Control Theming

Use this skill when working on src/Devolutions.AvaloniaTheme.WinUI/ and the goal is to add or refine WinUI-styled control themes while staying consistent with the resource strategy already used for this theme.

Core Principle

Prefer official WinUI resource names over made-up local names whenever they can be identified from WinUI source or docs.

This theme should follow the WinUI model as closely as practical:

  • Shared WinUI semantic tokens go in Accents/ThemeResources.axaml
  • Control-specific WinUI resources go in the relevant file under Controls/
  • New local resource names should be introduced only when no real WinUI equivalent exists

Why

Avalonia's Fluent theme is a Fluent-looking base theme, but its resource surface does not always match the newer WinUI token vocabulary. For this theme, the goal is not just to make controls "look good"; it is to make them look WinUI-like using WinUI concepts and names where possible.

That keeps future control work consistent:

  • later controls can reuse the same token set
  • resource names stay recognizable to people familiar with WinUI
  • ad-hoc local naming does not spread across the theme

Required Workflow

When adding or updating a WinUI control theme:

  1. Start from the WinUI control

    • Find the WinUI default template and the theme resources it uses.
    • Extract the actual resource names referenced by the template.
  2. Separate shared tokens from control-specific resources

    • Examples of shared tokens: TextFillColorPrimaryBrush, AccentFillColorDefaultBrush, ControlFillColorDefaultBrush
    • Examples of control resources: ButtonBackground, ButtonForegroundPointerOver, ButtonBorderBrushPressed
  3. Compare against Avalonia Fluent

    • Check the existing Avalonia Fluent control template and resource model.
    • Decide whether the control can be adapted with targeted overrides or needs a fuller template port.
  4. Port only what is needed

    • Do not dump the full WinUI token set into ThemeResources.axaml.
    • Add only the resources that are actually referenced by the new or updated control theme, unless there is a clear near-term reason to add a small shared set together.

Read the full file on GitHub · 291 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 28d ago Changed · +54 lines 8c22f0b2d469
  2. 1mo ago Changed · +24 lines 5a458bcdd7cf
  3. 1mo ago Changed · +42 lines db8708ff7f07
  4. 2mo ago First seen · 171 lines · 71 tokens per session scan A 5840daa3a161

Subscribe to this mod's changes

winui-control-theming is a skill published in the GitHub repository Devolutions/avalonia-extensions (84 stars, last pushed 15d ago), licensed MIT. It adds 71 tokens to every session and 3,698 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

anti-slop-design

Autonomous Principal Design Technologist. Cures vibe-coded software from AI frontend slop using curated token archetypes and 7-axis quality gating.

sickn33/agentic-awesome-skills · 34 tokens

chakra-ui-builder

Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…

chakra-ui/chakra-ui · 214 tokens

visual-ralph

Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ultragoal with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.

Yeachan-Heo/oh-my-codex · 52 tokens

frontend-ui-dark-ts

Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations. Use when creating dashboards, admin panels, or data-rich interfaces with a refined dark aesthetic.

microsoft/skills · 48 tokens

open-design-setup

Prepare or repair a project's prototyping environment so open-design can build prototypes with the project's own component library and render them through the project's toolchain. Use when the library target is needed and docs/design/prototyping.md is missing, stale, or failing; excludes HTML-only design work and…

compozy/compozy · 67 tokens

frontend-visual-qa

Audits rendered UI and specific task/object-link handoffs; excludes ordinary source citations alone. Audits already-rendered UI and Markdown/Obsidian image layout — web app, deck/slide, dashboard, design-system, or Electron/native app — via real-browser/native-app journeys and a Playwright sweep. Use after UI…

daymade/claude-code-skills · 125 tokens