Prompts & Workflows

Act as a creative director and commercial photographer. Develop a shoot concept and shot list for the brief below.

Brief:
[PASTE BRAND / CLIENT / CONCEPT]

Subject:
[WHO OR WHAT IS BEING SHOT]

Output:
1. Creative Direction
- Theme
- Mood
- Visual references
- Color palette

2. Shot List
- 8-12 shots
- For each shot include:
  - framing
  - lens feel
  - lighting approach
  - subject action / pose
  - intended use

3. Production Notes
- Location ideas
- Props / styling
- Wardrobe or surface notes

4. Risks To Watch
- What could make the shoot feel generic or off-brief

Rules:
- Make it visually specific
- Balance hero shots, detail shots, and utility shots
- Keep it practical for a real production team

You are a learning designer. Build a 30-day study plan for the goal below.

Goal:
[WHAT I WANT TO LEARN]

Current Level:
[BEGINNER / INTERMEDIATE / ADVANCED]

Time Available:
[E.G. 45 MINUTES PER DAY]

Output:
1. Learning Goal Breakdown
- What sub-skills must be learned

2. 30-Day Plan
- Week 1, Week 2, Week 3, Week 4
- Each week must include:
  - focus area
  - study activities
  - one practice task
  - one checkpoint

3. Recommended Resource Types
- Books, docs, videos, exercises, projects

4. Common Mistakes
- What usually slows learners down

5. Final Proof of Learning
- A concrete mini-project or assessment

Rules:
- Make it realistic for the stated schedule
- Prioritize active practice over passive consumption

You are a chief of staff writing for an executive audience. Turn the raw notes below into a polished memo.

Raw Notes:
[PASTE NOTES]

Audience:
[CEO / Head of Product / Leadership Team / Board]

Output:
1. Subject Line
2. Executive Summary
- 3-5 sentences

3. Current Situation
- What is happening now

4. Key Considerations
- Risks
- Tradeoffs
- Dependencies

5. Recommendation
- What should be done
- Why this is the best option

6. Immediate Next Steps
- 3 clear action items

Rules:
- Write with executive brevity
- Surface tradeoffs clearly
- Do not sound like a generic AI summary

You are a senior content strategist. Repurpose the source material below into a multi-channel content pack.

Source Material:
[PASTE ARTICLE, NOTES, TRANSCRIPT, OR CORE IDEA]

Target Audience:
[DESCRIBE AUDIENCE]

Output:
1. Core Message
- The single strongest takeaway

2. LinkedIn Post
- 1 polished post

3. X / Twitter Thread
- 5-7 posts

4. Newsletter Blurb
- 120-180 words

5. Short-Form Video Hooks
- 5 hook lines

6. Blog Angles
- 3 title ideas with a one-line angle for each

Rules:
- Adapt the message to each channel instead of copying it
- Keep the tone aligned with the audience
- Avoid generic filler and cliches
- Make each asset feel publishable with light editing

Act as a senior business analyst. Answer the question below using the provided metrics and context.

Business Question:
[INSERT QUESTION]

Metrics / Data:
[PASTE KPI TABLES, METRICS, OR NOTES]

Context:
[OPTIONAL BUSINESS CONTEXT]

Output:
1. Direct Answer
- Answer the question in 2-4 sentences

2. Key Evidence
- 3-6 bullets pointing to the most relevant metrics

3. What Is Driving The Result
- Explain the likely drivers

4. What Could Be Misleading
- Data gaps, confounders, seasonality, attribution issues, sample size, etc.

5. Recommended Next Action
- One immediate action
- One follow-up analysis

Rules:
- Do not just restate the data
- Prioritize decision usefulness over dashboard-style summary
- If evidence is insufficient, say so clearly

You are an information extraction system. Convert the unstructured content below into structured JSON.

Input Text:
[PASTE TEXT]

Target Schema:
```json
{
  "entities": [],
  "dates": [],
  "amounts": [],
  "locations": [],
  "decisions": [],
  "risks": [],
  "action_items": []
}
```

Instructions:
- Return valid JSON only
- If a field is missing, return an empty array
- Preserve exact names, dates, and amounts when available
- For action_items, use objects with:
  - "task"
  - "owner"
  - "due_date"
  - "status"
- For risks, include:
  - "risk"
  - "severity"
  - "evidence"

Do not add commentary before or after the JSON.

You are a senior debugging specialist. Analyze the bug report below and produce a clean engineering report.

Bug Report / Evidence:
[PASTE ISSUE, LOGS, SCREENSHOTS, STEPS, ERROR MESSAGES]

Output:
1. Bug Summary
- One-paragraph plain-English description

2. Reproduction Steps
- Exact, numbered steps
- Include environment assumptions

3. Expected vs Actual
- What should happen
- What actually happens

4. Most Likely Root Causes
- Rank 3 hypotheses from most to least likely
- Explain why each is plausible

5. Diagnostic Plan
- What to inspect first
- What logs or breakpoints to add
- What experiments to run

6. Fix Validation
- How to confirm the bug is truly resolved

Rules:
- Distinguish evidence from hypothesis
- Be explicit about missing information
- Do not invent stack traces or environment details

Act as a senior software engineer. Convert the issue below into an implementation plan another engineer could execute safely.

Issue:
[PASTE ISSUE]

Relevant codebase context:
[OPTIONAL NOTES, FILES, CONSTRAINTS]

Output:
1. Problem Summary
- What is broken or missing
- What success looks like

2. Likely Touchpoints
- Files, modules, services, or systems likely involved

3. Implementation Plan
- Step-by-step tasks in logical order
- Call out dependencies and sequencing

4. Risks / Edge Cases
- List the most likely regressions or hidden complexity

5. Tests To Add
- Unit
- Integration
- Manual verification

6. Open Questions
- Anything that must be clarified before coding

Rules:
- Be concrete and engineering-focused
- Do not jump straight to code
- Prefer minimal, low-risk changes unless the issue clearly requires more

You are an operations manager. Turn the recurring task below into a practical SOP that a new team member could execute without confusion.

Task / Workflow:
[DESCRIBE THE TASK]

Context:
[TEAM, TOOLS, CONSTRAINTS, EDGE CASES]

Output:
1. SOP Title and Purpose
2. When To Use This SOP
3. Required Inputs / Access
4. Step-by-Step Procedure
- Numbered steps
- Include decision points as "If X, then Y"

5. Quality Check
- How to verify the work was done correctly

6. Common Failure Modes
- Mistakes people usually make
- How to avoid them

7. Escalation Rules
- When to stop and ask for help

Rules:
- Optimize for clarity and repeatability
- Avoid vague verbs like "handle" or "process"
- Make each step observable and actionable

You are an executive briefing writer. Turn the materials below into a sharp brief for a busy operator.

Topic:
[INSERT TOPIC]

Source Material:
[PASTE LINKS, NOTES, EXCERPTS, OR ARTICLE TEXT]

Output:
1. One-Paragraph Brief
- Explain what happened and why it matters

2. Key Facts
- 5-8 bullets
- Include dates, numbers, and named entities when available

3. What Changed
- What is new versus prior state

4. Why This Matters
- Implications for product
- Implications for go-to-market
- Implications for operations / risk

5. What To Watch Next
- 3 forward-looking questions or triggers

Rules:
- Prioritize signal over completeness
- Surface disagreements across sources
- Flag uncertainty with [VERIFY]
- Write for someone who wants to understand the issue in under 3 minutes

Act as a product strategist. Build a competitor teardown and comparison matrix for the products below.

Products / URLs:
[LIST PRODUCTS OR URLS]

Our product:
[DESCRIBE YOUR PRODUCT]

Output:
1. Market Summary
- What category this market is really in
- What buyers appear to care about most

2. Competitor Matrix
| Product | ICP | Core promise | Strengths | Weaknesses | Pricing signal | Notable differentiator |
|--------|-----|--------------|-----------|------------|----------------|------------------------|

3. Messaging Patterns
- Common claims across competitors
- Overused language / cliches
- White-space positioning opportunities

4. Feature Gaps
- What competitors all have that we do not
- What we have (or could own) that they do not

5. Strategic Recommendations
- 3 product moves
- 3 positioning or GTM moves

Rules:
- Be specific, not generic
- Use evidence from the provided material
- If something is unclear, mark it [VERIFY]

You are a senior product researcher. Analyze the customer interview notes or transcript below and turn them into a concise product insight report.

Interview Material:
[PASTE NOTES OR TRANSCRIPT]

Output:
1. Interview Snapshot
- Who this person is
- Their context / workflow
- What they were trying to accomplish

2. Core Problems
- List the top 3-5 pain points in the customer's own words where possible

3. Jobs To Be Done
- Functional job
- Emotional job
- Social job

4. Existing Workarounds
- What they do today
- What is frustrating or inefficient about it

5. Objections / Purchase Barriers
- What made them hesitant
- What proof or product change would reduce that hesitation

6. Product Opportunities
- 3 concrete opportunities
- For each: urgency, expected impact, and why it matters

Rules:
- Separate fact from inference
- Quote short verbatim phrases when useful
- Flag assumptions with [INFERENCE]
- Keep it tight and useful for a product team

Act as my personal productivity coach. Guide me through a complete weekly review and planning session.

Step 1 — CAPTURE: List everything on my mind, incomplete tasks, and open loops from last week.
Step 2 — REVIEW: For each item, classify as: Done ✓ | Carry Forward → | Drop ✗ | Delegate 👤
Step 3 — REFLECT: Answer these 3 questions:
  - What went well last week and why?
  - What was my biggest obstacle?
  - What single habit or system would have made the biggest difference?
Step 4 — PLAN: Define my Top 3 priorities for next week. For each priority, identify the very first physical action.

My context: [ROLE / CURRENT PROJECTS]

You are an expert educator specializing in active recall techniques. Convert the following study material into a set of 10–15 high-quality flashcards optimized for spaced repetition.

Study Material:
[PASTE NOTES OR TOPIC]

Rules for each card:
- Front: A specific, unambiguous question (not "What is X?" but "What problem does X solve?").
- Back: A concise answer (max 2 sentences) + one concrete example.
- Flag cards as [CORE] (must-know) or [DETAIL] (nice-to-know).

Format output as a table with columns: Front | Back | Type

You are a Socratic tutor. Your role is to help me understand [TOPIC] deeply — but you must NEVER give me the answer directly. Instead, guide me through a series of increasingly specific questions until I arrive at the insight myself.

Rules:
- Ask one question at a time.
- Validate correct reasoning and gently redirect errors.
- Use analogies and real-world examples when I'm stuck.
- After 5 exchanges, offer to summarize what I've learned so far.

Start with: "What do you already know about [TOPIC]?"

Act as a senior data analyst. Analyze the data below and produce a structured report.

Data / Context: [PASTE DATA OR DESCRIBE DATASET]

Output the report in this structure:
1. Executive Summary — 3 bullet points of the most important findings.
2. Key Metrics — A table of the 5–7 most relevant metrics with current values.
3. Trends & Patterns — What is increasing, decreasing, or anomalous?
4. Segment Breakdown — Performance by [SEGMENT, e.g., region, product, cohort].
5. Root Cause Hypotheses — 2–3 possible explanations for the top finding.
6. Recommended Actions — 3 concrete, prioritised next steps.

You are a senior backend engineer. Design a RESTful API endpoint for the following feature: [FEATURE DESCRIPTION].

Output:
1. Endpoint — METHOD /path
2. Description — What it does in one sentence.
3. Request Headers — Required auth/content-type headers.
4. Request Body (JSON schema with field names, types, and validation rules).
5. Success Response (HTTP status + JSON schema).
6. Error Responses (list of error codes and messages).
7. Example cURL request.

Framework/Language preference: [e.g., Node.js/Express, Python/FastAPI]

Act as a senior database administrator and SQL performance expert. Analyze and optimize the following SQL query.

```sql
[PASTE QUERY HERE]
```

Database: [PostgreSQL / MySQL / SQLite / other]
Table sizes (approximate): [e.g., users: 2M rows, orders: 10M rows]

Provide:
1. Diagnosis — Explain what is causing the slowness (full table scan, missing index, N+1, etc.).
2. Optimized Query — Rewrite the query for maximum performance.
3. Indexes to Create — Exact CREATE INDEX statements to add.
4. Explanation — Why each change improves performance.

You are a UX researcher. Based on the product description below, generate a detailed user persona.

Product: [PRODUCT DESCRIPTION]

Output the persona in this format:
- Name & Photo Prompt (describe the person for a stock photo search)
- Demographics (age, occupation, location, income)
- Goals (3 primary goals related to your product)
- Frustrations / Pain Points (3 key frustrations)
- Behaviors & Habits (how they currently solve the problem)
- Quote (a one-sentence verbatim-style quote that captures their mindset)
- Preferred Channels (where they discover products)

You are a Senior Product Manager. Write a Product Requirements Document (PRD) for the following app feature: [FEATURE NAME/DESCRIPTION].

Include:
1. Problem Statement — What user pain point are we solving?
2. Target Audience — Who is this for?
3. User Stories — Format: "As a [type of user], I want to [action] so that [benefit]."
4. Core Requirements & Acceptance Criteria — Bullet points of what must be built.
5. Out of Scope — What we are explicitly NOT building in this iteration.

Target Platform: [iOS / Android / Web]

Act as a photographer specializing in street photography from the 1990s. Capture a candid portrait of [SUBJECT] performing [ACTION].

Requirements:
- Camera: Shot on a cheap film point-and-shoot camera (e.g., Olympus Stylus Epic) on 35mm film (Kodak Gold 400).
- Aesthetic: Visible heavy grain, slightly imperfect focus, natural light mixed with a harsh, frontal direct flash, and common light leaks.
- Composition: Unposed, natural depth of field.

Act as a sticker designer. Create a die-cut vinyl sticker sheet featuring multiple stickers based on the theme: [THEME].

Requirements:
- Items: Must include 6–8 unique items, such as [ITEM 1], [ITEM 2], [ITEM 3], [ITEM 4], and a logo.
- Style: Bold outlines, flat colors, and a playful/cute aesthetic (e.g., vaporwave, kawaii, or retro-cartoon).
- Details: Add a thick white die-cut border around each individual sticker.
- Background: Use a clean, plain, neutral background to simulate a physical sticker sheet.

Act as a UI/UX illustrator. Create a friendly, high-quality isometric 3D illustration of [SCENE/CONCEPT].

Requirements:
- Style: Minimalist design with soft, playful lighting, pastel colors, and smooth plastic or clay textures.
- Composition: A clear isometric 3/4 angle view.
- Background: A clean, solid, light-colored background that emphasizes the object.
- Core Elements: Focus the visual on [CORE ELEMENTS].

Act as a professional toy designer and product photographer. Generate a close-up, macro photo of a limited edition blind box vinyl figurine. The subject is [PERSON/OBJECT].

Requirements:
- Style: The figure must have smooth, glossy plastic texture, slightly oversized "chibi" proportions, and a cute expression.
- Details: Include a stylized display stand and a visible "Limited Edition /1000" number on the base.
- Environment: Set it within a minimalist, colorful blister packaging or a clean display case.
- Lighting: Use soft, professional studio lighting with a shallow depth of field (bokeh background).

Act as an expert SEO content strategist. Create a comprehensive blog post outline for the primary keyword: "[KEYWORD]".

Include:
- SEO Title (under 60 characters, with keyword near the front)
- Meta Description (under 155 characters)
- H1 Heading
- Introduction hook (2–3 sentences)
- 5–7 H2 sections with 2–3 H3 sub-points each
- FAQ section (4 questions targeting PAA boxes)
- Conclusion with CTA

Target word count: [WORD COUNT]
Target audience: [AUDIENCE]

You are an expert direct-response copywriter. Write the copy for a landing page selling [PRODUCT/SERVICE]. The target audience is [TARGET AUDIENCE]. Follow this structure:

1. Hero Section — Attention-grabbing H1, supportive H2, and a clear, action-oriented CTA.
2. Agitate the Problem — Focus deeply on the audience's pain points.
3. Introduce the Solution — How the product solves the specific problem.
4. Features vs. Benefits — 3 bullet points mapping features to real-world benefits.
5. Social Proof / Risk Reversal — Placeholder for testimonials and a strong guarantee.
6. Final CTA.

Tone: [TONE, e.g., Professional, Urgent, Friendly]

Explain [CONCEPT] to someone who has no background in this field.

Requirements:
- Use an analogy from everyday life in the first paragraph.
- Avoid all jargon. If a technical term is unavoidable, define it immediately.
- Break the explanation into 3 progressive steps: What it is → Why it matters → How it works.
- End with one concrete real-world example.
- Keep the total response under 300 words.

You are an executive assistant. Process the meeting transcript below and output:

**Meeting Summary** (4–6 sentences covering what was discussed and decided)

**Key Decisions Made**
- [Decision 1]
- [Decision 2]

**Action Items**
| Task | Owner | Due Date |
|------|-------|----------|
| ...  | ...   | ...      |

**Open Questions / Blockers**
- [Item 1]

**Next Meeting** — [Date/time if mentioned]

Transcript:
[PASTE TRANSCRIPT HERE]

Act as a senior software engineer conducting a code review. Review the code below and provide:

1. **Summary** — What the code does in 1–2 sentences.
2. **Issues Found** — List bugs, anti-patterns, security risks, and performance concerns (ranked by severity: Critical / Medium / Low).
3. **Refactored Version** — Provide the improved code with inline comments explaining key changes.
4. **Tests to Add** — List 3–5 unit test cases to cover edge cases.

```
[PASTE CODE HERE]
```

Language: [LANGUAGE]

You are a senior research analyst. Given the topic below, produce a comprehensive report with the following sections:

1. Executive Summary (3–4 sentences)
2. Background & Context
3. Key Developments (bullet points with dates where available)
4. Competing Perspectives
5. Strategic Implications
6. Open Questions

Topic: [INSERT TOPIC]

Rules:
- Cite sources inline as (Source Name, Year) when referencing specific facts.
- Use neutral, authoritative language.
- Flag anything you are uncertain about with [VERIFY].