desktopmanager-build

Category: Docs & Knowledge | Uploader: EvotecIT | Downloads: 0 | Version: v1.0（Latest）

Build, package, and verify DesktopManager NuGet, PowerShell module, and CLI/MCP artefacts through the repo-standard PowerForge entrypoints. Use when changing Build/Build-Project.ps1, Build/Build-Module.ps1, Build/project.build.json, powerforge.dotnetpublish.json, module packaging, CLI publish outputs, release assets, or build/operator documentation.

Changelog: Source: GitHub https://github.com/EvotecIT/DesktopManager

Directory Structure

Current level: tree/v2-speedygonzales/.agents/skills/desktopmanager-build/

📁 agents/
- 📄 openai.yaml 537 B
📄 SKILL.md 1.9 KB

SKILL.md

---
name: desktopmanager-build
description: Build, package, and verify DesktopManager NuGet, PowerShell module, and CLI/MCP artefacts through the repo-standard PowerForge entrypoints. Use when changing Build/Build-Project.ps1, Build/Build-Module.ps1, Build/project.build.json, powerforge.dotnetpublish.json, module packaging, CLI publish outputs, release assets, or build/operator documentation.
---

# DesktopManager Build

Use this skill when the task touches how DesktopManager is built, packaged, or published.

## Golden Path

1. Use the repo entrypoint first:
   `.\Build\Build-Project.ps1`
2. Prefer plan mode before changing packaging behavior:
   `.\Build\Build-Project.ps1 -Plan`
3. For PowerShell module-only work, use:
   `.\Build\Build-Module.ps1 -SkipInstall`
4. For CLI-only publish verification, use:
   `.\Build\Build-Project.ps1 -Build:$false -BuildModule:$false`
5. When checking a specific runtime publish, pass:
   `-Runtimes win-x64`

## Decision Rules

- Treat `Build/Build-Project.ps1` as the primary repo build and release entrypoint.
- Prefer changing `Build/project.build.json` and `powerforge.dotnetpublish.json` over hardcoding publish behavior in ad-hoc scripts.
- Prefer `Build/Build-Module.ps1` for PowerShell packaging behavior instead of editing checked-in artefacts by hand.
- Verify the resulting behaviour from the real surfaces:
  NuGet/library, PowerShell import, CLI help, and `desktopmanager mcp serve`.
- Keep docs aligned with the actual build flow:
  `Docs/Build.Runbook.md`, `README.MD`, and repo-local skills.
- When packaging or publish output changes, check the expected output locations before concluding:
  `Artefacts/ProjectBuild`, `Artefacts/Unpacked`, `Artefacts/Packed`, and `Artefacts/PowerForge/DesktopManager`.

## Reference Files

- `Build/Build-Project.ps1`
- `Build/Build-Module.ps1`
- `Build/project.build.json`
- `powerforge.dotnetpublish.json`
- `Docs/Build.Runbook.md`
- `README.MD`

Comments 0

Latest | Hot

Please login before commenting.

Loading comments...

desktopmanager-build

Directory Structure

SKILL.md

Report

Notice