메뉴
Gum release/build orchestration — drives the in-repo release checklist and hands off the notes draft. Triggers: cutting a release, publishing the Gum NuGet packages, releasing the tool, /gum-release.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Gum tool C# code generation. Triggers: CodeGenerator, CodeOutputPlugin, generated code structure, .codsj settings, OutputLibrary selection, Forms codegen, state generation. For CLI/headless codegen see gum-cli.
Where runtime-feature demo screens go. Triggers: adding a sample/demo page for a new runtime feature, NineSliceScreen/SpriteScreen, shape demos, MonoGameGumInCode, Samples/raylib, SilkNetGum.
Forms DefaultVisuals — code-only visual classes backing Forms controls. Triggers: ButtonVisual, any *Visual class in DefaultVisuals/, Styling, DefaultFormsTemplates registration, custom code-only Forms visuals.
Building or modifying a Gum theme package (Themes/Gum.Themes.*) — restyling Forms controls by subclassing their V3 default visuals. Triggers: any file under Themes/, custom *Visual subclassing Gum.Forms.DefaultVisuals.V3.*, theme entry-point methods like EditorTheme.Apply / DarkProTheme.Apply.
Test-first discipline for Gum. Triggers: behavior changes (bug fix or feature) under GumCommon/, Gum/, MonoGameGum/, RenderingLibrary/, KniGum/, FnaGum/, SkiaGum/, RaylibGum/, Tools/Gum.ProjectServices/. Skip for docs, renames, csproj/projitems plumbing, style-only edits.
Unifying per-platform runtime files (MonoGame/Raylib/Skia/KNI/FNA, plus the Apos.Shapes ↔ SkiaGum shape-runtime pair) into one source with
Invoking product-manager agent to drive the Gum release checklist.
This skill is a guided checklist driver, not full automation. Most release steps are inherently human — taking screenshots, clicking GitHub Actions, uploading to FTP, announcing on Discord/Twitter/Bluesky. The skill's job is to walk the maintainer through the steps in order, track what's done, and invoke the one step a skill can actually do (the notes draft).
The release process lives in docs/contributing/building-and-releasing-gum.md (published to the Gum GitBook space). That doc is canonical and maintainer-edited. Read it at the start of every run and follow whatever it says today — do not hardcode or paraphrase its steps into this skill, or the two will drift.
TaskCreate) so nothing is dropped across the long-running release, and mark each completed as the user confirms it.gum-monthly-release skill — it drafts the notes and is the only step with real automation. Everything else (NuGet workflow trigger, Build-and-Release workflow, screenshots, migration doc, announcements, FRB FTP upload) is the user's manual action; you confirm and check it off.gum-monthly-release only writes the notes markdown. It does not bump versions, cut the tag, or trigger workflows — those are separate manual steps in the doc.