skills.rest
ShareX
ShareXOFFICIAL
Explore all skills by this author →
Website𝕏@ShareXGitHub

ShareX Core Standards

Enforce license headers, Windows build rules, and SkiaSharp version constraints across C# projects.

309|15|Updated Dec 29, 2025
Search Tags:#csharp#standards#coding#avalonia#build-config#license-headers#skia
One-click install
npx skills add https://github.com/ShareX/XerahS --skill sharex-core-standards
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ShareX Core Standards
Source: https://github.com/ShareX/XerahS/tree/main/.ai/skills/xerahs-core
Command: npx skills add https://github.com/ShareX/XerahS --skill sharex-core-standards

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

License headers, build configuration rules, SkiaSharp version constraints, and general coding standards for XerahS are defined and enforced to maintain consistency, licensing compliance, and reliable builds across the project.

Core Features & Use Cases

  • License header enforcement across all C# files (.cs) to ensure GPL v3 compliance for the Avalonia-based implementation.
  • Build rule enforcement, including Windows Target Framework Moniker formatting (net10.0-windows10.0.19041.0) and SkiaSharp version constraints (2.88.9) to prevent incompatible configurations.
  • Guidelines for consistent documentation, testing, and security practices to streamline code reviews and releases.

Quick Start

Apply these standards to all new and existing C# projects in XerahS to ensure license compliance, build reliability, and consistent coding practices.

Frequently Asked Questions about ShareX Core Standards

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce license headers and coding standards for C# projects in CI pipelines?▼

You enforce license headers and coding standards for C# projects by applying automated validation rules during development, code reviews, and CI pipelines, ensuring GPL v3 compliance and build reliability across the repository.

What is the correct Windows target framework moniker for Avalonia C# builds?▼

The correct Windows target framework moniker for Avalonia C# builds is net10.0-windows10.0.19041.0. Validating this specific string prevents incompatible build configurations and ensures reliable execution.

Do I need to pin SkiaSharp to a specific version for Avalonia development?▼

Yes, you must pin SkiaSharp to version 2.88.9 for Avalonia development. Enforcing this version constraint across the codebase prevents incompatible configurations and maintains reliable rendering.

How do I validate frontmatter presence in SKILL.md files?▼

To validate frontmatter presence in SKILL.md files, enforce a rule requiring both a name and description in the frontmatter. This ensures consistent documentation standards across the repository.

What's the best way to ensure GPL v3 compliance across C# files?▼

The best way to ensure GPL v3 compliance across C# files is through license header enforcement applied to all .cs files. This maintains licensing compliance consistently during code reviews and CI pipelines.

When do I need to validate build configuration rules for SkiaSharp and Windows?▼

You need to validate build configuration rules for SkiaSharp and Windows during development, code reviews, and CI pipelines. This prevents incompatible configurations and ensures consistent build reliability across C# projects.

Related Skills

Explore More Software Engineering Skills→
sunyonghuansunyonghuan
46

dotnet-advisor

Route .NET and C# requests to the correct specialist skill.

Community
Intermediate
matteocervellimatteocervelli
25

typescript-quality-checker

Validate TypeScript/JavaScript code quality with Prettier, ESLint, tsc, and npm audit.

Community
Advanced
asynkronasynkron
32

roslynator

Analyze, fix, and format C# code in .NET solutions with Roslynator CLI.

Official
Advanced
AGIBuildAGIBuild
10

dotnet-version-detection

Detect .NET TFMs and SDK versions from project files.

Community
Intermediate