raylib profiling and builds
Diagnoses native or web build problems using the actual compiler, target and resource paths. It separates memory misuse from performance bottlenecks and records a reproducible build or gameplay check.
raylib-profiling-build
See how it helpsWhen is it useful?
Use when a raylib game crashes, slows down or cannot locate packaged assets.
What does it help you do?
- Records compiler, library, target and reproduction command.
- Separates memory misuse from CPU or graphics bottlenecks.
- Checks working-directory assumptions and packaged files without replacing existing build tooling.
Try asking this
Our packaged puzzle game works from the IDE but cannot find fonts when launched elsewhere. Reproduce with the release executable, inspect asset paths and build flags, then check a crowded board for allocations and frame cost. Keep packaging and performance findings separate.
Detailed documentation
Read the skill’s original instructions, examples and checks in their authored language.
Show less
raylib — profiling build
Use when diagnosing raylib crashes, performance or native/web build and asset path failures.
Version and project gate
Inspect The local raylib.h version, linked library, C/C++ build system, platform backend, asset paths, compile flags and ownership conventions. Match the cheatsheet to the linked version rather than assuming the current website API. Never turn a task into an engine upgrade without the user’s intent. Read the version-matching official reference when an API decision depends on it.
Work
Capture compiler, library, target and reproduction command. Distinguish memory misuse from CPU/GPU load; use available sanitizer or profiler evidence when execution is authorized. Check runtime working directories and packaged assets. Preserve the project’s existing build tooling.
Deliver
A reproducible issue, narrow fix and exact build/run instructions with measured or unavailable checks labeled. Keep the change in the existing project structure; separate actual observations from the proposed acceptance scenario below.
Failure to prevent
A debug desktop executable does not establish release or WebAssembly behavior; do not add an engine-sized framework to solve a path bug.
Acceptance scenario
Run from another working directory, omit a required packaged file and replay the busy gameplay scenario on the intended target. Follow the project’s execution and verification permissions. If execution or a target device is unavailable, provide the reproduction steps and name the remaining uncertainty; do not mark it passed.
Scope and sources
This skill belongs to Flint. Agent selection is restricted by Orqestria’s assigned-agent policy, including forced skill selection; instruction text alone is not an access control. These are original task workflows researched from official documentation, not a copied or endorsed vendor skill.
Included files 1
SKILL.md