/autopromptYou give Claude a rough idea, it builds the perfect prompt to get the best output.
Category: Power Commands
Before / After
Help me write a job description.
/autoprompt I need to hire a senior backend engineer for a small fintech.
What changes in Claude's response
Claude doesn't write the job description — it writes the *prompt* you should use to get a great job description, including what context to provide, what constraints to specify, and what format to ask for. Then you run that prompt. It's a meta-tool: you spend 30 seconds describing your goal vaguely and get a perfectly-engineered prompt for free.
When NOT to use /autoprompt
Skip /autoprompt for one-shot questions. The overhead only pays off if the prompt is worth saving and reusing.
Codes that stack with /autoprompt
/autoprompt is one of 120 tested prompt prefixes. The full cheat sheet has before/after examples, warnings, combos, and 10 workflow playbooks.
See the full cheat sheet — from $5More Power Commands codes
/godmodeThe most thorough, longest, most detailed response Claude can give. Use sparingly.
MEGAPROMPTGenerates a long, detailed prompt for exactly what you want — usually 500+ words.
/chainRuns multiple prompts in sequence, feeding each one's output into the next.
/systemWrites a custom system prompt you can drop into any LLM, not just Claude.
PERSONAMakes Claude respond as a specific expert. The specificity is everything.