← Prompt Library / Engineering
Spec a small internal tool or script before building it: exact inputs, outputs, failure behaviour, and the edge cases that turn a quick script into a week.
Spec this internal tool/script before I build it: {{idea}} (what it should do, who runs it, how often).
Define: exact inputs (arguments, files, env — with formats), exact outputs (including exit codes), behaviour on the boring failure paths (missing file, bad input row, network hiccup, re-run after partial completion — idempotency?), permissions and secrets handling, dry-run mode (almost always worth it — say if not), and logging (what it prints normally vs verbose). Then the scope check: which edge cases from my description turn this from an afternoon into a week — and can we exclude them for v1?
Fields like {{ this }} are placeholders — replace them with your own details, or let Aria ask you for them.
This prompt runs with Aria connected to your email, files, CRM and 40+ other services — and you can schedule it to run automatically.
Start Free WeekReview a diff for correctness, security, and readability issues.
Get a plain-English walkthrough of unfamiliar code.
Generate thorough unit tests for a function.
Diagnose an error systematically: likely causes ranked with reasoning, the cheapest test for each, a...
Build a regular expression from a plain-English requirement — explained token by token, tested again...
Turn a plain-English data question into a working SQL query — with the assumptions stated, a readabl...