← ClaudeAtlas

gat-reference-firstlisted

Run the mandatory reference-first gate before implementing, refactoring, or fixing a Godot feature. Inspect the project's analogous code first, then read a small licensed upstream implementation, pin its revision, map source behavior into the current architecture, and validate the evidence map with tools/reference_gate.py. Use for 实现, 修复, 重构, 借鉴代码, learn from code, reference implementation, or any /gat-implement work.
chenhangcuisg-code/gat · ★ 7 · AI & Automation · score 69
Install: claude install-skill chenhangcuisg-code/gat
# gat-reference-first — inspect, map, then implement Request: $ARGUMENTS Do not start a substantial Godot implementation from memory. Reuse the project's established shape, then borrow one concrete pattern from licensed source code and adapt it deliberately. Read `docs/reference-first.md` for source selection, licensing, and evidence details. ## Procedure 1. **Freeze the request.** Split every user requirement into an observable acceptance criterion. Work through them one by one; do not replace coverage with “the main parts are done.” 2. **Survey the current project.** Use `rg --files` and `rg` to trace the entry point, caller, state/data owner, save behavior, UI/scene, existing tests, and at least one analogous local implementation. Protect unrelated dirty-worktree changes. 3. **Select references with progressive disclosure.** Prefer, in order: - current project code and its tests; - one project-configured upstream Godot codebase or focused skill; - official Godot docs for the exact engine version. Read at most one broad upstream guide and one to three focused files. Never ingest a whole skill library when one module answers the question. 4. **Check rights before reuse.** Record repository URL, pinned commit, license, exact files, and reuse mode (`concept`, `adapted`, or `copied`). Unknown or incompatible license means clean reimplementation from behavior, not copying. Never carry names, assets, credentials, host information, private end