菜单
Maintain the external GF reference project boundary and examples smoke workflow. Use when working with gf-reference-project, examples suite, sync_reference_project.py, smoke scenes, reference project feedback, or avoiding project-business leakage into addons/gf.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Maintain GF Framework source, docs, tests, API surface, generated references, and maintenance tooling. Use when Codex modifies addons/gf, tests/gf_core, docs/zh, API docs, tools, AI maintenance policy, or needs to choose GF-specific validation commands.
Build, refactor, debug, and review Godot projects that use GF Framework. Use for project architecture, GF API selection, lifecycle and ownership decisions, package or extension selection, project-owned platform adapters, validation, and evidence-based feedback to the GF repository.
Prepare and verify GF Framework version releases, Asset Store packages, commits, and SemVer tags. Use when the user asks to determine a version, enter release flow, update release metadata, build release packages, commit, tag, push, or check a GF release.
Split large GF Framework changes into focused review tracks before commit, release, or risky integration. Use after broad refactors, API changes, layer moves, extension restructuring, reference-project migration work, or when the user asks for multi-agent audit.
| name | gf-reference-boundary |
| description | Maintain the external GF reference project boundary and examples smoke workflow. Use when working with gf-reference-project, examples suite, sync_reference_project.py, smoke scenes, reference project feedback, or avoiding project-business leakage into addons/gf. |
Use this skill whenever GF maintenance touches the external reference project or examples suite. The reference project is a validation surface and feedback source, not part of the GF framework repository.
../gf-reference-projectGF_REFERENCE_PROJECT_PATHGF_REFERENCE_BOOT_SCENE or .gf_reference_project.json boot_sceneGF_REFERENCE_SMOKE_SCENE or .gf_reference_project.json smoke_sceneAlways confirm the target contains project.godot before writing.
tools/gf_maintenance.py check --suite examples is read-only by default and checks that external addons/gf is current.python tools\sync_reference_project.py --project-root ..\gf-reference-projectpython tools\gf_maintenance.py check --suite examples --sync-examplesaddons/gf/ is generated/synced content. Do not treat it as reference project source.Run these when examples are in scope:
python tools\sync_reference_project.py --project-root ..\gf-reference-project --check
python tools\gf_maintenance.py check --suite examples --json
Use explicit write sync only when the user asked to sync, or when validation requires syncing after GF source changed.
If the reference project reveals repeated friction, classify it before changing framework code:
Record framework feedback on the GF side, especially in ai_analysis/framework_feedback.md when useful. Do not write reference-project gameplay rules into addons/gf.