Free AI Content Creation Templates

Outcome

Turns vague asks into crisp requirements.

When to use

When the request is fuzzy or you want fewer iterations.

Template

You are a senior analyst. Before answering, ask me up to 7 clarifying questions.

Context I can provide: audience, constraints, deadline, format.

After questions, propose 2 solution approaches and recommend one.

Tips

• Cap questions (5–7) to reduce friction.
• Ask for output format explicitly (bullets/table/JSON).

Outcome

Cleaner output with fewer hallucinations.

When to use

When you need reliable formatting and tone.

Template

Act as an editor.

Goal: <what you want>
Constraints: <length, tone, do/don't>
Output format: <exact format>

Input:
<paste text>

Tips

• Write constraints as checkboxes: must/must not.
• Define the output format like a contract.

Outcome

Matches tone and structure without copying content.

When to use

When you want consistent voice across outputs.

Template

You are a writing assistant. Learn the STYLE from the examples (not the facts).

Examples:
1) <example>
2) <example>

Now write a new piece on: <topic>
Constraints: <length, format>
Do not reuse sentences; only mimic tone and structure.

Tips

• Provide 2–3 examples max.
• Explicitly prohibit reuse of sentences.

Outcome

Self-corrects obvious flaws quickly.

When to use

When quality matters more than speed.

Template

Task: <task>

Step 1 — Draft: produce an initial answer.
Step 2 — Critic: list 5 concrete weaknesses.
Step 3 — Revise: produce an improved final answer addressing each weakness.

Output only the final answer (no steps).

Tips

• Ask for “concrete weaknesses” not generic critique.

Outcome

Improves factual discipline and uncertainty handling.

When to use

When the model might guess.

Template

You are a careful researcher.
If you are not sure, say "I don't know" and ask for what you need.
Cite assumptions explicitly.

Question: <question>
Constraints: bullet points, max 200 words.

Tips

• Force explicit assumptions.
• Cap length to prevent rambling.

Outcome

Turns “good/bad” into measurable feedback.

When to use

When reviewing copy, prompts, or plans.

Template

Evaluate the following against this rubric and score each dimension 1–5.

Rubric:
- Clarity
- Specificity
- Completeness
- Risk/edge cases
- Actionability

Then propose the top 3 improvements.

Item:
<paste>

Tips

• Keep rubrics short (5–7 dimensions).

Outcome

Finds issues + gives concrete diffs.

When to use

Before merging or refactoring.

Template

You are a strict code reviewer. Review the code below.

Return: (1) critical issues, (2) improvements, (3) refactor suggestion.
For each issue: explain impact and show a minimal patch (diff-style).

Code:
```
<paste code>
```

Tips

• Ask for diffs.
• Request tests if behavior changes.

Outcome

Systematic debugging plan instead of random guesses.

When to use

When you have an error and limited context.

Template

You are a senior engineer. Given the bug report, produce:
1) Top 5 hypotheses (ranked)
2) For each, 1–2 experiments to confirm/deny
3) Likely fix and risks

Bug report:
<paste>

Tips

• Ask for environment/version info early.

Outcome

Consistent, scannable news summaries.

When to use

When summarizing announcements/research.

Template

Summarize the article below into EXACTLY 4 bullets:
• What happened
• Why it matters
• Practical takeaway
• Link

Then add a 1-sentence “who should care” line.

Article:
<paste>

Tips

• Force “exactly 4 bullets” to control length.

Outcome

Produces CTA copy that matches intent and reduces friction.

When to use

When writing landing pages or newsletters.

Template

Write 12 CTA button labels for this offer.

Offer: <offer>
Audience: <audience>
Tone: <tone>

Rules: keep each CTA under 22 characters; avoid vague verbs like “Submit”.

Tips

• Ask for character limits.
• Write CTAs for different intent levels.

Outcome

A schedule that respects time and energy.

When to use

When you feel overloaded.

Template

You are my planning assistant. Create a realistic plan for the week.

Inputs:
- Fixed commitments: <list>
- Priorities (top 3): <list>
- Available hours/day: <number>
- Energy pattern: <morning/evening>

Output: a day-by-day schedule + 5-minute next action for each priority.

Tips

• Always include a “next action”.

Outcome

Fast comprehension without losing key nuance.

When to use

When you want a 60-second summary. Specifically for email output.

Template

Summarize the text below for a busy reader.

Output:
- 3 bullet summary
- 1 risk/limitation
- 1 action step

Text:
<paste>

Output must be formatted for: Email.
Tone: <tone>.
Length: <limit>.

Tips

• Ask for “risk/limitation” to prevent one-sided summaries.
• Specify tone + length to avoid drift.