I had an idea based on my own workflow: I often find myself typing frantically and repeating the same commands over and over. Would it be possible to develop Cursor’s chat prompt to include small programmable pads/buttons right below the prompt?
For example, user-configurable quick-action pads for frequently used commands or instructions.
Good news, you can get this today. Put your repeated instructions in skill files (create .cursor/skills/<name>/SKILL.md in your project, or under ~/.cursor/skills to make them available everywhere), and they become commands you can trigger by typing / in the chat input.
Even closer to what you described: in the / menu you can right click a skill and choose Pin, and it will show up as a clickable button right by the chat prompt. Right click the button again to unpin it. Just make sure you are on a recent Cursor version.
Thanks Colin! I wasn’t quite referring to Skills/Pin specifically, though. I may not have explained the idea clearly enough.
What I had in mind was a more general programmable quick-action pad/button system directly below the chat prompt.
For example, I could have buttons such as:
PLAN | IMPLEMENT | AUDIT | TEST | REFACTOR | WRAP-UP
Each button would be user-configurable and could contain a complete prompt/instruction, a Skill, or potentially even a predefined workflow.
The key idea is that these would function more like user-programmable action buttons/macros than simply pinned Skills. I would click a button and Cursor would immediately insert or execute the associated instruction or workflow in the current chat context.
So the feature request is really about a general programmable quick-action UI below the chat input, where users can create, edit, reorder, rename and configure their own actions.
Skills + Pin are definitely useful and seem related, but they don’t quite cover the UI/workflow concept I was suggesting.
I can actually build a small external tool to do this myself, so this isn’t a blocker for me. I already have an external application I’m developing that can control/drive Cursor as part of my workflow. I’m mainly suggesting this as a native Cursor UX feature, because I think having programmable actions directly available in the chat UI could be useful to many users.