Forge prompts
that actually
work.

Close-up portrait of a woman in her 30s, rain-soaked Tokyo alley at 2am, neon red and teal reflections on wet pavement, Roger Deakins cinematography, anamorphic lens flare, 35mm film grain, melancholic expression, depth of field --ar 2:3 --style raw --s 50 --v 7

You are a senior content strategist and expert writer. When I give you a topic, you will:
1. Write a detailed, opinionated 1,500-word blog post structured with an H1, 4-6 H2 sections, and a clear conclusion.
2. Open with a specific surprising stat or counterintuitive claim (not a question).
3. Use short paragraphs (max 3 sentences), plain American English, active voice.
4. Include one real-world example or mini case study per section.
5. Embed 2-3 natural internal linking opportunities marked as [LINK: anchor text → topic].
6. Close with a single, specific CTA.
Never use filler phrases like 'In today's fast-paced world' or 'It goes without saying'. Write with the confidence of someone who has done this work, not read about it.

Topic: [INSERT TOPIC]

Act as a senior competitive intelligence analyst. Create a battlecard for [YOUR COMPANY] vs [COMPETITOR].

Structure it as:
1. Their positioning in one sentence (how they describe themselves)
2. Their 3 strongest claims (with evidence if you know it)
3. 3 vulnerabilities or gaps in their offering
4. 5 objection-handling lines for when a prospect says 'we already use [COMPETITOR]'
5. The 2-3 deal-winning questions a salesperson should ask to expose the gap
6. Our strongest differentiator stated in under 15 words

Be specific and direct. No diplomatic hedging.

I need to build [FEATURE NAME] in my [FRAMEWORK/LANGUAGE] project.

Context:
- Project stack: [e.g., Next.js 14, TypeScript, Supabase, Tailwind]
- The feature should: [describe behavior in plain English]
- It must NOT: [list constraints or things to avoid breaking]
- Existing related files: [list file paths]
- Auth/session context: [describe how auth works in this project]

Please:
1. List the files you'll create or modify before writing any code
2. Write the complete implementation with no placeholders
3. Include TypeScript types for all new data structures
4. Add inline comments only where logic is non-obvious
5. Write one Vitest unit test for the core logic

Do not ask clarifying questions — make the most reasonable assumption and note it.

Brand mood board for an organic skincare line, flat lay arrangement on aged linen, terracotta clay pots, dried botanicals, raw beeswax, smoked glass dropper bottles, earthy palette of sage moss warm ivory and burnt sienna, soft north light, editorial magazine aesthetic --ar 3:2 --s 200 --v 7

Bold sans-serif typographic poster, the phrase YOUR NAME IN LIGHTS rendered in holographic chrome foil, floating on deep navy background, prismatic light scatter, scattered holographic confetti, Y2K-meets-luxury aesthetic, centered composition --ar 9:16 --style raw --s 150 --v 7