Migration Guide
If you're familiar with Cursor, GitHub Copilot, or other AI editors, you can use the following table to quickly map concepts when migrating to Tuanjie AI (Unity China's programming agent for game development), then dive into the linked documentation.
Concept Mapping
| Concept You Know | Corresponding in Tuanjie AI |
|---|---|
| Chat / Ask | Multi-turn conversations in Cowork, IDE extensions, or CLI; see Overview, CLI |
| Agent / Auto-execute multi-step | Main conversation + tools/MCP + Subagents; overview in Core Workflows |
| Rules / Project constraints | Configure rules, CODELY.md, Commands/Skills; see AI Rules & Project Conventions |
| @Files / @Folders | IDE and CLI behavior differs slightly: @ in conversations often relates to Subagents; @path in CLI references files/directories; see Context & Mentions |
| Cmd K / Inline code edit | Select code, describe modifications in Tuanjie AI, with @ or screenshots; see Core Workflows |
| MCP | MCP Servers |
| Codebase Indexing / Semantic Search | In-project understanding via Cowork; public repository search via Code Search |
Suggested Migration Steps
- Choose your form: Based on your preference, select Cowork, VS Code / JetBrains / Visual Studio extension, or CLI.
- Migrate rules: Consolidate your existing "team standards" into
CODELY.mdor configurerules, see AI Rules & Project Conventions. - Migrate workflows: Turn high-frequency prompts into Commands, and domain-specific workflows into Skills.
- Connect external systems: Re-connect services you previously used in Cursor etc. via MCP.