Learn AI
Prompting Guide
Learn how to write prompts that get great results from AI. Master the ROCOV framework with 12 real-world examples and build your own prompts with the interactive tool.
What You Will Be Able to Do
- Turn a vague request into a clear objective with relevant context.
- Set constraints, output format, and checkable acceptance criteria.
- Iterate on a first response without surrendering judgment.
- Recognize when a production workflow needs structured output and deterministic validation.
The ROCOV Framework
Every great AI prompt follows six components. Remember the acronym ROCOV to structure your prompts for consistent, high-quality results.
R — Role
Tell the AI who it should be. This sets the tone, expertise level, and perspective for the response.
O — Objective
State clearly what you want the AI to do. Be specific about the task and the desired outcome.
C — Context
Provide background information. The more relevant context you give, the better the AI can tailor its response.
C — Constraints
Set boundaries. Specify length, format, tone, topics to avoid, or any limitations the AI should follow.
O — Output
Describe the format you want. Should it be a table, bullet list, email, paragraph, or code?
V — Verification
Tell the AI how to check its work. Ask it to review for accuracy, completeness, or specific criteria.
Tip: You do not need all six components for every prompt. Start with Role, Objective, and Context, then add Constraints and Output as needed. Verification is most useful for complex or high-stakes tasks.
Example 1: Writing a Professional Email
Before
Write an email about a meeting.
After (ROCOV)
Role: You are an experienced project manager.
Objective: Write a meeting invitation email.
Context: Our team needs to discuss the Q2 marketing campaign timeline. The meeting is next Tuesday at 2 PM, lasting one hour. Three team members will present their sections.
Constraints: Keep it under 150 words. Use a friendly but professional tone.
Output: A complete email with subject line, greeting, body, and sign-off.
Verification: Review the email to ensure all meeting details (date, time, duration, agenda) are included and accurate.
Example 2: Researching a Business Idea
Before
Tell me about starting a coffee shop.
After (ROCOV)
Role: You are a small business consultant with 15 years of experience in the food and beverage industry.
Objective: Help me evaluate whether opening a specialty coffee shop in a university town is a good business idea.
Context: I am considering opening a coffee shop near a university with 20,000 students. My budget is $80,000. I have no prior experience in the food industry but I am passionate about specialty coffee.
Constraints: Focus on realistic challenges and opportunities. Do not give generic advice. Include specific numbers where possible.
Output: A structured analysis with sections for market opportunity, startup costs, potential revenue, key risks, and a recommendation.
Verification: Check that all cost estimates are reasonable for a small town and flag any assumptions that need local research.
Example 3: Creating a Social Media Marketing Campaign
Before
Give me social media ideas for my bakery.
After (ROCOV)
Role: You are a social media marketing specialist for small food businesses.
Objective: Create a one-week social media campaign for a new bakery opening in a suburban area.
Context: The bakery specializes in artisan bread and pastries. It will open next month. Target customers are families and young professionals in the neighborhood. Budget for paid ads is $500 for the month.
Constraints: Focus on Facebook and Instagram only. Include at least one interactive post idea. Do not suggest influencer partnerships.
Output: A daily content plan with post type, suggested caption, and recommended visual for each day.
Verification: Review the plan to ensure each day has a unique post type and that the campaign builds anticipation for the opening.
Example 4: Analyzing Sales Data
Before
Analyze this sales data.
After (ROCOV)
Role: You are a data analyst specializing in retail sales.
Objective: Analyze the attached monthly sales data and identify trends.
Context: I run a small retail clothing store with 3 locations. Here are 12 months of sales data by product category and location. I want to know which products and locations are performing best and worst.
Constraints: Do not make assumptions beyond the data provided. If the data is insufficient for a conclusion, say so clearly.
Output: A summary of key findings followed by a table showing top 3 and bottom 3 product-location combinations.
Verification: Cross-check all numbers in the summary against the data table to ensure accuracy.
Example 5: Planning a Project
Before
Help me plan a project.
After (ROCOV)
Role: You are a project management expert certified in Agile and Waterfall methodologies.
Objective: Create a project plan for launching a company newsletter.
Context: Our company has 50 employees. We want to launch a monthly internal newsletter to improve communication. I have a team of 2 people working on this part-time. We have 6 weeks until the first issue.
Constraints: Include a timeline with milestones, a task breakdown, resource requirements, and potential risks. Keep the plan practical for a small team.
Output: A project plan in table format with columns for phase, tasks, owner, deadline, and status.
Verification: Review the timeline to ensure it is realistic and that no tasks are missing before the launch date.
Example 6: Troubleshooting a Software Issue
Before
My website is broken. Help.
After (ROCOV)
Role: You are a senior web developer with expertise in HTML, CSS, and JavaScript debugging.
Objective: Help me diagnose and fix a CSS issue on my website.
Context: My website layout looks correct on desktop but the navigation menu overlaps with the content on mobile devices (screen width under 768px). I am using a CSS media query but it does not seem to be working.
Constraints: Provide specific code fixes. Explain what each fix does. Do not suggest rewriting the entire layout.
Output: Step-by-step troubleshooting guide followed by the corrected CSS code.
Verification: Describe how to test the fix in a browser to confirm it works on mobile viewports.
Example 7: Creating Social Media Content
Before
Write some Twitter posts about AI.
After (ROCOV)
Role: You are a social media content creator who specializes in making complex technology topics accessible.
Objective: Write 5 Twitter posts about AI for small business owners.
Context: My audience runs small businesses and has basic AI knowledge. They want practical tips they can use immediately. My brand voice is friendly, encouraging, and slightly informal.
Constraints: Each tweet must be under 280 characters. Include at least one question or call-to-action in each tweet. Do not use jargon without explanation. Include relevant hashtags.
Output: 5 separate tweets, each with suggested hashtags.
Verification: Check that each tweet is under 280 characters, uses accessible language, and provides a clear takeaway.
Example 8: Improving Customer Service Responses
Before
Write a response to a complaint.
After (ROCOV)
Role: You are a customer service manager with expertise in de-escalation and conflict resolution.
Objective: Write a professional response to a customer complaint about a delayed order.
Context: A customer ordered a gift for their anniversary and it was supposed to arrive 3 days ago but has not. They sent an angry email. Our company policy allows full refunds or expedited free shipping.
Constraints: Be empathetic but not defensive. Do not blame other departments. Offer a clear solution. Keep the tone warm and professional.
Output: A complete email response with subject line.
Verification: Review the response to ensure it acknowledges the customer's frustration, offers a concrete solution, and does not make promises that cannot be kept.
Example 9: Preparing a Team Meeting Agenda
Before
Make a meeting agenda.
After (ROCOV)
Role: You are an executive assistant who specializes in organizing efficient team meetings.
Objective: Create a 45-minute meeting agenda for our weekly team stand-up.
Context: Our team has 8 members. We meet every Monday morning. We need to cover project updates, blockers, and upcoming deadlines. Each person gets about 3 minutes.
Constraints: Include time allocations for each agenda item. Add a buffer for unexpected topics. Keep the agenda to one page.
Output: A structured agenda with time slots, topics, and responsible person for each item.
Verification: Ensure the total time does not exceed 45 minutes and that all critical topics are covered.
Example 10: Learning a New Skill
Before
Teach me about Excel.
After (ROCOV)
Role: You are a patient Excel instructor who teaches beginners through practical examples.
Objective: Create a learning plan for someone who knows basic Excel and wants to become proficient.
Context: I use Excel for personal budgeting and my small business finances. I know how to enter data and do simple sums but I have never used formulas, charts, or pivot tables. I can practice 30 minutes per day.
Constraints: Focus on skills I will use for business and budgeting. Skip advanced features like VBA or Power Query. Provide one exercise per skill level.
Output: A 4-week learning plan with daily topics, practice exercises, and self-assessment questions.
Verification: Review the plan to ensure it builds progressively and that each week introduces manageable new concepts.
Example 11: Writing Software Documentation
Before
Write documentation for this code.
After (ROCOV)
Role: You are a technical writer specializing in developer documentation.
Objective: Write clear documentation for a JavaScript function that calculates tax.
Context: The function takes a price and tax rate, handles decimal precision, and returns the total. It is used by our e-commerce team. Other developers may need to modify it.
Constraints: Use plain language. Include code examples. Explain edge cases like negative prices or zero rates.
Output: Documentation with function description, parameters, return value, usage examples, and common pitfalls.
Verification: Review the documentation to ensure a developer could use the function without reading the source code.
Example 12: Creating a Presentation Outline
Before
Make a presentation about AI.
After (ROCOV)
Role: You are a presentation coach who helps professionals create engaging, clear presentations.
Objective: Create an outline for a 20-minute presentation about AI for business leaders.
Context: I am presenting to a group of small business owners who are curious about AI but worried it is too complex or expensive. I want them to leave feeling empowered, not overwhelmed.
Constraints: Include a hook to grab attention, 3 main points with examples, and a clear call to action. Suggest visual ideas for each slide. Keep it to 10-12 slides.
Output: A slide-by-slide outline with title, key message, and visual suggestion for each slide.
Verification: Review the outline to ensure the presentation flows logically and that the call to action is specific and actionable.
Interactive Prompt Builder
Use this tool to build your own ROCOV prompts. Fill in each section and click "Generate" to see your completed prompt. You can copy it and paste it into any AI tool.
Your generated prompt will appear here...
Protecting Your Private Information
When using AI tools, it is important to protect sensitive information. Here are key guidelines:
- Never share passwords, credit card numbers, or social security numbers with any AI tool.
- Remove personal identifiers from documents before uploading them to AI tools. Replace names with "Person A" or "Employee 1".
- Do not paste proprietary business data such as financial records, trade secrets, or confidential client information into public AI tools.
- Use AI tools that offer data privacy guarantees. Check the privacy policy of any AI tool before using it with business information.
- Assume everything you type into an AI tool could be stored or reviewed. When in doubt, do not enter it.
- For sensitive business tasks, consider using enterprise AI tools with data encryption and access controls.
Recognizing AI Hallucinations
AI tools can sometimes generate information that sounds confident but is completely wrong. This is called a "hallucination." Here is how to spot them:
- Overly specific but unverifiable details: If the AI cites a specific law, statistic, or quote that you cannot verify, be skeptical.
- Confident tone with no sources: AI may state false information with complete confidence. Always check facts from a reliable source.
- Inconsistent information: If the AI gives different answers to similar questions, one of them is likely wrong.
- Made-up citations: AI sometimes invents book titles, author names, or research papers. Search for any citations the AI provides.
- Logical gaps: If the AI jumps to a conclusion without explaining its reasoning, it may be hallucinating.
Best practice: Always verify important information from at least one independent, reliable source before acting on AI-generated content.
Using AI as a Collaborator
The most effective way to use AI is as a thinking partner, not just a tool. Here are strategies for collaborative AI use:
- Iterate: Treat the first response as a draft. Ask follow-up questions, request revisions, and refine until you are satisfied.
- Challenge the AI: Ask the AI to argue against its own answer. This often reveals blind spots and produces better results.
- Ask for alternatives: Request multiple approaches to a problem. "Give me three different ways to solve this" often leads to creative solutions.
- Use it for brainstorming: Generate a list of ideas, then pick the best ones and develop them further. AI is great at quantity; you provide the quality filter.
- Explain your reasoning: When you explain your thought process to the AI, it can give more targeted and useful feedback.
- Combine AI with your expertise: AI provides options and drafts; you provide judgment, context, and the final decision. The best results come from this partnership.