AI Prompts Library

Help me build a topic cluster around the pillar topic: "[PILLAR TOPIC]".

Produce:
1. The pillar page outline (definitive, comprehensive)
2. 8-12 cluster posts that link to and from the pillar - each one drilling into a specific subtopic
3. The internal linking structure (which posts link to which)
4. Suggested URL structure (slug pattern)
5. Priority order for publishing (highest-impact first)

For each cluster post, give: title, target keyword, search intent, 1-sentence summary.

Focus on posts that can rank individually AND build authority for the pillar.

I'm pricing [PRODUCT/SERVICE]. Help me think through it.

Context:
- Cost to deliver: [COST]
- Closest competitor's price: [COMPETITOR PRICE]
- Target customer: [PERSONA + PAIN]
- Market position desired: [PREMIUM / VALUE / DISRUPTIVE]

Provide:
1. Three pricing approaches (cost-plus, value-based, competitive) with pros/cons for my situation
2. A recommended price point with reasoning
3. Recommended pricing structure (one-time / subscription / tiered / usage-based)
4. Three psychological pricing techniques relevant here (anchoring, decoy, charm pricing, etc.)
5. The biggest pricing risk and how to test cheaply before committing

Be direct, not corporate. I want a decision, not a menu.

Generate a 30-minute customer discovery interview script for a [PRODUCT TYPE] targeting [PERSONA].

The interview should follow Mom Test principles - past behavior over future hypotheticals, specifics over generalities, learn before pitch.

Include:
1. 2 warm-up questions to build rapport
2. 6-8 problem-discovery questions (about their existing workflow and pain)
3. 3-4 questions to validate problem severity
4. 2 questions to understand current alternatives
5. 1-2 questions to gauge willingness to pay (without leading)
6. A closing that doesn't pitch the product

For each question, briefly explain what insight you're trying to extract.

Write a cold email to [PROSPECT - title + company].

My product: [WHAT IT DOES IN 1 SENTENCE]
Potential value to them: [SPECIFIC PAIN IT SOLVES]
Proof I have: [CASE STUDY / STAT / DEMO]
Personalization angle: [SOMETHING I LEARNED ABOUT THEM]

Constraints:
- Under 90 words total
- Subject line under 6 words
- Lead with personalization, not the product
- Specific ask (15-min call), not vague ("would love to chat")
- No buzzwords, no "hope this finds you well", no "quick question"
- Sounds like a human, not a marketer

Produce 3 variants with different angles.

Below is my pitch deck content. Tell me what's weak.

[PASTE DECK NOTES OR SECTION-BY-SECTION SUMMARY]

Review as a skeptical Series A investor. For each section, answer:
1. Is the claim believable? Any unsupported assertions?
2. Is the math defensible? Any obvious holes?
3. Is this actually distinct, or am I describing a wishful-thinking version of myself?
4. Where would a thorough investor's first follow-up question land?

Then give me the 3 most damaging weaknesses overall and how to fix each.

Be blunt. Diplomacy is wasting my time.

Build a competitive analysis matrix for [PRODUCT CATEGORY].

My product: [BRIEF DESCRIPTION]
Direct competitors: [LIST 3-5]

Produce:
1. Feature comparison matrix (what do they have, what don't they have)
2. Pricing comparison
3. Target segment for each (where they win, where they lose)
4. Public reviews / known complaints (cite if you have specifics)
5. The strategic gap - where competitors are uniformly weak that my product could exploit
6. The strategic risk - where competitors are uniformly strong that I cannot compete on directly

Finish with a 2-sentence recommendation: where I should position vs. where I should not.

Write a press release announcing [ANNOUNCEMENT].

Key facts: [WHAT, WHEN, WHO, WHY IT MATTERS]
Spokesperson quote attribution: [NAME + TITLE]
Target media: [BUSINESS / TECH / VERTICAL TRADE]

Follow standard press release format:
- Headline (clear, factual, no clickbait)
- Subhead (one sentence amplifying)
- Dateline
- Lead paragraph answering 5W's
- Quote from spokesperson with substance (not corporate fluff)
- Background context (one paragraph)
- About paragraph (one paragraph)
- Media contact info

Keep total under 400 words. Avoid superlatives unless they're true and provable.

Generate quarterly OKRs for [TEAM / DEPARTMENT].

Company context: [WHAT THE COMPANY DOES]
Team mission: [WHAT THIS TEAM IS FOR]
Quarter focus: [STRATEGIC PRIORITY]

Produce 2-3 Objectives, each with 3-4 Key Results.

Objectives must be:
- Aspirational and qualitative
- Tied to the strategic priority
- Memorable in one sentence

Key Results must be:
- Numeric and binary-measurable
- Outcomes, not activities (no "ship feature X")
- A stretch - uncomfortable but plausibly achievable
- Time-bound to the quarter

Flag any KR that is actually a project disguised as an outcome - those need rewriting.

Write a job description for [ROLE TITLE].

Company: [BRIEF COMPANY DESCRIPTION]
Team: [TEAM CONTEXT]
Level: [JUNIOR / MID / SENIOR / STAFF / DIRECTOR]
Must-have skills: [LIST]
Nice-to-have: [LIST]
What success looks like in 6 months: [DESCRIBE]

Write:
1. A role title (avoid inflated language)
2. A 2-paragraph 'About the role' that sells the actual work, not the company
3. Outcomes-based responsibilities (not activity lists)
4. Honest must-haves (the things that will actually trigger rejection)
5. Honest nice-to-haves
6. Compensation range (specific, not 'competitive')
7. What working here is actually like (the truth, not the brochure)

Avoid "rockstar", "ninja", "family", "fast-paced", "work hard play hard" - they tell candidates we're amateurs.

Help me diagnose churn for [PRODUCT].

Context:
- Current churn rate: [%]
- Industry benchmark: [%]
- Top 5 reasons users churn (per exit surveys / cancellation flow): [LIST]
- Lifecycle stage where churn peaks: [ONBOARDING / 30-90 DAYS / 6+ MONTHS]
- Pricing tier with worst churn: [TIER]

Produce:
1. Top 3 likely root causes, ranked by evidence strength
2. For each, the cheapest experiment to validate
3. Ranked list of interventions (highest impact, lowest effort first)
4. Metrics to track post-intervention to know if it worked
5. A reasonable expected churn improvement if interventions land

Don't suggest "build a customer success team" unless I asked for capital-intensive options.

Help me run a 90-minute quarterly strategy review.

Context:
- Last quarter's goals: [LIST]
- What landed: [LIST]
- What slipped: [LIST]
- Major surprises: [LIST]
- Current strategic priorities for next quarter: [LIST]

Produce:
1. Agenda with timed sections (90 min total)
2. 5-7 hard questions to ask the team for each section
3. The single most important decision the team should walk out having made
4. A pre-read document the team should review beforehand (3-paragraph max)
5. Post-meeting follow-up template

The goal is honesty and decisions, not theater.

You are Claude Code, an agentic coding assistant running inside the user's terminal. You have full access to the filesystem, can execute shell commands, search codebases, and edit files. Your goal is to help the user accomplish software engineering tasks efficiently and correctly.

**Core Principles:**
1. **Understand before acting**: Always read existing code, configurations, and project structure before making changes. Use grep and find to locate relevant files.
2. **Minimal, targeted changes**: Make the smallest change that correctly solves the problem. Do not refactor unrelated code unless asked.
3. **Preserve conventions**: Match the existing code style, naming conventions, import patterns, and project structure.
4. **Verify your work**: After making changes, run the project's test suite, linter, or build command to confirm nothing is broken.
5. **Explain your reasoning**: Before making edits, briefly explain what you found and what you plan to do. After edits, summarize what changed.

**Workflow for every task:**
- Step 1: Clarify the request if ambiguous. Ask one round of questions maximum.
- Step 2: Search the codebase to understand the relevant code, dependencies, and patterns.
- Step 3: Plan your changes and state them clearly.
- Step 4: Implement the changes using precise file edits.
- Step 5: Run tests or build commands to verify correctness.
- Step 6: Provide a concise summary of what was done.

**Rules:**
- Never create new files unless absolutely necessary. Prefer editing existing files.
- Never generate placeholder or TODO code. Every line you write must be complete and functional.
- When fixing bugs, identify the root cause first. Do not apply band-aid fixes.
- For new features, check if similar patterns exist in the codebase and follow them.
- Always handle errors gracefully. Never swallow exceptions silently.
- If you are unsure about something, say so rather than guessing.

**Tool Usage:**
- Use `grep` / `ripgrep` to search for symbols, patterns, and references across the codebase.
- Use `find` / `glob` to locate files by name or extension.
- Read files before editing them to understand the full context.
- Run shell commands for building, testing, and verifying changes.
- Use `git diff` and `git status` to review changes before committing.