AUTOMATETurns a manual process you described in English into a runnable script.
Category: Coding & Technical
Before / After
Write me a script that does [thing].
AUTOMATE Every Monday I download 4 CSVs from S3, join them on customer_id, and email the result to ops@. I want this to run automatically.
What changes in Claude's response
Claude doesn't just write the script — it asks the structural questions first: where should it run (cron, Lambda, GitHub Actions)? What credentials are available? What happens when one of the CSVs is missing? Then it writes the script with logging and error notifications baked in. The output is the entire automation, not just the code.
When NOT to use AUTOMATE
Don't AUTOMATE one-off tasks. Building an automation for something you'll do twice in your life is more work than just doing it.
Codes that stack with AUTOMATE
AUTOMATE 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 Coding & Technical codes
/debugFinds the bug and tells you exactly where it is, not what bugs look like in general.
REFACTORCleans up messy code without changing what it does. Tells you what changed and why.
/shipitAdds the production-readiness layer Claude usually skips: error handling, edge cases, types, logging.
ARCHITECTDesigns system structure before any code is written. Forces decisions, doesn't just list options.
/convertRewrites code in another language idiomatically — not transliterated.