Skip to content
PromptPilot AI

The power of a prompt

The same idea, written two ways. The PromptPilot prompt below is generated live by our builder from the same idea, so it is exactly what you would get.

Outputs marked “Example output” are written by us to show the kind of result to expect. They are not real AI responses, and we show no AI images we did not generate.

Cover letter

Weak prompt

write cover letter

PromptPilot prompt

## Role
You are a recruiter turned career writer who has screened thousands of applications and knows what makes a hiring manager keep reading.

## Task
Write a cover letter for a junior data analyst job at a Bengaluru fintech startup.
Success looks like: The letter connects my 2–3 most relevant achievements to the job's top requirements in under 300 words, and sounds like a person.

## If details are missing
I haven't told you these yet, so assume:
- Job description: I'll paste it; until then, use [requirement] placeholders
- Your relevant experience: use [achievement + result] placeholders; never invent
- Why this company: use a [specific reason] placeholder
State these assumptions in one line at the top of your answer. If one would change the answer a lot, ask me about it first.

## Steps
1. Extract the top 3 requirements from the job description
2. Match each to one of my achievements (or flag a gap)
3. Write an opening that names the role and a specific reason for this company
4. Write 2 short proof paragraphs: requirement → what I did → result
5. Close with a confident, specific next step

## Constraints
- Under 300 words
- No "I am writing to express my interest" or "I believe I would be a great fit"
- Never invent experience, employers or metrics
- No filler: skip intros, restating my request and closing summaries
- Don't invent facts, statistics, quotes, sources or details about me; flag anything I should verify

## Output format
- **Requirement match** table: requirement | my evidence | gap?
- **Cover letter**
- **3 questions** whose answers would make it stronger

## Before you answer, check
- Each paragraph proves a requirement
- Under 300 words
- Nothing invented

Example output

Dear Hiring Manager,
I'm applying for the Junior Data Analyst role. In my final-year project I cleaned and analysed sales data in SQL and Python and presented the findings as a dashboard…
Try this prompt

Shop Instagram caption

Weak prompt

caption for my shop

PromptPilot prompt

## Role
You are an Indian social media strategist who plans festive content for creators and small brands on Instagram, Facebook and LinkedIn.

## Context
Festival: Diwali (also called Deepavali, Deepawali, Lakshmi Puja)
Date (India): 26–31 Oct 2027, main day Fri, 29 Oct 2027
Where it's celebrated: Pan-India, Diaspora
Account / brand: saree shop
Platform: Instagram
Language: Hinglish
Location: Lucknow

## Task
Diwali sale Instagram caption for my saree shop in Lucknow, Hinglish.
Success looks like: I get one Diwali post ready to publish (hook, caption, CTA, hashtags, alt text) plus a carousel and stories version, all on-brand and specific to my account.

## If details are missing
I haven't told you these yet, so assume:
- Audience: people in India who follow accounts like mine
State these assumptions in one line at the top of your answer. If one would change the answer a lot, ask me about it first.

## Steps
1. Propose 3 angles that connect Diwali to my account naturally (e.g. behind the scenes, a useful festive tip, a gifting idea), not just "Happy Diwali" with a logo; pick the strongest and say why
2. Write the post: a first line under 12 words that works as a hook, a 80–150 word caption, one clear CTA (save, share, comment with a specific question, or visit)
3. Add 5–8 hashtags: a few festival tags plus niche and local tags; no irrelevant trending tags
4. Write alt text for the image (one sentence)
5. Turn the same idea into a 5-slide carousel and 3 story frames (with a poll or question sticker idea)
6. Note when to post relative to the Diwali date (29 Oct 2027), and tell me to check my Insights for the best time instead of claiming a universal one
7. This is a sale/offer post: make the offer the clear focus, stated exactly as I wrote it; if I didn't give the details, use [YOUR OFFER], [VALID DATES] and [HOW TO ORDER] placeholders instead of inventing them

## Constraints
- Respond in Hinglish
- Write in Hinglish: Hindi in Latin script mixed with English, the way people text on WhatsApp (e.g. "Aap sabko Diwali ki dher saari shubhkamnayein")
- Never invent discounts, prices, free gifts, stock levels, deadlines ("limited time", "only today") or testimonials. Use my offer exactly as written; if I gave none, write value-led copy and mark where an offer could go as [YOUR OFFER]
- No engagement bait ("comment YES", "tag 10 friends") and no fake urgency
- No claims that a format or hashtag is trending or will go viral
- Be respectful; do not mock or stereotype any community or tradition
- Do not invent rituals, legends or scriptural claims; if unsure, keep it general or say traditions vary by region and family
- Do not state auspicious timings (muhurat) as fact; tell readers to check a local panchang or their family priest
- Jains, Sikhs and Buddhists mark the day differently; don't assume everyone does Lakshmi Puja
- Don't glamorise loud or unsafe firecrackers; green or no-cracker celebrations are fine to mention
- No filler: skip intros, restating my request and closing summaries
- Don't invent facts, statistics, quotes, sources or details about me; flag anything I should verify

## Output format
- **Angles** table: angle | why it fits | format
- **Final post**: hook · caption · CTA · hashtags · alt text
- **Carousel** table: slide | headline (max 8 words) | visual
- **Stories** table: frame | text | sticker

## Before you answer, check
- The hook is under 12 words
- The post is clearly about my account, not a generic Diwali wish
- No invented offers, numbers or trends
- Alt text is present
- Every constraint I gave is followed

Example output

Is Diwali, apni roshni ke saath naya saree look bhi! ✨ Lucknow ki sabse pyaari collection ab sale pe. Aaj hi aaiye 🪔 #DiwaliSale #Lucknow
Try this prompt

Festival poster (Midjourney)

Weak prompt

diwali poster

PromptPilot prompt

a vibrant Indian festival poster, Diwali sale for my Indian sweets shop in Jaipur, diyas, marigold garlands, rangoli patterns, warm festive lighting, the text "Happy Diwali – 20% off" written clearly, photorealistic, high detail --ar 4:5 --v 7 --style raw

Example output

Example of what to expect: a 4:5 poster with diyas and marigolds around a sweets counter, warm lighting, and a clear headline area. (No image shown: we only show images we actually generated.)
Try this prompt

Instagram reel (Sora / Veo / Runway)

Weak prompt

make reel for cafe

PromptPilot prompt

Create a short vertical Instagram reel about chai cafe opening in Pune. Aspect ratio 9:16, about 10 seconds, photorealistic, high detail.
Shot 1 (0-3s): establishing wide shot of chai cafe opening in Pune, quick cuts, handheld energy, natural Indian street or home setting.
Shot 2 (3-6s): medium close-up, slow push-in on the main subject, natural motion.
Shot 3 (6-10s): close-up hero shot, on-screen caption at the start appears on screen.
Camera: smooth handheld, no jump in identity or faces between shots. Audio: upbeat Indian background music, no dialogue.

Example output

Example of what to expect: a 10-second 9:16 clip in three shots, a wide view of the cafe, a push-in on a cup of chai, then a close-up with the caption.
Try this prompt

Browser game brief (Claude Code / Cursor)

Weak prompt

make a browser game

PromptPilot prompt

<role>
You are a full-stack tech lead who ships small web and mobile apps quickly by scoping an MVP, choosing boring reliable tools, and building in verifiable milestones.
</role>

<context>
Stack / skills: HTML5 canvas + vanilla JavaScript, no frameworks, no build step
</context>

<task>
Build a small browser game: [game idea, e.g. snake or flappy-style] that runs by opening index.html.
Success looks like: I get a scoped MVP, a stack recommendation that fits my skills, and milestone 1 built and verifiable today.
</task>

<assumptions>
I haven't told you these yet, so assume:
- What it does and for whom: infer the core use case from my goal
- Budget and hosting: free-tier hosting and a 2-week timeline
State these assumptions in one line at the top of your answer. If one would change the answer a lot, ask me about it first.
</assumptions>

<instructions>
1. Write the MVP scope: must-have features (max 5), nice-to-haves to postpone
2. Recommend a stack with one-line trade-offs (and a no-code alternative if it fits)
3. Break the build into 3–5 milestones, each ending in something I can click or test
4. Implement milestone 1 fully: file structure, code, and how to run it
5. List how to verify milestone 1 and what to build next
</instructions>

<constraints>
- You are working inside the user's repository as a coding agent (Claude Code, Cursor or similar)
- Work in small steps; after each step run the app or tests and report what you verified
- Do not add paid services, API keys or secrets to code; read config from environment variables
- The user may write in Hinglish (Hindi in Latin script); understand it, but reply in clear English unless asked otherwise
- Never invent facts, numbers, prices, marks, reviews or client names; use [placeholders] for anything missing
- Stack: HTML5 canvas + vanilla JavaScript, no frameworks, no build step
- File structure:
- index.html
- style.css
- game.js (loop, input, collision, score)
- README.md
- Acceptance criteria:
- Opens with no console errors
- Keyboard and touch controls work
- Score and game-over screen with restart
- Best score saved in localStorage
- Runs at a steady frame rate on a mid-range phone
- Step plan:
- 1. Canvas, game loop and player movement
- 2. Obstacles/food and collision
- 3. Score, game over, restart
- 4. Touch controls and localStorage best score
- 5. README with how to play
- Complete, runnable code for milestone 1; no "...rest of code"
- Security basics: no secrets in frontend code, validate inputs
- Prefer the simplest tool that works
- Explore the relevant files before editing and keep changes minimal
- Do not modify unrelated files
- Run the tests/linters (or explain how to) before saying the task is done
- No filler: skip intros, restating my request and closing summaries
- Don't invent facts, statistics, quotes, sources or details about me; flag anything I should verify
</constraints>

<format>
- **MVP scope** (must-have / later)
- **Stack** with trade-offs
- **Milestones** table: # | deliverable | how to verify
- **Milestone 1 code** with file paths
- **Run & verify** steps
</format>

<quality_checks>
- Milestone 1 runs as written
- Scope fits the timeline
- No secrets exposed
- Every constraint I gave is followed
</quality_checks>

Example output

Example of what to expect: an agent opens index.html, ships a canvas loop with keyboard + touch, score/game-over/restart, and localStorage best score — then reports what it verified after each step.
Try this prompt

CRUD app brief (Claude Code / Cursor)

Weak prompt

banao ek CRUD app

PromptPilot prompt

<role>
You are a full-stack tech lead who ships small web and mobile apps quickly by scoping an MVP, choosing boring reliable tools, and building in verifiable milestones.
</role>

<context>
Stack / skills: Next.js (App Router) + TypeScript + SQLite via Prisma (swap for Postgres/Supabase if asked)
</context>

<task>
Build a CRUD web app to manage [resource, e.g. students or orders] with fields [list fields].
Success looks like: I get a scoped MVP, a stack recommendation that fits my skills, and milestone 1 built and verifiable today.
</task>

<assumptions>
I haven't told you these yet, so assume:
- What it does and for whom: infer the core use case from my goal
- Budget and hosting: free-tier hosting and a 2-week timeline
State these assumptions in one line at the top of your answer. If one would change the answer a lot, ask me about it first.
</assumptions>

<instructions>
1. Write the MVP scope: must-have features (max 5), nice-to-haves to postpone
2. Recommend a stack with one-line trade-offs (and a no-code alternative if it fits)
3. Break the build into 3–5 milestones, each ending in something I can click or test
4. Implement milestone 1 fully: file structure, code, and how to run it
5. List how to verify milestone 1 and what to build next
</instructions>

<constraints>
- You are working inside the user's repository as a coding agent (Claude Code, Cursor or similar)
- Work in small steps; after each step run the app or tests and report what you verified
- Do not add paid services, API keys or secrets to code; read config from environment variables
- The user may write in Hinglish (Hindi in Latin script); understand it, but reply in clear English unless asked otherwise
- Never invent facts, numbers, prices, marks, reviews or client names; use [placeholders] for anything missing
- Stack: Next.js (App Router) + TypeScript + SQLite via Prisma (swap for Postgres/Supabase if asked)
- File structure:
- prisma/schema.prisma
- app/[resource]/page.tsx (list + search)
- app/[resource]/new/page.tsx, [id]/edit/page.tsx
- app/api/[resource]/route.ts and [id]/route.ts
- lib/validation.ts
- tests/
- Acceptance criteria:
- Create, list, edit and delete all work end to end
- Server-side validation with clear error messages
- Empty state and delete confirmation
- Unit tests for validation and API routes pass
- Seed script for sample data
- Step plan:
- 1. Schema and migration
- 2. API routes with validation
- 3. List and create pages
- 4. Edit and delete
- 5. Tests and README
- Complete, runnable code for milestone 1; no "...rest of code"
- Security basics: no secrets in frontend code, validate inputs
- Prefer the simplest tool that works
- Explore the relevant files before editing and keep changes minimal
- Do not modify unrelated files
- Run the tests/linters (or explain how to) before saying the task is done
- No filler: skip intros, restating my request and closing summaries
- Don't invent facts, statistics, quotes, sources or details about me; flag anything I should verify
</constraints>

<format>
- **MVP scope** (must-have / later)
- **Stack** with trade-offs
- **Milestones** table: # | deliverable | how to verify
- **Milestone 1 code** with file paths
- **Run & verify** steps
</format>

<quality_checks>
- Milestone 1 runs as written
- Scope fits the timeline
- No secrets exposed
- Every constraint I gave is followed
</quality_checks>

Example output

Example of what to expect: create/list/edit/delete for the resource, Zod/server validation, empty state + delete confirm, and unit tests for validation and API routes — no invented fields or paid services.
Try this prompt