gdshader-general

EEEEEEEEthan

Documents common mistakes to avoid in Godot gdshader development and ways to mitigate them. Intended as a quick anti-pitfall checklist when writing, refactoring, and debugging shaders—especially useful when encountering cracks, hard seams, fake-looking materials, repeating textures, or performance issues.

General Coding Guidelines

EEEEEEEEthan

General coding conventions, such as requiring local and loop variables to have full, descriptive names and forbidding single-letter names or vague abbreviations. Intended for use when writing or reviewing code in C#/GDScript and similar languages.

skill-optimize

EEEEEEEEthan

Refine and polish existing skill content by writing back improvements based on the actual process of the current work, issues explicitly pointed out by the user, and the skills actually used in this session. Intended for when the user explicitly requests “optimize skill”, “polish skill”, or “optimize skills based on this work experience.”

code-optimize

EEEEEEEEthan

Code optimization to reduce maintenance costs, with an emphasis on minimizing class members. Use during code reviews, refactoring, or performance optimization. Follow principles such as encapsulation and reuse, inlining methods that are called only once, and removing redundant logic.

Godot Script

EEEEEEEEthan

Best practices for writing Godot scripts, covering node initialization timing, use of @onready, avoiding defensive coding, and more. Intended for use when writing GDScript.

git-create-branch

EEEEEEEEthan

Parse source/target and safely create a Git branch, handling ambiguous source names, illegal target characters, and name conflicts, then switch and set the default push upstream. Used when a user requests to create a new branch, switch branches, or 'create a new branch from an existing branch'.

Bugfix Skill

EEEEEEEEthan

Provides principles and techniques for fixing bugs, ensuring that fixes are correct, clean, and maintainable. Use this when debugging, repairing issues, reviewing bug fixes, or when you need guidance on proper bug resolution.

naming-skill

EEEEEEEEthan

A must-read whenever you need to name anything.

api-design

EEEEEEEEthan

Design clear public APIs, encapsulate internal state, avoid ambiguity, and provide a unified interface. Use when designing class methods, encapsulating internal state, or creating public interfaces.

code-optimize

EEEEEEEEthan

Code optimization to reduce maintenance costs, with an emphasis on minimizing class members. Used during code reviews, refactoring, or optimization. Follows principles such as encapsulation and reuse, inlining methods that are called only once, and removing redundant logic.

godot-engine

EEEEEEEEthan

Usage and behavior guidelines for the Godot engine when working with engine objects, layout, sizes, CallDeferred, process_frame, and Engine.IsEditorHint.