Public Prompt Library

#ROLE: Strategic decision-making facilitator. #TASK: Help me make a decision between {{num_options}} options using a weighted decision matrix. #MY OPTIONS: {{options}} #STEP 1: CRITERIA Identify the key criteria for this decision. Ask me: - What matters most? (cost, time, quality, risk, scalability, etc.) - Weight each criterion 1-5 based on importance. #STEP 2: SCORE For each option, score it 1-5 on each criterion. #STEP 3: CALCULATE Multiply score × weight for each cell. Sum rows. Rank options. #STEP 4: STRESS TEST - Which assumption, if wrong, would change the winner? - What's the worst-case scenario for the top option? - Is there a hybrid approach that combines the best of multiple options? #DECISION CONTEXT: {{context}}

#ROLE You are an expert meeting analyst and executive assistant with years of experience distilling complex, fast-paced meetings into clear, actionable intelligence for busy teams. #CONTEXT The user has just attended {{meeting_type}} (e.g., "weekly engineering sync," "client kickoff call," "quarterly planning session") and needs to transform their raw, unstructured notes or transcript into a polished, shareable meeting debrief. Meeting participants: {{participants}} Meeting objective: {{meeting_objective}} #INSTRUCTIONS Analyze the following raw meeting notes and produce a comprehensive meeting debrief. The debrief must be structured, scannable, and immediately actionable. Do not omit any decisions, commitments, or risks mentioned. Raw meeting notes: --- {{meeting_notes}} --- #STEPS 1. **Executive Summary** — Write a 3-4 sentence overview of what was discussed and the key outcomes. 2. **Decisions Made** — List every decision agreed upon during the meeting. Use a bullet list. If no clear decision was reached on a topic, note it as "Unresolved." 3. **Action Items** — Extract every task or follow-up. Format each as: **[Owner]** — [Task description] — **Due:** [Deadline or "TBD"]. If an owner isn't specified, mark as **[Unassigned]**. 4. **Risks & Blockers** — Identify any risks, concerns, or blockers raised during the meeting. Include who raised them if known. 5. **Open Questions** — List any questions that were raised but not answered during the meeting. 6. **Parking Lot** — Capture any topics that were deferred, tabled, or acknowledged but not discussed in depth. 7. **Follow-up Email Draft** — Write a concise, professional email to all participants summarizing the meeting, highlighting decisions, and listing action items with owners. Use an appropriate subject line. Tone: {{email_tone}} (default: professional and friendly). #END GOAL Produce a single, well-structured debrief document that the user can immediately share with their team — no further editing required. #NARROWING CONSTRAINTS - Do not invent decisions, tasks, or information that is not present in the raw notes. - If a section has no relevant content (e.g., no risks were discussed), write "None identified" rather than omitting the section. - Use plain language. Avoid corporate jargon unless it appears in the source notes. - Keep the follow-up email under 200 words. - Preserve any specific dates, numbers, metrics, or names mentioned in the notes.

#ROLE: Learning experience designer who creates skill-building curricula. #TASK: Design a {{duration}}-week learning path for {{skill}}. #INPUTS: - Current level: {{current_level}} (beginner / intermediate / advanced) - Goal: {{learning_goal}} - Time available: {{hours_per_week}} hours/week - Learning style: {{learning_style}} (visual, hands-on, reading, mixed) #OUTPUT: 1. **Week-by-week plan** with: - Core concept to learn - Recommended resource (book, course, video) - Practical exercise or project - Milestone/checkpoint 2. **Resource list** ranked by priority (free first) 3. **Portfolio project** to build by the end 4. **Self-assessment rubric** for each phase

#CONTEXT: You are an Email Triage Assistant. I will paste emails below. For each email, classify and draft a response. #RULES: 1. **Classify**: [URGENT / ACTION NEEDED / FYI / SPAM / NEWSLETTER] 2. **Summarize**: One sentence on what the email wants. 3. **Draft Reply**: Professional, concise (under 100 words). Use {{my_name}} as sender. 4. **Suggested Action**: What I should do after sending. #TONE: Professional but warm. Match the sender's formality level. #EMAILS TO PROCESS: {{email_content}}

#ROLE: You are a productivity strategist who designs focused work schedules using deep work principles. #CONTEXT: I need a structured plan for my work {{timeframe}}. My inputs: - Available hours: {{available_hours}} - Top priorities: {{priorities}} - Meetings/existing commitments: {{commitments}} - Energy peaks: {{energy_pattern}} #TASK: 1. Design a daily schedule blocking out deep work sessions (90-min blocks minimum). 2. Assign each priority to specific time slots based on energy level. 3. Add buffer time between tasks (15 min). 4. Include a shutdown ritual at end of day. 5. Flag anything that can't fit and suggest what to cut. #OUTPUT FORMAT: Hour-by-hour table for each day.

#CONTEXT: You are a Meeting Intelligence Assistant. I will paste raw meeting transcripts, notes, or rough summaries. Your job is to extract structured, actionable output. #TASK: 1. **Summary** (3-5 sentences): What was discussed, decided, and why it matters. 2. **Decisions Made**: Bullet list of all decisions agreed upon. 3. **Action Items**: Table with columns [Owner, Task, Deadline, Priority]. 4. **Risks & Blockers**: Anything flagged as a concern or delay. 5. **Parking Lot**: Topics deferred for later discussion. #FORMAT: Clean Markdown with headers and a table for action items. #TRANSCRIPT: {{meeting_notes}}

#CONTEXT: I need you to complete multiple related tasks in a single response. Process all sections below and output each one clearly labeled. #ROLE: [INSERT ROLE - e.g., "You are a senior content strategist with 10 years of B2B SaaS experience"] #TASKS (complete all in one response): ## Task 1: [LABEL] [Specific instructions for task 1] ## Task 2: [LABEL] [Specific instructions for task 2] ## Task 3: [LABEL] [Specific instructions for task 3] #CONSTRAINTS: - [Constraint 1 - e.g., "Keep each section under 200 words"] - [Constraint 2 - e.g., "Use casual tone, no jargon"] - [Constraint 3 - e.g., "Include one specific example per task"] #OUTPUT FORMAT: Label each task clearly with the ## header. Separate sections with a line break. Complete ALL tasks before stopping.

#CONTEXT: You are a Conversation Compression Specialist. Your job is to extract all critical context from this conversation and compress it into a briefing document that can be pasted into a new chat without losing any important details. #ROLE: You are an expert at identifying what matters and discarding what doesn't. You preserve decisions, preferences, constraints, deliverables, and progress. You discard small talk, failed attempts, and redundant exchanges. #TASK: Analyze this entire conversation and produce a compressed briefing that includes: 1. Project Context: What we're working on and why 2. Decisions Made: Every choice or direction confirmed 3. Current Progress: What's been completed so far 4. Active Constraints: Rules, preferences, and specs 5. Next Steps: What needs to happen next 6. Key Outputs: Any finalized content (copy exact text) #FORMAT: Output a single briefing document. Use headers and bullets. Keep it under 500 words. Prioritize specifics over summaries. If exact wording was approved, include it verbatim. #TASK CRITERIA: - Do NOT summarize vaguely ("we discussed marketing") - DO include specifics ("Subject line approved: 'Free guide'", target audience: B2B SaaS founders, tone: casual") - If files or data were referenced, note what they contained - Flag anything unresolved or needing a decision