
Start From A Precise Brief
Carry a concrete asset request into Workspace with the intended use and constraints already named.
Use this promptSEELE AI · Tool
Plan a reviewable retopology route for a game asset, then continue the exact technical brief in SEELE Workspace. Mesh revisions remain drafts until topology, shading, deformation, baking, scale, rights, and destination checks pass.
This tool turns a mesh-cleanup goal into an editable retopology brief and carries the exact prompt into SEELE Workspace. A revised mesh remains a draft until topology, shading, deformation, baking, rights, and destination checks pass.

The working loop
Keep intent, constraints, and review criteria visible through the first pass.
Name the asset type, source condition, deformation needs, camera distance, target engine, and the problem the topology pass should solve. The prompt enters Workspace with source constraints and acceptance criteria visible.
Protect silhouette, deformation zones, hard edges, seams, material boundaries, and bake requirements while removing geometry that does not contribute. The Workspace thread supports iteration around the same technical brief without claiming an automatic approved result.
Inspect manifoldness, normals, UVs, bake artifacts, deformation, scale, naming, and runtime behavior in the actual destination. A human decides whether the revised mesh meets the project contract.
What leaves the page
The handoff is designed to produce concrete material for iteration, not an automatic shipping claim.
A source-to-destination plan that names silhouette, deformation, shading, UV, baking, and runtime constraints.
A structured direction for edge flow and mesh reduction that can be compared against the original asset.
Checks for normals, manifoldness, UVs, bake artifacts, deformation, scale, naming, and target-engine behavior.
Fit and limits
Before you start
Retopology rebuilds or reorganizes a mesh so its geometry better fits deformation, shading, UV work, baking, editing, and runtime needs. The appropriate route depends on the asset, representative camera distance, motion, materials, target engine, and hardware. A lower polygon count alone does not prove that a topology pass is successful.
No. This page structures a retopology brief and carries the exact prompt into SEELE Workspace for continued iteration. A revised mesh remains a draft until a person inspects topology, manifoldness, intersections, normals, seams, UVs, baking, deformation, scale, naming, collision, rights, and behavior in the intended destination.
Include the asset type, source condition, target engine, representative camera distance, deformation needs, silhouette priorities, hard edges, UV and baking requirements, material boundaries, scale, and acceptance checks. Explain what the topology pass should improve and which visual or technical characteristics must remain unchanged during reduction or reconstruction.
Yes. Selecting a starter replaces the editable prompt-box value, and the primary action appends that exact text as the prompt query parameter on the Workspace URL. You can review or revise the prompt before continuing, which makes the handoff explicit and avoids relying on hidden page state or a generic Workspace link.
No. Geometry changes should be judged against silhouette, deformation, shading, UV seams, material boundaries, draw setup, collision, scene density, target hardware, and measured behavior in the actual destination. Removing geometry can create visible or technical regressions, so an agreed budget and representative tests are more useful than an isolated polygon number.
Review manifoldness, intersections, normals, edge flow, UVs, bake artifacts, deformation, scale, pivots, naming, materials, collision, licensing, and target-engine behavior. Compare the revised mesh with the source at representative camera distances and poses. A person should approve the result only after the asset passes the project’s actual visual and technical contract.
Next move
Choose or edit a prompt, then carry the exact brief into SEELE Workspace for the next iteration.
Choose A Starting Route
Each card selects a complete prompt that remains editable before the Workspace handoff.

Carry a concrete asset request into Workspace with the intended use and constraints already named.
Use this prompt
Choose another starter prompt to explore a materially different route without rewriting the request from scratch.
Use this prompt
Frame the checks a human should complete before the result enters a game project.
Use this promptA Practical Handoff, Not A One-Click Promise
The page stays inside capabilities that can be represented honestly and reviewed in the target workflow.

Select a starter prompt or edit the brief, then send the exact text into SEELE Workspace as the prompt parameter.
Open Workspace
Name the target engine, camera distance, animation needs, and delivery constraints before deeper asset work begins.
Open Workspace
Treat generated or revised assets as drafts until geometry, materials, scale, rights, and runtime fit have been checked.
Open WorkspaceStructured Handoff Versus An Unscoped Request
A structured brief makes review criteria visible before deeper production work.
| Dimension | Structured SEELE handoff | Unscoped request |
|---|---|---|
| Input | Use, constraints, and review target are named | Goal and constraints may remain implicit |
| Continuation | Exact prompt continues into Workspace | Context may need to be recreated |
| Review | Human checks are listed before production use | Acceptance criteria may be unclear |
Who Can Use This Workflow
Built for teams preparing or reviewing 3D game assets.
Structure an asset brief and the checks needed before approval.
Open WorkspaceName topology, scale, material, engine, and runtime constraints before iteration.
Open WorkspaceCarry one shared prompt from planning into a reviewable Workspace thread.
Open Workspace