12 prompts
Write unit tests for the function below using [TEST FRAMEWORK]. Cover the happy path, edge cases, and likely failure modes. Use clear test names that describe the scenario. Point out any behavior that's hard to test (a sign it might need refactoring). Function: [PASTE]
Write a regex that matches [WHAT TO MATCH] and does NOT match [WHAT TO EXCLUDE]. Show the pattern, explain each part, and give me 3 test strings that should match and 3 that shouldn't. Flavor: [JavaScript / Python / PCRE].
Write a SQL query for this: [WHAT I WANT]. My tables/columns are: [SCHEMA]. Use [dialect: PostgreSQL / MySQL]. Explain the query in one line, and mention if there's a more efficient way.
Convert this code from [LANGUAGE A] to [LANGUAGE B]. Keep the logic identical and make it idiomatic for the target language, not a literal line-by-line translation. Note anything that doesn't map cleanly. Code: [PASTE]
I need to build [FEATURE / THING]. Before I write any code, help me think it through: ask me any clarifying questions first, then outline an approach, the main components, edge cases to handle, and a suggested order to build it in. Don't write the code yet.
The code below is slow / resource-heavy. Identify the bottleneck, explain why it's costly (time/space complexity), and give me an optimized version. Note the tradeoffs of your approach. Code: [PASTE]
Add clear docstrings and comments to the code below. Document what each function does, its parameters, and return value. Comment only the non-obvious logic — don't state the obvious. Keep the code itself unchanged. Code: [PASTE]
I want to build [FEATURE] in [STACK]. Ask clarifying questions, then propose an approach and components.
Help me implement [COMPONENT], explaining key decisions.
Give me the file/function structure and stubs for that approach.
Review the finished feature like a senior engineer and list must-fixes.
Write unit tests covering happy path and edge cases.