Cursor Custom Commands Tutorial for Testers: Turn Your Repeated Prompts Into One Slash Command

Typing the same long prompt every day? In this Cursor custom commands tutorial for testers, I show how to save repeated prompts as markdown files in .cursor/commands, run them with a slash, add details after the name, and share them with your team in git. Plus commands vs rules vs skills, what the latest documentation recommends, a tester starter pack, and examples for manual, API, performance and automation testing. This is Episode 11 of The Cursor-Powered Tester, a Cursor AI for testing series on Automate With SDET. You'll learn: ✅ What a custom command is (a saved prompt in a .md file) ✅ Where commands live: .cursor/commands and ~/.cursor/commands ✅ Running a command and adding details after the name ✅ Commands vs rules vs skills ✅ The newer way: skills + /migrate-to-skills ✅ Writing and naming good commands ✅ A tester starter pack of 5 commands Chapters 0:00 Intro: the same long prompt 1:00 Episode 10 recap 1:24 What a command is 1:58 Where commands live 2:35 Your first command 3:12 Running a command 3:40 Adding details 4:10 Commands vs rules vs playbooks 4:44 What the documentation says now 5:26 Writing a good command 6:01 Naming commands 6:32 Quick quiz 7:05 5 commands for testers 7:26 Example: manual testing 8:04 Example: bug reports 8:36 Example: API testing 9:10 Example: performance testing 9:40 Example: automation testing 10:16 Commands + context 10:47 Before / after commands 11:20 Creating commands quickly 11:48 Best practices 12:17 Limits + safety 12:49 When to upgrade 13:15 Cheat sheet 13:50 Recap 14:15 Homework + next: Hooks Links Skills, incl. slash-only skills + /migrate-to-skills (Cursor documentation): https://cursor.com/docs/skills Rules (Cursor documentation): https://cursor.com/docs/rules Note: the old commands page now redirects to Skills; .cursor/commands files still work (as of Oct 2026). Features, menus, plans and prices are as described at the time of recording (October 2026) and can change. Screens in this video are illustrations, not exact screenshots. Follow your company's policy before using AI tools on work data, and never paste real customer data into a prompt. Previous episode: Cursor Subagents for Testers (Ep 10) Next episode: Cursor hooks for testers: auto-check AI edits and block risky commands (Ep 12) Subscribe to The Cursor-Powered Tester on Automate With SDET. Instagram: @automatewithsdet #CursorCommands #CursorAI #SlashCommands #CursorCustomCommands #CursorRules #CursorAgent #PromptEngineering #CursorAITutorial #CursorAIForTesting #CursorForTesters #TheCursorPoweredTester #AIinTesting #QATesting #SoftwareTesting