You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Trae Support, is currently broken, and not well implemented, to better take advantage of features within trae
With Some recent changes and Updates, Trae IDE, now Supports, Custom /Slash Commands, as well as .agents/skills folder support.
We are not limited to .trae/skills let improve the Integration of Speckit, to properly integrate with the skills, as well as Commands.
Proposed Solution
Trae, Does support global rules, lets Implement it in a way, a user, is asked whether they need global support, or project only. this way, relevant skills as well as rules, and /slash commands, can be implemented, fro trae.
Alternatives Considered
No response
Component
Specify CLI (initialization, commands)
AI Agent (if applicable)
None
Use Cases
using slash commands, inside trae, would work without issues.
it would be possible to implement globally
This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed in 30 days if no further activity occurs.
This issue has been automatically closed after 90 days without activity. To request reconsideration, please provide updated reproduction details, the currently affected version or environment, and the present impact. Ask a maintainer to reopen this issue if it is fundamentally the same problem. If the scope or reproduction has materially changed, create a new issue, link this one, and explain what has changed.
Activity
github-actions commentedon Sep 11, 2026
This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed in 30 days if no further activity occurs.
github-actions commentedon Oct 11, 2026
This issue has been automatically closed after 90 days without activity. To request reconsideration, please provide updated reproduction details, the currently affected version or environment, and the present impact. Ask a maintainer to reopen this issue if it is fundamentally the same problem. If the scope or reproduction has materially changed, create a new issue, link this one, and explain what has changed.