Build gameplay systems
Create components, state machines, abilities, inventory, saving, AI, UI, input, and event-driven behavior.
Codex Skills for Unity give Codex a project-aware process for writing C# gameplay code, organizing scenes and prefabs, building editor tools, managing assets, debugging physics, profiling performance, and preparing platform builds. Download the skills for Unity projects that need maintainable systems and playable verification.
task: complete unity game development task
inspect:
- requirements and context
- existing standards
- failure and edge cases
verify: outputs + checks + handoffStrong unity game development work depends on context, explicit decisions, and checks that match the real environment.
These skills give Codex a specialist workflow for unity game development while preserving local conventions, important constraints, and human review.
Create components, state machines, abilities, inventory, saving, AI, UI, input, and event-driven behavior.
Use prefabs, ScriptableObjects, packages, addressable content, serialization, and ownership deliberately.
Develop inspectors, editor windows, import processors, validators, build helpers, and content workflows.
Measure frame time, allocations, memory, rendering, physics, loading, and platform build behavior.
The steps keep context, implementation, and verification visible so the result can be reviewed and repeated.
Read editor version, render pipeline, packages, scenes, prefabs, input, assembly definitions, and targets.
Trace initialization, updates, references, events, persistence, loading, and object lifetime.
Respect architecture, serialization, asset workflows, platform constraints, and designer usability.
Test scenes and builds, use the profiler, check devices, validate assets, and document release risks.
The workflow adjusts to the project, audience, tools, and risk while preserving the same quality standard.
Build sprites, tilemaps, animation, physics, cameras, UI, and level workflows.
Develop characters, cameras, environments, navigation, physics, lighting, and rendering systems.
Reduce repetitive content work with inspectors, windows, processors, validators, and automation.
Prepare input, quality, assets, performance, permissions, signing, and package settings per target.
Start with one defined outcome and provide the source material, constraints, and checks that matter.
These skills are designed for people who need dependable unity game development work with a visible process.
Build gameplay, tools, tests, performance fixes, and platform features.
Keep scenes, content, code, and release work manageable across a small team.
Create data-driven systems and editor tools that support iteration.
Work within device performance, input, lifecycle, and platform constraints.
The skills assist Unity development, but game feel, device performance, store compliance, licensing, art quality, and release approval need hands-on review.
Install the complete skill folder and add the project-specific context before beginning.
Keep SKILL.md with the included unity game development guidance, checks, and supporting files.
Use project scope for local rules and versions, or personal scope for a reusable workflow.
Document the tools, audience, standards, source material, constraints, and approval rules for this unity game development work.
Provide the intended outcome, important edge cases, required checks, and expected handoff.
Practical answers about capabilities, limits, setup, and review.
The workflow follows the editor and package versions recorded by the project.
Yes. They work with the architecture and Unity APIs available in the project.
Yes. They can build inspectors, windows, import helpers, validators, and build automation.
They use profiling evidence to target CPU, GPU, memory, allocation, loading, and physics issues.
They can prepare and verify builds when required platform tools exist. Signing and store submission require authorization.
Clear context. Purposeful work. Relevant checks. A result others can understand.