50 ChatGPT Prompts for Australian Developers (2026)

These prompts are designed for Australian software developers using ChatGPT, Claude, or any capable AI assistant. Copy them directly, or adapt them to your specific language, framework, or context. The more specific you are about your situation, the better the output.

Code Generation

1. "Write a [language] function that [describe what it should do]. It should handle [edge cases]. Include error handling and add comments explaining the logic."

2. "Generate a REST API endpoint in [framework] that [describe the endpoint]. Include input validation, error responses, and a brief docstring."

3. "Write a [language] class for [describe the class purpose]. Include constructor, key methods, and type annotations. Follow [naming convention] conventions."

4. "Create a database migration script in [ORM/framework] that [describe the schema change]. Include both up and down migrations."

5. "Write a [language] script that reads from [data source], processes [describe transformation], and outputs to [destination]. Include logging."

6. "Generate boilerplate for a [framework] project with [describe features: auth, database, API, etc.]. Include folder structure and key configuration files."

7. "Write a [language] utility function that [describe purpose]. It should be pure, well-typed, and include JSDoc/docstring comments."

8. "Create a [language] implementation of [algorithm or data structure]. Include time and space complexity comments and example usage."

Debugging

9. "I'm getting this error: [paste error and stack trace]. Here is the relevant code: [paste code]. What is likely causing this and how do I fix it?"

10. "This function is returning [unexpected result] when I pass [input]. Expected output is [expected]. Here is the code: [paste code]. What is wrong?"

11. "My [framework] application is slow when [describe scenario]. Here is the relevant code: [paste code]. What are the likely performance bottlenecks and how do I address them?"

12. "I have a race condition in this code: [paste code]. Explain what is happening and suggest how to fix it."

13. "This SQL query is returning incorrect results: [paste query]. The schema is: [describe schema]. What is wrong with the query?"

14. "My [language] code works locally but fails in production with this error: [paste error]. What environment differences might cause this?"

15. "I'm getting a memory leak in this [language] code: [paste code]. What is causing it and how do I fix it?"

Code Review

16. "Review this [language] code for potential issues: [paste code]. Focus on security vulnerabilities, performance problems, and maintainability concerns."

17. "What are the potential security issues in this code? [paste code]. I'm particularly concerned about [input validation / SQL injection / auth / etc.]."

18. "How would you refactor this function to be more readable and maintainable? [paste code]. Keep the same behaviour but improve the structure."

19. "Does this code follow [SOLID / DRY / KISS] principles? [paste code]. Explain any violations and suggest improvements."

20. "Review this pull request diff for issues: [paste diff]. What should be changed before merging?"

21. "Is this code thread-safe? [paste code]. Explain any concurrency issues and how to address them."

22. "What test cases am I missing for this function? [paste function]. List edge cases and error conditions I should test."

Documentation

23. "Write a README for this project: [describe the project, its purpose, and key features]. Include installation, usage, and contributing sections."

24. "Generate JSDoc/docstring comments for these functions: [paste functions]. Include parameter types, return types, and brief descriptions."

25. "Write API documentation for these endpoints: [paste endpoint definitions]. Use a clear format with request/response examples."

26. "Create a CHANGELOG entry for these changes: [describe changes]. Follow the Keep a Changelog format."

27. "Write inline comments for this complex function explaining what each section does: [paste function]."

28. "Create a technical design document for [describe feature or system]. Include overview, architecture decisions, data model, and API design."

Architecture and Design

29. "I need to design a system that [describe requirements]. What architecture would you recommend and why? What are the trade-offs?"

30. "Compare [option A] vs [option B] for [use case]. What are the pros and cons of each for an Australian startup with [describe constraints]?"

31. "How should I structure a [framework] application that needs to [describe requirements]? Suggest a folder structure and explain the reasoning."

32. "What database design would you recommend for [describe data model and access patterns]? Explain your choice of relational vs NoSQL."

33. "I'm designing an API for [describe purpose]. What endpoints should I create and what should the request/response shapes look like?"

34. "How should I handle [authentication / caching / rate limiting / logging] in a [framework] application? Describe the approach and key implementation decisions."

35. "What are the main risks in this architecture? [describe architecture]. How would you mitigate them?"

Testing

36. "Write unit tests for this function using [testing framework]: [paste function]. Cover happy path, edge cases, and error conditions."

37. "Write integration tests for this API endpoint: [paste endpoint code]. Include tests for valid requests, invalid inputs, and error responses."

38. "What should I mock in these tests and why? [paste test code and the code being tested]."

39. "Generate test data fixtures for these tests: [describe what the tests need]. Make the data realistic and cover edge cases."

40. "How do I test this asynchronous code? [paste code]. Show me the correct pattern for [testing framework]."

41. "Write a test plan for [describe feature]. What should be tested at unit, integration, and end-to-end levels?"

Learning and Explanation

42. "Explain [concept or technology] to me as if I'm an experienced developer but new to this specific area. Use concrete examples."

43. "What is the difference between [concept A] and [concept B]? When would you use each? Give examples in [language]."

44. "Walk me through how [framework or library] works under the hood. What are the key abstractions and how do they fit together?"

45. "I'm learning [technology]. What are the most important concepts to understand first, and what common mistakes do beginners make?"

46. "Explain this code to me: [paste code]. What does it do, how does it work, and are there any non-obvious aspects I should understand?"

47. "What are the best practices for [topic: error handling / logging / security / performance] in [language or framework]?"

Productivity and Workflow

48. "Write a [bash/Python/PowerShell] script that automates [describe repetitive task]. It should handle errors gracefully and log what it does."

49. "Create a [language] CLI tool that [describe purpose]. Include argument parsing, help text, and error handling."

50. "I need to migrate [describe existing code or system] to [new approach or technology]. What is the safest migration strategy and what are the key risks?"

Getting Better Results from These Prompts

A few practices that consistently improve AI output for developers:

Provide context about your stack. "In a Node.js Express application using TypeScript and Prisma" gives far better results than "in my app."

Specify constraints. If you need the solution to work with a particular Node version, avoid certain dependencies, or follow specific conventions, say so upfront.

Paste the actual code. Describing code in words is less effective than showing it. Paste the relevant function, class, or file.

Ask for explanations. "Explain why you made these choices" helps you evaluate the output and learn from it.

Iterate. First responses are rarely perfect. Follow up with "make it more defensive," "simplify the error handling," or "add logging" to refine the output.

Verify everything. AI-generated code can look correct and be wrong. Run it, test it, and understand it before committing.