frankhaugen

Reviews root AGENTS.md for agents.md style plus ACS discoverability. Use when editing AGENTS.md or when user asks if the entry contract is complete. Triggers on AGENTS.md, entry contract, or agents.md alignment.

Audits this repository for ACS v0.1 self-consistency—AGENTS.md discovery, .ai/index completeness, skill packages, and verify script. Use before releases or when user asks if the repo is compliant. Triggers on audit, compliance, self-check, or verify repo.

Edits normative Sections 1–10 of spec/ACS-v0.1.md. Use for BCP 14 keyword fixes, compliance wording, Section 10 reference table updates, or new MUST/SHOULD rules. Triggers on normative spec, BCP14, compliance, Section 10, or RFC 2119.

Creates or edits Agent Skills packages under .ai/skills/, templates/.ai/skills/, or examples. Validates directory name, SKILL.md front matter, and index links. Use for skill structure or YAML fixes. Triggers on SKILL.md, skill package, agentskills, or new skill directory.

Aligns templates/ and examples/ with spec ACS-v0.1 after layout or taxonomy changes. Use when publisher docs or Sections 5–8 paths change. Triggers on templates, examples, parity, or publisher-layout.

Adds or updates automated tests when code behavior changes. Use after implementing features, fixing bugs, refactoring public APIs, or when the user asks for test coverage. Triggers on keywords such as tests, coverage, unit test, and regression.

Template Agent Skill for ACS. Replace with a real skill name (must match this directory) and a description that states what the skill does and when to use it, including trigger keywords.

Pack shipping NuGet libraries from Frank.GameEngine.slnx and locate output artifacts.

Run or explain Frank.GameEngine samples—loops, NullInputSource, audio, and optional Aspire AppHost.

Restore, build, and test Frank.GameEngine.slnx in Release using TUnit and Microsoft.Testing.Platform.

Checklist-driven review of a game codebase against the HexGame architecture specification (dependency direction, commands, snapshots, effects, testing). Use when the user asks whether a project is HexGame-compliant, compatible, or strict per Section 27 of the spec.

Workflow for proposing and landing a change to the HexGame normative or informative specifications, including changelog and TOC hygiene. Use when the user asks to update the architecture spec, add sections, or reconcile overview text with hexgame-architecture.md.

Acts as the Galactic Confederation Review's in-universe editor: mines reference material or archive gaps for an angle, writes a republished selection, registers it in the mesh archive, generates audio, commits, and pushes. Use when the user asks to publish a new essay, create a selection, run the Review editor, draft from reference material, or ship one complete republication release.