perf
/perf
Use when a Godot game stutters, hitches, loads slowly, has low or uneven fps, uses too much memory or video memory, or when asked to optimise a Godot project. Measures first, finds the cause with Godotwright's performance review and lessons from real projects, fixes one thing at a time and measures again. Also in Dutch: "het hapert", "haperingen", "laadtijd te lang", "lage fps", "sneller maken", "te veel videogeheugen", "optimaliseren".
- Author
- laaielichter ↗
- Repository
- Godotwright ↗
- Licence
- MIT
- Last repository change
- 13.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when a Godot game stutters, hitches, loads slowly, has low or uneven fps, uses too much memory or video memory, or when asked to optimise a Godot project. Measures first, finds the cause with Godotwright's performance review and lessons from real projects, fixes one thing at a time and measures again. Also in Dutch: "het hapert", "haperingen", "laadtijd te lang", "lage fps", "sneller maken", "te veel videogeheugen", "optimaliseren".
Triggers from the description
Arguments
/perf [what is slow, optional]
Original author description
Use when a Godot game stutters, hitches, loads slowly, has low or uneven fps, uses too much memory or video memory, or when asked to optimise a Godot project. Measures first, finds the cause with Godotwright's performance review and lessons from real projects, fixes one thing at a time and measures again. Also in Dutch: "het hapert", "haperingen", "laadtijd te lang", "lage fps", "sneller maken", "te veel videogeheugen", "optimaliseren".
How it works
SKILL.md has no level-two headings · 29 lines, 388 words
SKILL.md preview
---
name: perf
description: Use when a Godot game stutters, hitches, loads slowly, has low or uneven fps, uses too much memory or video memory, or when asked to optimise a Godot project. Measures first, finds the cause with Godotwright's performance review and lessons from real projects, fixes one thing at a time and measures again. Also in Dutch: "het hapert", "haperingen", "laadtijd te lang", "lage fps", "sneller maken", "te veel videogeheugen", "optimaliseren".
argument-hint: "[what is slow, optional]"
---
# Make a Godot game faster, measured
Work on $ARGUMENTS (or what the user named). Never optimise without a number before and after.
1. **Measure first, the right way.** `godot_perf` on the scene (with `input` for what happens in it) gives frame-time
percentiles against a budget, the slowest frames and what changed on them, and keeps a baseline. Agree on one
repeatable case (a scene, a start position, a camera path, a time).
Read frame time, not fps: the worst frames (99th percentile, the longest frame) show a stutter that an average
hides. Measure an exported build or the export template when you can; editor and debug builds are slower in other
places. Alternate A and B runs in blocks, so warm caches and heat do not decide the result.
2. **Ask what real projects learned.** `godot_lessons` with topic `performance` and the symptom ("stutter when a model
loads", "hitch on first explosion", "slow start"). Typical causes: a glTF parsed on the main thread, shaders
compiled on first use, many nodes made in one frame, textures read back from the GPU, physics ticks catching up,
heavy `_process` work on things far away.
3. **Let the review point.** `godot_review` and read the `performance` category: per-frame allocations, node lookups
in `_process`, `get_image()` in loops, runtime glTF without mipmaps, small lights with cube shadows.
4. **One change at a time,** each behind a switch you can turn off, so a change that does not help can be proven
useless and removed. Spread work over frames instead of doing it in one; pool what is made and freed often; load
in the background with `ResourceLoader.load_threaded_request()`; warm shaders with the same settings as the real view.
5. **Measure again** with `godot_perf`, the same case and the same method: it shows the change since the last run. Keep the change only when the numbers say so; say how
much it helped (worst frame, average, load time, memory).
6. **Memory that grows** over a long session (or orphan nodes growing in `godot_perf`): run `godot_leaks` on the scene
that streams or reloads. It names the class, script and line of what is left behind per cycle; after the fix it
must show 0 per cycle.
7. Keep lessons with `godot_lesson_add` when a cause was hard to find.
End with a table: change, before, after, kept or dropped.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · laaielichter/Godotwright | 96 | MIT |
| duronext/jig | 100 | MIT |
| dxos/dxos | 100 | Apache-2.0 |
| anilsoylu/famiglia | 100 | Apache-2.0 |
| jisuzzzz/haechi | 100 | MIT |
| oliver-kriska/claude-elixir-phoenix | 100 | MIT |
| 8beeeaaat/touchdesigner-mcp | 100 | MIT |
| 8beeeaaat/touchdesigner-mcp | 100 | MIT |
| htlin222/dotfiles | 100 | MIT |
Database snapshot: 13.11.2026 · package version 5853de22aa2d (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 96perf-pass
Investigate and fix performance problems (low FPS, hitches, memory growth, slow loads). Use when the user mentions lag, stutter, frame drops, or high memory. Measures first, fixes the top offender, remeasures. - 100game-perf-budget
Diagnoses and fixes game performance problems with frame-time budgets and a measure-first workflow - finding whether a game is CPU-bound or GPU-bound, profiling in Godot, Unity and Unreal, and fixing the usual culprits (per-frame allocations, too many draw calls, overdraw,… - 96debug
Use when Godot prints an error or warning (SCRIPT ERROR, Parse Error, "Invalid access", "Cannot infer the type", a crash or a black screen), or when a Godot game behaves wrong (falls through a floor, jitters, slides off a moving platform, a node is null, a signal never fires).… - 100plan-perf-audit
Plan-only performance audit across web, mobile, backend, and data; measures first, fixes nothing. Use when "performance audit plan", "perf burndown", "measure before optimize", or "N+1 audit plan". Apply fixes → audit-performance. - 100game-perf-profiling
Profiles game builds against frame-time, memory, GPU draw-call, and GC-spike budgets using Unity Profiler + Profile Analyzer + Performance Testing package and Unreal Insights + stat commands. Establishes pass/fail thresholds (16.6 ms at 60 fps, 33.3 ms at 30 fps), writes… - 90godot-performance-optimization
Expert blueprint for performance profiling and optimization (frame drops, memory leaks, draw calls) using Godot Profiler, object pooling, visibility culling, and bottleneck identification. Use when diagnosing lag, optimizing for target FPS, or reducing memory usage. Keywords…