Bring ECC workflows to Trae IDE. This repository provides custom commands, agents, skills, and rules that can be installed into any Trae project with a single command.
# Install to current project
cd /path/to/your/project
TRAE_ENV=cn .trae/install.shThis creates .trae-cn/ in your project directory.
# Install globally to ~/.trae-cn/
cd /path/to/your/project
TRAE_ENV=cn .trae/install.sh ~
# Or from the .trae folder directly
cd /path/to/your/project/.trae
TRAE_ENV=cn ./install.sh ~This creates ~/.trae-cn/ which applies to all Trae projects.
# If already in project directory with .trae folder
cd .trae
./install.shThe installer uses non-destructive copy - it will not overwrite your existing files.
Install to the current project's .trae-cn directory:
cd /path/to/your/project
TRAE_ENV=cn .trae/install.shThis creates /path/to/your/project/.trae-cn/ with all ECC components.
Install to your home directory's .trae-cn directory (applies to all Trae projects):
# From project directory
TRAE_ENV=cn .trae/install.sh ~
# Or directly from .trae folder
cd .trae
TRAE_ENV=cn ./install.sh ~This creates ~/.trae-cn/ with all ECC components. All Trae projects will use these global installations.
Note: Global installation is useful when you want to maintain a single copy of ECC across all your projects.
- Default: Uses
.traedirectory - CN Environment: Uses
.trae-cndirectory (set viaTRAE_ENV=cn)
# From project root, force the CN environment
TRAE_ENV=cn .trae/install.sh
# From inside the .trae folder
cd .trae
TRAE_ENV=cn ./install.shNote: TRAE_ENV is a global environment variable that applies to the entire installation session.
The uninstaller uses a manifest file (.ecc-manifest) to track installed files, ensuring safe removal:
# Uninstall from current directory (if already inside .trae or .trae-cn)
cd .trae-cn
./uninstall.sh
# Or uninstall from project root
cd /path/to/your/project
TRAE_ENV=cn .trae/uninstall.sh
# Uninstall globally from home directory
TRAE_ENV=cn .trae/uninstall.sh ~
# Will ask for confirmation before uninstalling- Safe removal: Only removes files tracked in the manifest (installed by ECC)
- User files preserved: Any files you added manually are kept
- Non-empty directories: Directories containing user-added files are skipped
- Manifest-based: Requires
.ecc-manifestfile (created during install)
Uninstall respects the same TRAE_ENV environment variable as install:
# Uninstall from .trae-cn (CN environment)
TRAE_ENV=cn ./uninstall.sh
# Uninstall from .trae (default environment)
./uninstall.shNote: If no manifest file is found (old installation), the uninstaller will ask whether to remove the entire directory.
Commands are on-demand workflows invocable via the / menu in Trae chat. All commands are reused directly from the project root's commands/ folder.
Agents are specialized AI assistants with specific tool configurations. All agents are reused directly from the project root's agents/ folder.
Skills are on-demand workflows invocable via the / menu in chat. All skills are reused directly from the project's skills/ folder.
Rules provide always-on rules and context that shape how the agent works with your code. All rules are reused directly from the project root's rules/ folder.
- Type
/in chat to open the commands menu - Select a command or skill
- The agent will guide you through the workflow with specific instructions and checklists
.trae/ (or .trae-cn/)
├── commands/ # Command files (reused from project root)
├── agents/ # Agent files (reused from project root)
├── skills/ # Skill files (reused from skills/)
├── rules/ # Rule files (reused from project root)
├── install.sh # Install script
├── uninstall.sh # Uninstall script
└── README.md # This file
All files are yours to modify after installation. The installer never overwrites existing files, so your customizations are safe across re-installs.
Note: The install.sh and uninstall.sh scripts are automatically copied to the target directory during installation, so you can run these commands directly from your project.
- Start with planning: Use
/plancommand to break down complex features - Write tests first: Invoke
/tddcommand before implementing - Review your code: Use
/code-reviewafter writing code - Check security: Use
/code-reviewagain for auth, API endpoints, or sensitive data handling - Fix build errors: Use
/build-fixif there are build errors
- Open your project in Trae
- Type
/to see available commands - Enjoy the ECC workflows!