Give the code enough context
Name the engine or language, the relevant component, and the behavior that should remain unchanged.
AI-powered code editor for game development
Describe the change, its code context, and how you will check it.
Use a focused task—such as adjusting a Unity controller or adding an interaction to a Three.js game—to explore a code change. Include the expected behavior and an edge case, then inspect and test the result in its project context.
Get started with
- Free starter credits
- No coding required
- Review cost before generating
- Runs in your browser
How it works
How to describe and review a game code task
A specific request gives code changes a clear purpose. Add context, inspect the result, and test it in the project that will use it.
- State the task
Say what should change
Describe the player action or output you want, and name the part of the game that should respond.
- Add context
Show the code environment
Include the relevant engine or language, surrounding behavior, and any conventions the change must keep.
- Set a check
Define the expected result
Explain how success should look and include one edge case worth testing.
- Inspect the code
Review the change in context
Check dependencies, state updates, and neighboring behavior before using the result.
- Run the test
Verify it in the project
Try the normal interaction and the edge case. Note what passed and what still needs a revision.
Pick a starting point
Choose a game coding task to explore
Start with a controller, a Three.js interaction, a reproducible bug, or a small game interface.
Tune a player controller
Describe the input, movement response, and the condition you want to test.
Prompt
For a Unity third-person controller, add a short sprint while the player holds Left Shift. Keep the existing walk speed and jump behavior. Explain where the change belongs, avoid changing camera controls, and include a check for releasing the key while airborne.
- Name the input and expected response
- Keep unrelated movement behavior unchanged
- Test the edge case as well as the normal action
Make movement behavior explicit ↗Why SEELE
What to include in a code request
Describe the expected behavior
Write what the player does and what the game should show or change in response.
Include an edge case
Call out a boundary condition—such as repeated input, missing data, or a restart—and check it separately.
Review the proposed change
Inspect how the code fits its surrounding state, events, and project conventions before using it.
Test in the project context
Run the change with the intended controls and scene. Check both the normal path and the edge case from the brief.
Keep revisions easy to compare
Change one behavior at a time and record what passed or still needs attention.
Who it’s for
Who can use an AI-powered code editor
Use a small code task to explore a behavior, learn how game state changes, or refine a browser game.
Indie developers editing game behavior
Describe one code task and its surrounding project rules before trying a small change. Review the result in context and test the player-facing behavior.
AI 3D Game Maker with Code ↗
Three.js creators building browser games
Use a focused brief for scene interactions, UI state, or controls, then verify the result in the browser and across relevant inputs.
Three.js Editor ↗
Students learning game programming
Compare a small code change with its expected behavior. Use one test case to understand how input, state, and feedback connect.
Browser 3D Game Maker ↗Compare
Compare an AI-assisted code task with a manual edit
Both workflows require project context and testing. Choose how to begin based on your current code and task.
| Feature | AI-assisted code task | Manual code edit |
|---|---|---|
| Describe the change | State the component, expected behavior, and one constraint. | Write down the same requirements before editing the project. |
| Provide context | Include the relevant engine, language, and existing behavior. | Locate the surrounding code and project conventions. |
| Consider an edge case | Name one boundary condition to include in review. | Add an edge case to the implementation checklist. |
| Inspect the result | Check the proposed change against nearby code and project state. | Review the changed files and surrounding logic. |
| Verify behavior | Run the task in its intended project and test the stated case. | Run the project and test the same case before merging. |
Reviews
Creator videos about SEELE AI
These creator videos cover broader SEELE AI workflows. Confirm current editor options before relying on a specific capability.
Related game creation pages
Explore related editors, game makers, guides, and tools for common game development tasks.
Guides for game code and prototyping
Three.js Games: Examples and How to Build OneGame development guideHow to Design an AI Game Loop with Practical PrototypingGame design guideAI Game Prototyping GuideGame prototyping guide
Tools for game assets and interface ideas
AI Game UI Generator ToolGame UI Icon GeneratorAI 3D Environment Asset GeneratorAI Game Asset Generator ToolAI Game Mission GeneratorAI Achievement Generator
Game code concepts in this page
Code contextExpected behaviorEdge casePlayer inputGame loopEvent handlerGame stateCollision eventDebuggingCode reviewTest caseThree.js
FAQ
AI code editor questions
What is an AI-powered code editor?
An AI-powered code editor uses a written request and code context to assist with programming tasks. Review suggested changes in the surrounding project and test them before relying on them.
Can an AI code editor help with game development?
It can help you explore a focused game coding task, such as a controller change, a scene interaction, or a UI state. Include the expected behavior and verify the result in the intended project.
What should I include in a game code prompt?
Name the engine or language, the relevant component, the desired behavior, and one constraint. Add an edge case or short test that would show whether the change worked.
Can I use this page for Unity code tasks?
The examples include a Unity player controller task. Check the current editor and project workflow for supported inputs, then test any proposed code in the Unity project that will use it.
Can I use this page for Three.js games?
The examples include a Three.js browser game interaction. State the relevant scene object and expected browser behavior, then verify the code with the project’s current Three.js setup.
Can an AI code editor debug a game automatically?
Do not assume every issue can be detected or fixed automatically. Share a reproducible error, the relevant code, and the expected result; inspect any suggestion and test it yourself.
How do I describe a bug clearly?
List the steps that reproduce it, what happened, and what should have happened. Include the smallest relevant code sample or error message and note whether the bug appears every time.
How should I test a suggested code change?
Run it in the intended project, test the main interaction, and check the edge case named in the request. Confirm that nearby behavior still works.
Can an AI code editor write a complete game?
A code suggestion is not a substitute for a complete game plan or project review. Break the idea into testable tasks and integrate changes against the project’s actual requirements.
Does SEELE AI support code export to Unity?
Available export and engine options can change by workflow. Check the current editor for supported formats and verify that any output opens and behaves as expected in the target project.
Is an AI-powered code editor free?
Plan access, model choices, and generation costs can vary. Check the current balance and displayed cost in the editor before starting a task.
Can I use the editor to create game UI code?
The examples include a pause menu with Resume, Restart, and Sound controls. Describe the screen state and the result of each action, then test the controls after starting and restarting the game.
What should I review before using generated code?
Check whether the change matches the request, follows project conventions, handles the named edge case, and behaves correctly in the target runtime. Review security and licensing requirements where relevant.
How can students learn from an AI code suggestion?
Ask for a small change, compare the code with the expected behavior, and trace how input changes game state. Test one case, then explain what each changed part does.
Describe one game code change
Include the project context and a behavior you can test. Review the result before using it in a larger feature.
Start a code task →