How do I install the Build And Test skill?

Run npx skillmds@latest add huynhsontung/build-and-test in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Build And Test safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Build And Test?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Build And Test free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Build And Test?

huynhsontung (@huynhsontung) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Build And Test by huynhsontung — Agent Skill

Name: Build And Test
Author: huynhsontung

File contents

Build and Test Runbook

Follow these structured procedures when restoring, compiling, testing, or validating formatting in the Screenbox solution.

1. Prerequisites & Package Restore

Ensure local dotnet tools and NuGet packages are restored before building.

[!IMPORTANT] Always use MSBuild from Visual Studio 2026 (version 18) for compiling and restoring projects in this repository. NEVER use dotnet build, as UWP and CsWinRT tooling require Visual Studio 2026 MSBuild.

Locate Visual Studio 2026 MSBuild

You can locate MSBuild using vswhere or standard installation path:

$msbuild = & "${env:ProgramFiles(x86)}\Microsoft Visual Studio\Installer\vswhere.exe" -version "[18.0,19.0)" -latest -requires Microsoft.Component.MSBuild -find MSBuild\**\Bin\MSBuild.exe
if (-not $msbuild) { $msbuild = "C:\Program Files\Microsoft Visual Studio\18\Community\MSBuild\Current\Bin\MSBuild.exe" }

Restore Dotnet Tools (XAML Styler & LottieGen)

dotnet tool restore

Restore NuGet Packages

For the full solution:

& $msbuild Screenbox.slnx -t:restore -p:Platform=x64 -p:Configuration=Debug

Or restore the main UWP app project individually:

& $msbuild Screenbox/Screenbox.csproj /p:Configuration=Debug /p:Platform=x64 /t:Restore /m

2. Compilation / Build

Target the system platform for local development. For example, to build the main UWP app in Debug mode on the x64 platform:

& $msbuild Screenbox/Screenbox.csproj /p:Configuration=Debug /p:Platform=x64 /t:Build /m

Or build Screenbox.Core:

& $msbuild Screenbox.Core/Screenbox.Core.csproj /p:Configuration=Debug /p:Platform=x64 /t:Build /m

3. Running Automated Tests

Run Full Test Suite

dotnet run --project Screenbox.Core.Tests/Screenbox.Core.Tests.csproj

Testing Rules & Constraints

Pure Logic Tests: Use [TestMethod] in Screenbox.Core.Tests.
XAML-Dependent Tests: NEVER use plain test runners for tests that instantiate XAML types. Use the UWP Unit Test App runner with [UITestMethod].
No Boilerplate Comments: Do not emit // Arrange, // Act, // Assert comments.
Naming Style: Mirror existing test method naming in nearby test classes.

4. XAML Formatting & Lint Verification

Verify all XAML files adhere to XAML Styler rules:

pwsh ./scripts/lint-xaml.ps1

To format specific modified XAML files manually:

dotnet tool run xstyler -f Screenbox/Pages/PlayerPage.xaml

---name: build-and-testdescription: Procedures for restoring packages, compiling Screenbox and Screenbox.Core, running automated unit tests, and verifying XAML formatting. Use when the user asks to build projects, run tests, or verify code changes.---# Build and Test RunbookFollow these structured procedures when restoring, compiling, testing, or validating formatting in the Screenbox solution.---## 1. Prerequisites & Package RestoreEnsure local dotnet tools and NuGet packages are restored before building.> [!IMPORTANT]> **Always use MSBuild from Visual Studio 2026 (version 18)** for compiling and restoring projects in this repository. **NEVER use `dotnet build`**, as UWP and CsWinRT tooling require Visual Studio 2026 MSBuild.### Locate Visual Studio 2026 MSBuildYou can locate MSBuild using `vswhere` or standard installation path:```pwsh$msbuild = & "${env:ProgramFiles(x86)}\Microsoft Visual Studio\Installer\vswhere.exe" -version "[18.0,19.0)" -latest -requires Microsoft.Component.MSBuild -find MSBuild\**\Bin\MSBuild.exeif (-not $msbuild) { $msbuild = "C:\Program Files\Microsoft Visual Studio\18\Community\MSBuild\Current\Bin\MSBuild.exe" }```### Restore Dotnet Tools (XAML Styler & LottieGen)```pwshdotnet tool restore```### Restore NuGet PackagesFor the full solution:```pwsh& $msbuild Screenbox.slnx -t:restore -p:Platform=x64 -p:Configuration=Debug```Or restore the main UWP app project individually:```pwsh& $msbuild Screenbox/Screenbox.csproj /p:Configuration=Debug /p:Platform=x64 /t:Restore /m```---## 2. Compilation / BuildTarget the system platform for local development. For example, to build the main UWP app in Debug mode on the `x64` platform:```pwsh& $msbuild Screenbox/Screenbox.csproj /p:Configuration=Debug /p:Platform=x64 /t:Build /m```Or build `Screenbox.Core`:```pwsh& $msbuild Screenbox.Core/Screenbox.Core.csproj /p:Configuration=Debug /p:Platform=x64 /t:Build /m```---## 3. Running Automated Tests### Run Full Test Suite```pwshdotnet run --project Screenbox.Core.Tests/Screenbox.Core.Tests.csproj```### Testing Rules & Constraints- **Pure Logic Tests**: Use `[TestMethod]` in `Screenbox.Core.Tests`.- **XAML-Dependent Tests**: **NEVER** use plain test runners for tests that instantiate XAML types. Use the `UWP Unit Test App` runner with `[UITestMethod]`.- **No Boilerplate Comments**: Do not emit `// Arrange`, `// Act`, `// Assert` comments.- **Naming Style**: Mirror existing test method naming in nearby test classes.---## 4. XAML Formatting & Lint VerificationVerify all XAML files adhere to XAML Styler rules:```pwshpwsh ./scripts/lint-xaml.ps1```To format specific modified XAML files manually:```pwshdotnet tool run xstyler -f Screenbox/Pages/PlayerPage.xaml```

Frequently asked questions

Build And Test