build-install
Skill1 starsChanged 11 days agoAGPL-3.0View on GitHub
Build and install Agentmaster ON THIS MACHINE — every build flavor (lib-only compile check, ClCompile-only for locked binaries, full Debug package, full Release package, the engine test harness) and both local installs: the DEV instance (AgentmasterDev, Debug loose layout, close → build → relaunch) and the PRODUCTION instance (Agentmaster, Release loose layout: build -ReleaseIdentity → stamp version → register → launch → profile picker), including the HOT deploy of either instance — build into the layout slot it is NOT registered from (Build-Agentmaster.ps1 -LayoutDir; production slots Q:\agentmaster-layouts\Release / Release-B, dev slots Q:\agentmaster-layouts\Debug / Debug-B — EVERY build writes to Q:, never K:, the build trees are junctions to Q:) while it keeps running, then a few-second swap (tools\Swap-AgentmasterLayout.ps1 [-PackageName AgentmasterDev]: GUI-only stop, drain, re-register, launch, rollback). Encodes the machine map (two registered identities side by side, one repo tree, the Store WT to never touch) and the battle-tested troubleshooting: the self-kill check (is MY shell hosted in the instance I'm about to close?), PRI210 mapped resources.pri, 0x80070020 same-full-name re-register collisions (orphaned claudes pin a removed package — bump the layout version, never kill them), stale build-mutex reclaim, Git-Bash msbuild invocation quirks, the ~156s `.appxsym` symbol-package skip (the wrapper's default `/p:AppxSymbolPackageEnabled=false`, a measured 4–10x speedup), the transient `D8040` / `C1083 Permission denied` obj-lock build failure (clear leftover MSBuild/mspdbsrv nodes, retry), and the STALE-INCREMENTAL-BUILD class after a `SessionModels.h`/ `SessionRegistry.*`/other widely-included header or a `.idl` changes struct layout or WinRT properties — a plain `LNK2019` on a symbol that IS defined in source, an `/RTC1` stack-corruption fail-fast, or a genuine `STATUS_HEAP_CORRUPTION` (`0xC0000374`) crash on launch, all fixed the SAME way (purge `Generated Files` + both engine projects' `obj`, full rebuild with `-ClMpCount 6` to dodge a PCH virtual-memory-exhaustion failure of its own under unbounded `/m`), confirmed 3x in one session. Use when asked to build, rebuild, compile-check, deploy/reinstall/relaunch the dev or production instance, make the build faster, register the loose layout, or diagnose a build/registration/crash-on-launch failure.
- Deletes or force-pushes
In this repository5 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- claude-wrap-ConPTYSkill
- debug-dumpsSkill
- release-notesSkill
- release-versionSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.