Skip to main content
NEW · APP STORE Now on iOS · macOS · iPad Android & Windows soon GET IT
Prompts Polar.sh Payment Prompts for Notion Template Sales

model prompt_engineering template risk: medium

Polar.sh Payment Prompts for Notion Template Sales

Instructs the model to act as an elite prompt engineering expert and create three versions of optimized prompts (short, detailed structured, and chain-of-thought heavy) for answeri…

  • Policy sensitive
  • Human review

PROMPT 

You are an elite prompt engineering expert. Your task is to create the perfect, highly optimized prompt for my exact need.

My goal: ${${describe_what_you_want_in_detail:I want to sell notion template on my personal website. And I heard of polar.sh where I can integrate my payment gateway. I want you to tell me the following: 1. will I need a paid domain to take real payments? 2. Do i need to verify my website with indian income tax to take international payments? 3. Can I run this as a freelance business?}}

Requirements / style:
• Use chain-of-thought (let it think step by step)
• Include 2-3 strong examples (few-shot)
• Use role-playing (give it a very specific expert persona)
• Break complex tasks into subtasks / sub-prompts / chain of prompts
• Add output format instructions (JSON, markdown table, etc.)
• Use delimiters, XML tags, or clear sections
• Maximize clarity, reduce hallucinations, increase reasoning depth

Create 3 versions:
1. Short & efficient version
2. Very detailed & structured version (my favorite style)
3. Chain-of-thought heavy version with sub-steps

Now create the best possible prompt(s) for me:

INPUTS

describe_what_you_want_in_detail REQUIRED

Detailed description of the user's goal and specific questions to address

e.g. I want to sell notion template on my personal website. And I heard of polar.sh where I can integrate my payment gateway. I want you to tell me the following: 1. will I need a paid domain to take real payments? 2. Do i need to verify my website with indian income tax to take international payments? 3. Can I run this as a freelance business?

REQUIRED CONTEXT

  • user goal description with specific questions

OPTIONAL CONTEXT

  • prompt engineering requirements and style preferences

ROLES & RULES

Role assignments

  • You are an elite prompt engineering expert.
  1. Use chain-of-thought (let it think step by step)
  2. Include 2-3 strong examples (few-shot)
  3. Use role-playing (give it a very specific expert persona)
  4. Break complex tasks into subtasks / sub-prompts / chain of prompts
  5. Add output format instructions (JSON, markdown table, etc.)
  6. Use delimiters, XML tags, or clear sections
  7. Maximize clarity, reduce hallucinations, increase reasoning depth

EXPECTED OUTPUT

Format
markdown
Schema
numbered_sections · 1. Short & efficient version, 2. Very detailed & structured version (my favorite style), 3. Chain-of-thought heavy version with sub-steps
Constraints
  • 3 distinct versions
  • version 1: short and efficient
  • version 2: very detailed and structured
  • version 3: chain-of-thought heavy with sub-steps
  • include chain-of-thought, 2-3 few-shot examples, role-playing, subtasks, output format instructions, delimiters
  • maximize clarity, reduce hallucinations

SUCCESS CRITERIA

  • Create 3 versions of highly optimized prompts
  • Incorporate all specified requirements and style guidelines
  • Address the exact user goal of answering 3 specific questions about polar.sh, payments, taxes, and freelance business

FAILURE MODES

  • May produce prompts that encourage hallucinations on legal/tax advice
  • Versions may lack sufficient differentiation
  • Prompts may not deeply reason about Indian regulations or polar.sh specifics

CAVEATS

Ambiguities
  • Nested placeholder syntax '${${describe_what_you_want_in_detail:...}}' is confusing and unclear how it should be used or replaced.
  • 'my favorite style' for version 2 is subjective and undefined.

QUALITY

OVERALL
0.80
CLARITY
0.75
SPECIFICITY
0.90
REUSABILITY
0.65
COMPLETENESS
0.85

IMPROVEMENT SUGGESTIONS

  • Simplify the goal placeholder to a clean variable like '${USER_GOAL}' for better templating.
  • Explicitly define 'detailed & structured' style with examples or additional traits.
  • Add output format for the 3 versions, e.g., use <version1>, <version2>, <version3> XML tags to separate them.
  • Specify criteria for 'strong examples' in few-shot to guide generation.

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR MODEL