Maintains the connection between the GF framework and its external reference examples.
Install
mkdir -p .claude/skills/gf-reference-boundary && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12994" && unzip -o skill.zip -d .claude/skills/gf-reference-boundary && rm skill.zipInstalls to .claude/skills/gf-reference-boundary
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
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.Key capabilities
- →Check that external addons/gf is current using a read-only command
- →Perform explicit write sync for the reference project
- →Run checks for examples when they are in scope
- →Classify repeated friction from the reference project into categories
- →Record framework feedback in ai_analysis/framework_feedback.md
How it works
The skill maintains the boundary of the external GF reference project by providing tools to check and sync its content, and to classify feedback without integrating project-specific rules into the framework.
Inputs & outputs
When to use gf-reference-boundary
- →Sync reference project
- →Run smoke tests
- →Check example suite
- →Validate framework integration
About this skill
GF Reference Boundary
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.
Path
- Default project path:
../gf-reference-project - Override:
GF_REFERENCE_PROJECT_PATH - Boot scene override:
GF_REFERENCE_BOOT_SCENEor.gf_reference_project.jsonboot_scene - Smoke scene override:
GF_REFERENCE_SMOKE_SCENEor.gf_reference_project.jsonsmoke_scene
Resolve the project path in this order: explicit --project-root, GF_REFERENCE_PROJECT_PATH, then the default. Always confirm the target contains project.godot before writing. The current file check is necessary but not sufficient proof of ownership; until a managed identity protocol is adopted, do not use sync against an unfamiliar project root.
Sync Rules
tools/gf_maintenance.py check --suite examplesis read-only by default and checks that externaladdons/gfis current.- Write sync is explicit only:
python tools\sync_reference_project.py --apply- or
python tools\gf_maintenance.py check --suite examples --sync-examples
- The external project's
addons/gf/is generated/synced content. Do not treat it as reference project source. - Sync defaults to read-only check;
--planreports planned and applied actions separately without writing. Copy sync captures a bounded binary-exact payload manifest, stages the complete tree, and swaps it with rollback on ordinary failures. Link sync refuses to replace an existing target until a managed ownership protocol is adopted.
Checks
Run these when examples are in scope:
python tools\sync_reference_project.py --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.
Feedback Boundary
If the reference project reveals repeated friction, classify it before changing framework code:
- project convention
- documentation suggestion
- maintenance tool improvement
- framework candidate
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.
When not to use it
- →When the task involves writing reference-project gameplay rules into addons/gf
Limitations
- →Do not write reference-project gameplay rules into addons/gf
How it compares
This skill explicitly separates the reference project as a validation surface from the core GF framework, ensuring that project-specific logic does not leak into the framework's addons.
Compared to similar skills
gf-reference-boundary side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| gf-reference-boundary (this skill) | 0 | 2mo | No flags | Intermediate |
| e2e-testing-patterns | 8 | 2mo | No flags | Intermediate |
| testing-workflow | 16 | 9mo | Review | Intermediate |
| perf-lighthouse | 13 | 5mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
e2e-testing-patterns
wshobson
Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.
testing-workflow
amo-tech-ai
Comprehensive testing workflow for E2E, integration, and unit tests. Use when testing applications layer-by-layer, validating user journeys, or running test suites.
perf-lighthouse
tech-leads-club
Run Lighthouse audits locally via CLI or Node API, parse and interpret reports, set performance budgets. Use when measuring site performance, understanding Lighthouse scores, setting up budgets, or integrating audits into CI. Triggers on: lighthouse, run lighthouse, lighthouse score, performance audit, performance budget.
xcodebuildmcp
cameroncooke
Official skill for XcodeBuildMCP. Use when doing iOS/macOS/watchOS/tvOS/visionOS work (build, test, run, debug, log, UI automation).
verify
Use when you want to validate changes before committing, or when you need to check all React contribution requirements.
playwright-pro
alirezarezvani
Production-grade Playwright testing toolkit. Use when the user mentions Playwright tests, end-to-end testing, browser automation, fixing flaky tests, test migration, CI/CD testing, or test suites. Generate tests, fix flaky failures, migrate from Cypress/Selenium, sync with TestRail, run on BrowserStack. 55 templates, 3 agents, smart reporting.