Semiteq

Use when building or reviewing Avalonia settings, preferences, options, or editor windows, forms, dialogs, property panes, or any AXAML where labels and controls must align across groups. Triggers on control alignment, ragged card widths, shared label/control columns, right-alignment consistency, numeric-input alignment, and dialog sizing/clipping. Avalonia 12+ (uses Grid shared-size scope + ColumnSpacing/RowSpacing).

Use when theming or restyling an Avalonia desktop app toward a JetBrains/IntelliJ "New UI" look (flat, dense, neutral grays, one restrained blue accent, light+dark). Covers the JetBrains Int UI design tokens (color ramps, typography, dimensions, radii), and how to realize them in Avalonia 12 via Semi.Avalonia + token overrides + Inter/JetBrains Mono + theme variants. Triggers on theme/palette/dark-mode/accent/font/corner-radius/design-token work. Distinct from avalonia-form-layout (which is about alignment/spacing inside a single form).

Use this skill when the user wants to create a release. Checks working tree, proposes a tag message based on recent commits, gets user approval, then commits, tags, pushes, and monitors CI. Never releases without explicit user approval.

Load this skill whenever you need information about Avalonia UI components, controls, layouts, styles, animations, bindings, or any other Avalonia API. Use the GitHub MCP tools to read docs from the AvaloniaUI/avalonia-docs repository. Fall back to WebFetch only if the topic is not covered there.

Step-by-step workflow for writing documentation for a Function Block in NtoLib. Covers both headless and visual FBs. Produces a Russian-language markdown doc following the established pattern in Docs/.

Use this skill when the user asks to release a new NtoLib version — "let's release v1.12.0", "cut a release", "выпустить новую версию", "пуш тега", "сделать beta1". Walks through gathering changes since the last release, drafting release notes in the project's established Russian style, creating an annotated tag with the right cleanup flag, pushing it to trigger the GitHub Actions release workflow, and verifying the published GitHub Release. NOT for generic release tooling on other repos (use release-tools:new) or for listing unreleased commits (use release-tools:last-tag).

Use when creating a brand-new headless (non-visual) Function Block in NtoLib — "add a new headless FB", "create a StaticFBBase block", "new non-visual function block", "add an FB with no UI". Covers XML pin config, service facade, FB orchestrator class, csproj registration, build, and elevated COM registration. NOT for visual FBs that have a control (use new-visual-fb), nor for editing an existing FB.

Use when creating a brand-new visual Function Block in NtoLib — "add a new visual FB", "create a VisualFBBase block with a control", "new FB with a mnemoscheme control", "make an editor-style copy of an FB". Covers the XML Map/VisualMap, FB + VisualControlBase control with distinct GUIDs, palette bmp, DI composition, csproj registration, build, elevated COM registration, and the shared-core / thin-shell copy pattern. NOT for headless FBs with no control (use new-nonvisual-fb), nor for editing an existing FB in place.