← Prompt Library / Engineering
Structure a performance investigation: measure first, form hypotheses from the symptom pattern, and test them cheapest-first — before touching any code.
Something is slow: {{symptom}} (what's slow, for whom, since when, what's been ruled out). Stack: {{stack}}.
Structure the investigation: (1) Measure first — what exact number defines 'slow', and the measurement to run before ANY fix (baseline or we can't prove improvement). (2) Hypotheses ranked by the symptom pattern — sudden vs gradual, all users vs some, constant vs spiky each point to different causes; explain the reasoning. (3) For each hypothesis: the cheapest test that confirms or kills it. (4) The classic traps for my stack. Rule: no optimisation until a measurement points at the culprit — guessing wastes more time than measuring.
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...