بنقرة واحدة
refactor
// This skill should be used when the user asks to refactor code, do a refactor pass, clean up code, extract a class or service, inject a dependency, or make incremental improvements to existing code structure.
// This skill should be used when the user asks to refactor code, do a refactor pass, clean up code, extract a class or service, inject a dependency, or make incremental improvements to existing code structure.
Use when adding, modifying, or reasoning about Gluj/Glux file format versions, the GluxVersions enum, FileVersion checks, or anything that gates behavior on the version of a loaded Glue project.
Use when working on Glue's Gum code generation — adding/removing/version-gating generated properties on Gum standard runtime types (NineSlice, Text, Container, Sprite, etc.), or debugging "why is/isn't this Gum variable being generated."
| name | refactor |
| description | This skill should be used when the user asks to refactor code, do a refactor pass, clean up code, extract a class or service, inject a dependency, or make incremental improvements to existing code structure. |
| version | 1.0.0 |
See REFACTORING.md for the full philosophy, checklist, and status of ongoing refactoring efforts.
Incremental is good. A small step in the right direction — even if it doesn't finish the job — is valuable. You do not need to complete an entire refactor in one pass. Leave the code measurably better without rewriting everything at once.