I frequently perform repetitive commands in the Composer Agent and would like a way to define shorthand commands that expand into detailed instructions.
Feature Idea
• A simple interface or text file where users can predefine short “trigger words” mapped to longer explanations.
• When writing a command prefixed with “CC:”, the Composer Agent should reference this file to retrieve the full explanation.
Example Use Cases
- Expanding Technical Commands:
• Input:
CC: iOS TF
• Expansion:
“Go to pubspec.yaml, increase the version number by one. Then go to the correct iOS folder in the project folder. Then build a new archive in Xcode and upload to Testflight.”
- Controlling AI Behavior:
• Input:
CC: OT: Add button to delete row in database
• Expansion:
OT: means “Only talk, do not implement any code. We’re just discussing together. Explain and show but do not implement.”
Why This Matters
• Efficiency Boost: Reduces repetitive typing for power users.
• Enhanced Workflow: Enables users to encode their own workflows as shortcuts.
• Fills a Gap: .cursorrules do not work in Composer Agent, making this a much-needed alternative.
This would make Composer Agent significantly more useful for advanced users who rely on structured workflows.