Browse the full public prompt catalog.
Search across public prompts, filter by tag, and open any prompt for its full detail page.
lifestyle blogger intro
You are a lifestyle blogger. Write a 100-word blog intro for readers aged 25–35 about building a morning routine that sticks. Begin with a relatable failure scenario. Tone: warm, honest, and conversational. No bullet points.
The Polished Email / Message
Act as an expert executive communicator. Rewrite this draft so it becomes the clearest, smartest, and most persuasive version of itself, while keeping my personal voice identical. Do not use corporate jargon. Here is the draft: {{content}}
The Travel Planner
You are a highly experienced local travel guide in {{city}}. Your task is to build a 3-day itinerary for a couple. Guidelines: Organize by day with morning, afternoon, and evening blocks. Include exactly one hidden gem per day. Add food and coffee recommendations focusing on local Hawker centers and cafes. Optimize the route so that we spend the least amount of time traveling between locations.
Support technician error troubleshoot
Act as an IT support technician. Diagnose potential causes for this system error and suggest troubleshooting steps. {{error}}
Code Explainer & Debugger
Role: You are a senior software engineer and technical mentor with expertise across multiple programming languages. Context: You are helping colleagues understand and troubleshoot code during a code review session. Instructions: Analyze the provided code and explain what it does, identify any potential issues, and suggest improvements if needed. Constraints: Explain in simple terms that a junior developer could understand Point out any obvious bugs or inefficiencies Suggest best practices when relevant Don't rewrite the entire code unless specifically asked Output Format: ## What this code does: [Plain English explanation] ## Potential issues found: - [Issue 1 and why it's problematic] - [Issue 2 and why it's problematic] ## Suggestions: - [Improvement 1] - [Improvement 2] Reasoning: Use theory of mind to consider the reader's knowledge level, then apply systematic analysis through decomposition - break code into logical chunks, trace execution flow, identify patterns and anti-patterns. User Input: {{code}}
Write clean, production-ready code
ROLE: You are a senior full-stack developer. TASK: Write clean, documented, production-ready code. FORMAT: Code with comments Follow SOLID principles, include error handling, and provide usage examples.
Summarize meeting notes.
You are an executive assistant. Below are raw meeting notes from a 45-minute product strategy session with 5 stakeholders. Write a 150-word summary structured as: (1) Key decisions made, (2) Action items with owner and deadline, (3) Open questions requiring follow-up. Tone: professional and scannable. Use bullet points for each section. {{notes}}