194 prompts
Explain [math concept, e.g. negative numbers / derivatives / probability] using a visual description, a real-life analogy, and a step-by-step example. Then give 3 practice problems with answers, getting gradually harder. Level: [grade].
Uses diagrams and analogies to make a math idea click.
Act as an algebra tutor. Here's my problem: [equation]. Don't solve it for me. Ask what the first step should be, give hints when I'm stuck, check each step I write, and explain mistakes. When we finish, give me a similar problem.
Guides students through solving equations themselves.
Help me prove: [statement]. Given: [givens]. First explain the strategy in plain words, then guide me to build a two-column proof (statement | reason) one line at a time, letting me suggest each step.
Explain the Big O time and space complexity of this code step by step, as if teaching a junior developer. Point out the most expensive part and how input size affects it. Code: [paste code]
Explain this stack trace in plain English. Identify where the error actually originates in my code (not library code), the likely cause, and how to fix it. Ask for the relevant code if needed. Stack trace: [paste]
Set up error monitoring for a [stack] app in production. Explain what to capture (errors, context, releases), how to avoid logging sensitive data, alerting rules, and show the integration code for [tool or a generic logger].
Catches and reports production errors before users complain.
This code is too clever and hard to read. Rewrite it for clarity: descriptive names, small functions, comments only where needed, and the same behaviour. Explain what the original was doing. Code: [paste code]
My [framework] app has these needs: [describe shared state, server data, forms]. Recommend a state management approach (e.g. built-in state, Context, Zustand, Redux Toolkit, React Query), explain why, and show the setup with one example feature.
Chooses and sets up state management for a frontend app.
My page breaks on mobile: [describe problem, e.g. horizontal scroll, overlapping elements]. Here's the HTML/CSS: [paste]. Find the cause, fix it with mobile-first CSS, and explain how to test on different screen sizes.
Optimise this Dockerfile for size, build speed and security. Use multi-stage builds, a minimal base image, layer caching, a non-root user and .dockerignore suggestions. Explain each change. Dockerfile: [paste]
Makes Docker images smaller, faster and more secure.
Explain [data structure, e.g. a hash map / heap / trie] for a [level] developer. Include a text diagram, how operations work with time complexity, a clean implementation in [language], and when to use it in real projects.
Explains a data structure with visuals and an implementation.
Explain this pull request diff for a reviewer. Summarise what changed and why (as far as you can tell), list risky areas, possible bugs, missing tests, and questions to ask the author. Diff: [paste diff]
Summarises what a PR changes and what to watch for.