Explore Prompts
Discover production-grade prompts crafted by the community. Search, filter, fork, and make them your own.
by Marcus Dev
I'll describe a feature or resource. Design a RESTful API for it: 1. **Endpoints** — List each endpoint with method, path, and purpose. 2. **Request/Response** — Show example JSON request bodies and response payloads with proper status codes. 3. **Validation** — Describe input validation rules for each field. 4. **Error Handling** — Define error response format and common error scenarios. 5. **Auth** — Specify which endpoints need authentication and what permissions are required. Use consistent naming conventions (plural nouns, kebab-case). If the feature is complex, suggest pagination, filtering, and sorting patterns.
by Sarah Kim
I'll paste an error message or stack trace. Help me debug it: 1. **Identify the error type** — What kind of error is this? (syntax, runtime, type, network, etc.) 2. **Root cause** — Explain what's actually going wrong and why. 3. **Fix** — Provide the corrected code with an explanation of the change. 4. **Prevention** — Suggest how to avoid this error in the future (linting rules, type guards, error boundaries, etc.) If the error is ambiguous without more context, ask me for the relevant code surrounding the error. Always explain the fix in plain English before showing code.
by Alex Chen
I'll describe the changes I made. Write a conventional commit message following this format: ``` <type>(<scope>): <short summary> <body — what and why, not how> <footer — breaking changes, issue refs> ``` Types: feat, fix, docs, style, refactor, perf, test, build, ci, chore - Summary: imperative mood, lowercase, no period, max 50 chars - Body: wrap at 72 chars, explain motivation and contrast with previous behavior - Footer: reference issues as "Closes #123" or "BREAKING CHANGE: ..." If my description is vague, ask what the motivation behind the change was. Suggest the most appropriate type and scope based on what I describe.
by Marcus Dev
You are a SQL expert. I will describe the data I need in plain English, and you will: 1. Write an optimized SQL query (PostgreSQL dialect by default, unless I specify otherwise). 2. Add inline comments explaining each clause. 3. If the query involves joins, briefly explain the relationship between tables. 4. Suggest an appropriate index if the query would benefit from one. If my description is ambiguous, ask a clarifying question before writing the query. Always prefer CTEs over nested subqueries for readability.
by Sarah Kim
Generate a production-ready React component based on my description. Requirements: - Use TypeScript with proper type definitions - Use functional components with hooks - Follow the component structure: types → component → exports - Include sensible default props where appropriate - Use semantic HTML elements - Add aria attributes for accessibility - Keep styling framework-agnostic (use className props) unless I specify otherwise If the component needs state management, prefer useState/useReducer for local state. For complex components, break them into smaller sub-components in the same file. Respond with just the code and a brief usage example.
by Alex Chen
You are an expert code reviewer. When I share code with you, analyze it for: 1. **Bugs & Logic Errors** — Identify potential runtime errors, off-by-one mistakes, null reference issues, and incorrect logic. 2. **Performance** — Flag unnecessary re-renders, O(n²) loops that could be optimized, memory leaks, and redundant computations. 3. **Security** — Check for injection vulnerabilities, improper input validation, exposed secrets, and unsafe data handling. 4. **Readability** — Suggest better variable names, function decomposition, and clearer control flow. 5. **Best Practices** — Recommend idiomatic patterns for the language/framework being used. Format your review as a numbered list of findings, each with a severity tag: Critical, Warning, Suggestion. End with a brief summary and an overall quality score out of 10.
by Joshua Chuah
Review the following text to correct grammar, clarity, logic, and sentence structure. Rewrite it to be concise, easy to understand, and professionally polished while keeping the original meaning. Text: [paste text].
by Joshua Chuah
Edit this text so it sounds fluent and natural, as if written by an expert. Correct grammar, sentences, flow, structure, and tone. Make it easy to read and professional. Text: [paste text].
by Joshua Chuah
Correct all grammar issues, errors, and awkward phrasing in this text: [paste text]. Then rewrite it in a clean, professional, and confident tone without changing my message.
by Joshua Chuah
Act as a professional editor and rewrite the following text to correct grammar, errors, punctuation, and clarity. Keep my original meaning but dramatically improve the structure and readability. Here is the text: [paste text].