Best Prompts by Role: Developer, Marketer, Founder, Designer, and Analyst
·
5 min read
Introduction
A large prompt library is useful, but people rarely search by abstract prompt taxonomy. They search by work: “I am a developer,” “I need help with marketing,” “I need to draft a proposal,” or “I am analyzing metrics.” That is why organizing prompts by role is often more practical than organizing them by theory alone.
Table of Contents
- Why role-based prompt selection is useful
- Best prompts for developers
- Best prompts for marketers
- Best prompts for founders
- Best prompts for designers
- Best prompts for analysts
- How to build your own personal prompt stack
Why Role-Based Prompt Selection Helps
Role-based prompt selection helps you:
- find useful templates faster
- avoid using the wrong prompt for the wrong kind of work
- build a more realistic personal workflow
- identify which prompts are worth saving as reusable templates
Best Prompts for Developers
1. Ask for Structure Before Code
I need to implement {feature} in {stack}.
Do not write code yet.
First:
1. propose the class / module structure
2. define each part's responsibility
3. identify failure modes
4. say what should be tested first
2. Debug by Hypothesis
Symptom: {symptom}
Reproduction: {reproduction}
Logs: {logs}
Give me the 3 strongest hypotheses, the cheapest verification step for each, and what data is still missing.
3. Review Mechanical Risk
Review this code using only 5 criteria: validation, authorization, query efficiency, error handling, and test gaps.
Best Prompts for Marketers
4. Generate an SEO Outline
Create a detailed outline for an article about {topic}.
Audience: {audience}
Intent: {intent}
Angle: {angle}
Output: title options, meta description, H2/H3 structure, key takeaways, and internal link ideas.
5. Repurpose One Article Across Channels
From the long article below, create 3 social captions, 1 newsletter draft, 5 quote cards, and 1 short 60-second video script.
6. Write LinkedIn Posts with Real Insight
Write 5 LinkedIn posts about {topic}, each starting with one clear insight, ending with one practical takeaway, and avoiding hype.
Best Prompts for Founders
7. Stress-Test an Idea
I am considering this idea: {idea}.
Act like a skeptical reviewer.
List the 5 biggest weaknesses, the assumptions most likely to fail, and a smaller scope worth testing first.
8. Write a Decision Memo
From the following context / data, write a decision memo with: Decision, Context, Options, Trade-offs, Recommendation, and Open Questions.
9. Prepare for a Discovery Call
Create 15 discovery call questions for a prospective customer, grouped by current workflow, pain points, decision process, budget/timing, and success criteria.
Best Prompts for Designers
10. Use a Structured Image Prompt Formula
[subject], [environment], [composition], [style], [lighting], [color palette], [camera cues], [quality cues]
11. Create a Storyboard for Video Work
Create a 6-scene storyboard for a video about {topic}. For each scene, include the purpose, frame description, movement, camera direction, and suggested duration.
12. Generate Variants from One Visual Direction
Here is the visual direction I like: {reference style}.
Create 5 new variants with the same mood and structure, but different focal subjects or compositions.
Best Prompts for Analysts
13. Write SQL from a Business Question
Schema: {schema}
Business question: {question}
Dialect: {sql_dialect}
Return the SQL, explain the logic, list assumptions, and point out edge cases.
14. Explain a KPI Shift
KPI change: {metric_change}
Time window: {window}
Related metrics: {related_metrics}
Give me 5 hypotheses, the data to check, and the order in which the investigation should happen.
15. Write a Weekly Report That Means Something
From the following metrics, write a weekly report using: What changed, Why it likely changed, Risks, and Recommended actions.
Useful Prompts for Every Role
16. Force Clarifying Questions When Needed
If the input is not sufficient for a strong answer, do not guess. Ask up to 5 clarifying questions first.
17. Separate Fact, Assumption, and Recommendation
Separate clearly:
1. what is directly supported by the input
2. what is a reasonable assumption
3. the recommendation
4. what still needs validation
18. Split the Task into Two Steps
Do not give the final answer immediately.
First analyze the possible approaches. Then provide the final output.
How to Build Your Own Personal Prompt Stack
A practical approach looks like this:
- identify the 5 tasks you repeat most often
- save the prompts that give the most stable output
- refine those prompts for your own tone and workflow
- split them into templates by task type
Common Mistakes
- using one prompt for too many kinds of work
- failing to define role, goal, and output format
- not saving prompts that already worked well
- trying to optimize every prompt instead of the few that matter most
FAQ
Should I create one master prompt for everything?
Usually no. Strong prompts tend to be task-specific. One universal prompt usually gives average output across all tasks.
Where should I start building a personal prompt library?
Start with the 3-5 tasks you do every week. Prompts that support repeated workflows are the ones that create lasting value.
Key takeaways:
- Organizing prompts by role is often more useful than organizing them by theory alone.
- Each role has a small core set of prompts worth saving as reusable templates.
- The most useful universal prompts are the ones that force AI to expose assumptions and ask for missing information.
- You do not need a huge prompt library. You need a small set of high-value prompts for recurring work.
- The best prompt library is the one refined around your real workflow.
Conclusion
Good prompting is not just about models or frameworks. It is also about matching the prompt to the work you are actually doing. When prompts are organized by role, they become easier to find, easier to reuse, and much easier to turn into an everyday workflow asset.