Turning One-Off Prompts into Reusable Macaron Routines
Guardrails: Privacy, Approvals, and Audit Trails
Conclusion & Next Steps
Frequently Asked Questions
How to Use AI as a Personal Assistant: 30 Prompts That Actually Work
How to Use AI as a Personal Assistant: 40 Prompts That Actually Work
You have probably heard that an AI personal assistant can save you time. The less obvious part is what to ask it on an ordinary Tuesday, when your inbox is full, a meeting has moved, and you still need to decide what is for dinner.
The trick is to give it a real task with enough context to produce something you can use. “Help me get organized” usually returns general advice. “Here are my three deadlines, two meetings, and the hour I need to leave—build a realistic plan” gives it a job.
This guide gives you 40 prompts across communication, scheduling, projects, travel, research, daily life, learning, and self-reflection. For each category, you will see what information to provide, what kind of output to expect, and how to correct an answer that misses the mark. We will also separate making a planfrom carrying it out. An assistant can draft an email or propose a meeting time in a chat; sending the email or changing a calendar requires the right connection, permissions, and your approval.
Disclosure: This guide is published by Macaron. The prompts work with any capable AI assistant. Where Macaron is mentioned, check the features and permissions available in your version of the app before relying on a connected or automated workflow.
Start Here — Give Your AI the Personal Context It Needs
The difference between a generic answer and a useful assistant often comes down to context. A chatbot can suggest a schedule for anyone. A personal assistant should account for your working hours, the meeting you cannot move, the fact that you prefer a quiet morning, and the family commitment at 5 PM.
That does not mean giving it your entire life story. Think of it as briefing a new human assistant. Tell it what regularly affects its recommendations, then add details when a specific task calls for them.
Useful starting context might include:
Your usual work hours and meeting preferences
Your preferred tone for emails and messages
Recurring responsibilities you want included in plans
Constraints such as school pickup, commute time, or a budget
A decision rule, such as “ask before scheduling anything after 5 PM”
Which information it may use and which actions need approval
Preferences can change. Review them when the assistant keeps making the same wrong assumption. And check how your chosen product handles memory: remembering something during the current conversation is different from retaining it for future ones. For example, ChatGPT’s memory documentation describes controls for reviewing and changing remembered information; those controls vary by account and settings.
Copy-Ready Personal Context Setup Prompt
Use this when you first set up an assistant, or when its answers have become too generic:
Act as my personal assistant. My usual work hours are [hours]. I prefer meetings [preference], and I need [buffer] between them. My communication style is [tone]. My current priorities are [priorities]. Please account for these recurring constraints: [constraints].
When you draft a message, let me review it before sending. When you suggest a calendar change, show me the proposed change before making it. If you cannot access my calendar, contacts, or task list, say so and use only the information I provide. Ask one clarifying question if a missing detail would materially change your answer.
You do not have to fill every bracket. A few reliable preferences are more useful than a long profile you never update.
What you should expect: The assistant should acknowledge the rules and use them in a small test request. Try: “Plan tomorrow around these three tasks and my 3 PM appointment.” If it schedules work after your stated cutoff, correct that assumption before giving it a bigger job.
What Not to Put in a Personal Assistant Prompt
Do not paste passwords, full payment details, government ID numbers, private medical records, or confidential company information into a general prompt. Avoid sharing someone else’s sensitive information unless you have the right to do so and the tool is approved for that use.
Often, the assistant does not need the identifying detail. “Draft a calm reply to a client about a billing dispute” may be enough; the client’s name and account number can be added later in your email app.
For sensitive work, the useful question is: What is the smallest amount of information the assistant needs to produce a good draft? Give it that. If you connect accounts or upload files, review the product’s permissions and privacy terms as well as your employer’s rules.
Principles of Effective Delegation to AI
Treat the assistant like a capable colleague receiving a brief. It can help quickly, but it cannot reliably infer the deadline you forgot to mention or know whether “send this” means “write a draft” or “contact a real person.”
Here are six principles that make everyday requests more useful.
Be clear about the task. “Help with travel” could mean compare flights, build an itinerary, write a packing list, or book a ticket. Start with the action you want: “Compare three nonstop flights from New York to London for these dates. Include baggage costs and arrival times.”
Supply the inputs it actually needs. Paste the email thread you want summarized. Give the task list you want prioritized. State the dates, budget, and location for a trip. If the assistant has a connected source, identify it: “Use my calendar for next week.” If it does not, paste the relevant details rather than expecting it to guess.
Describe the output. Ask for an agenda, a draft email, a table of options, or a short checklist. An output format gives you something you can inspect. “Return three options with price, travel time, and one drawback each” is easier to use than “tell me the best option.”
Break larger jobs into stages. For a team offsite, ask the assistant to list the selection criteria first. Confirm them. Then ask for a venue comparison. Booking comes after you have checked the options. A good sequence creates natural points where you can catch an error.
Correct the first answer. “This is too formal; keep the first paragraph and shorten the rest” is useful feedback. So is “You assumed I can work Friday evening. I cannot. Rebuild the plan.” You do not need to rewrite the entire prompt each time.
Set action boundaries. Ask for drafts and proposals before external actions. “Prepare the invitation, but do not send it” is clearer than hoping the assistant understands where your approval is required.
The ramsac personal-assistant prompt guide uses a structured formula that covers role, request, examples, adjustments, output type, and extra context. The practical lesson is simple: specify enough for the assistant to do the task, then refine the result. Coursera’s personal-assistant guide also organizes uses around planning, communication, and learning, with follow-up prompts that make an initial answer more specific.
You do not need to recite a formula every time. Once you know the pattern, a good request can still be one sentence long.
The Reusable Personal Assistant Prompt Formula
For a task that keeps producing vague answers, use this structure:
Role + Goal + Context + Inputs + Constraints + Output Format + Approval Rule
Here is a copy-ready version:
Act as my [role]. Help me [specific goal]. Here is the context: [relevant background and preferences]. Use these inputs: [pasted material or connected source]. Follow these constraints: [deadline, budget, tone, privacy limits, things to avoid]. Return [format]. State any assumptions you made. Before taking an external action, show me what you plan to do and ask for approval.
For example:
Act as my planning assistant. Help me plan tomorrow. I prefer deep work in the morning, meetings after lunch, and 30 minutes between calls. Here are my fixed events: [events]. Here are my tasks and deadlines: [tasks]. Protect 90 minutes for the proposal draft and end the workday by 5 PM. Return a timed agenda and flag anything that does not fit. Do not change my calendar.
That last sentence matters. It tells the assistant that you want a proposed schedule, not a calendar edit. If you later decide to add the blocks, you can give a separate instruction and confirm the details.
If the output is weak: Ask, “Which part of this plan depends on an assumption? Show me a version that protects the proposal deadline even if my 2 PM meeting runs long.” You will often get more value from that follow-up than from starting over.
Relationships, Gifts, and Personal Life Admin
Personal assistance is not only about work. Remembering an occasion, planning a meal for people with different needs, or drafting a thoughtful message can take surprising amounts of mental space.
Give the assistant the context that makes the answer personal without handing over unnecessary private details:
“Help me choose a birthday gift for my sister. She likes hiking and cooking, dislikes clutter, and my budget is $75. Give me five ideas and tell me why each might fit.”
“Draft a warm, brief thank-you note to a friend who hosted dinner. Keep it casual; we know each other well.”
“Create a packing checklist for a weekend trip with my partner and child. We have one small suitcase, mild weather, and one formal dinner.”
“Plan a low-stress dinner for six. One guest is vegetarian, another avoids dairy, and I want most of the cooking done before anyone arrives.”
“What details should I collect before arranging a group trip? Turn the questions into a short message I can send everyone.”
These requests work because they describe a real decision. If the gift list still feels generic, add one detail the assistant could not know: “She already owns a good water bottle and never uses gift cards. Try again.”
40 Copy-Ready Prompts by Category
The 40 prompts below are organized by the job you need done. Replace the bracketed text with your own details. Where a prompt mentions a calendar, inbox, document, or task app, provide the information yourself unless your assistant has access to that source.
An AI assistant may give you a convincing answer that is incomplete or wrong. Treat each output as something to review, especially when it involves a date, price, source, personal detail, or message to another person.
Email & Communication
For email tasks, the best input is usually the actual thread or a short summary of what happened. Remove details the assistant does not need. Decide whether you want a recap, a draft, or an edit.
1. Summarize a thread
Here is an email thread about [topic]: [paste thread]. Summarize the decision, unresolved questions, action items, owners, and dates. If an owner or date is not stated, mark it “not specified” rather than guessing.
What you get: A recap you can use before replying or entering a meeting.
If it misses something: “You left out the budget concern raised in the second email. Add it under unresolved questions.”
2. Draft a reply
Draft a reply to [person] about [issue]. Acknowledge [concern], give this status update: [facts], and propose [next step]. Keep the tone [tone] and the email under [length]. Do not invent a completion date.
What you get: A draft, not a sent message. Check the facts and tone before you use it.
3. Prepare a meeting invitation
Write an invitation for a [length] brainstorm on [date] at [time]. The goal is [goal]. Ask attendees to bring [preparation]. Include a placeholder for the meeting link and list anything I should confirm before sending.
What you get: Invitation text and a short pre-send check. A real calendar event requires a separate action and the right permissions.
4. Edit a sensitive draft
Here is my draft to [audience]: [paste draft]. Make it slightly more [formal/warm/direct], cut repetition, and keep every factual claim unchanged. Show me the revised version, then list any sentence you changed substantially.
What you get: A cleaner draft while preserving your meaning. Compare the revised text with the original before sending.
5. Brief a long message
I have one minute before a meeting. Summarize this message from [source]: [paste text]. Give me the three points I need to know, one decision I may be asked to make, and any deadline. Do not treat a suggestion as an agreed decision.
What you get: A compact briefing rather than a shortened version of every paragraph.
For a recurring inbox task, save the prompt in whichever tool you use. If that tool supports scheduled access to your inbox, check what it can read and whether it can send messages. A saved prompt alone cannot monitor new email.
Calendar & Scheduling
A schedule prompt needs fixed commitments, flexible tasks, time zone, and realistic buffers. If your assistant cannot read your calendar, paste the relevant events. If it can, check that it has the right calendar and date.
6. Find a meeting time
I need a 30-minute meeting with [people] next week about [topic]. Prefer afternoons, avoid Wednesday, and leave 15 minutes between meetings. Using the availability I provide below, suggest three slots. Do not book one yet. Availability: [paste].
What you get: A shortlist to approve. If the assistant has calendar access, verify whose availability it can actually see.
7. Build today’s agenda
Here are today’s fixed events and tasks: [paste]. Build a timed agenda that includes preparation for each meeting, one break, and a realistic finish at [time]. Flag any work that does not fit instead of squeezing it into an impossible schedule.
What you get: A usable day plan with conflicts made visible.
8. Protect focus time
Here is my calendar for the week: [paste or identify connected calendar]. Find two uninterrupted two-hour blocks for [project]. Prefer [days/times]. Show the proposed blocks and what I would need to move; do not change any event.
What you get: Candidate focus blocks. “Free” on a calendar does not always mean you have the energy or permission to use that time.
9. Prepare a recurring reminder
I need a reminder to submit [report] every Friday at 4 PM in [time zone]. Write the reminder text, tell me what information should be included, and ask before creating a recurring event or notification.
What you get: A defined reminder ready to set up. Whether it runs automatically depends on your assistant’s scheduling features. For one example of how scheduled AI tasks work and where availability varies, see OpenAI’s scheduled-tasks documentation.
10. Add travel time
I have a meeting at [address] on [date] at [time]. My previous commitment ends at [time/place]. Estimate the travel time using a source you can access, add a sensible buffer, and tell me when I should leave. If you cannot check current travel times, say so.
What you get: A departure plan with its assumptions exposed. Check the route yourself before a high-stakes appointment.
If the first schedule fails: “You used the wrong time zone and left no lunch break. Rebuild the agenda in [time zone], keep all fixed meetings, and show what no longer fits.”
Task & Project Management
Task lists become useful when the assistant can see deadlines, dependencies, and the amount of time each item may take. “Prioritize these” is a start; “tell me what I can finish before 3 PM” gives you a decision.
11. Extract action items
Here are my meeting notes: [paste]. Pull out every action item. For each, show the task, owner, deadline, and the sentence in the notes that supports it. Write “unclear” where a detail is missing.
What you get: A task list you can check against the source. The evidence column makes invented owners easier to spot.
12. Rank today’s work
These are my five tasks: [list]. These are the deadlines: [list]. I have [amount] of working time today. Rank the tasks, estimate which can realistically fit, and tell me what should be deferred. Explain any trade-off in one sentence.
What you get: A plan that accounts for capacity, not just urgency labels.
13. Break down a large project
“Launch our new blog” is too broad. Break it into tasks I can complete in 30–90 minutes. Group them by dependency, identify what needs someone else’s approval, and suggest the first action I can take today.
What you get: A starting checklist, with waiting points visible.
14. Draft a deadline reminder
Here is the list of deliverables, owners, and due dates: [paste]. Draft a polite reminder I can send to the team. Mention only the items supported by this list. Keep it direct and avoid implying someone has missed a deadline if it is not yet due.
What you get: A draft grounded in your task data, ready for your review.
15. Close a completed task
I finished [task]. Based on this project checklist: [paste], what follows logically? Separate required next steps from optional suggestions. Do not mark anything complete or notify anyone.
What you get: A clean next-step check without an unapproved update to your project tool.
If the list is too ambitious: “You assumed every task takes 20 minutes. Use the durations I provided and give me a version that fits in four hours.”
Travel Planning
Travel is where an assistant can sound especially confident while using old prices or missing a practical detail. Give it dates, route, budget, baggage, flexibility, and what matters most to you. Ask it to distinguish live information from estimates.
16. Compare flights
Find three nonstop flights from [origin] to [destination], leaving [date/window] and returning [date/window]. I need [baggage]. Show departure and arrival times, total trip time, baggage rules, and the price source with the time checked. If you cannot access live prices, give me a comparison template instead.
What you get: A shortlist or a clear statement that live search is unavailable. Verify the fare before purchasing.
17. Narrow down hotels
I need a hotel in [city] for [dates], up to [budget] per night, near [location]. Reliable Wi-Fi and [other requirement] matter more than amenities. Give me three candidates, their trade-offs, and what I should verify before booking.
What you get: A focused comparison rather than a generic “top hotels” list.
18. Draft a relaxed itinerary
Plan a two-day visit to [city]. I care about [interests], prefer [pace], and want no more than [number] main activities a day. Group nearby activities, leave time for meals, and flag any opening hours or tickets that need checking.
What you get: A draft itinerary with fewer impossible cross-city jumps.
19. Build a packing list
Make a packing checklist for a five-day business trip to [place] in [month]. I have a two-day conference, one formal dinner, and time for sightseeing. I am taking [luggage]. Separate essentials, weather-dependent items, and things to check before departure.
What you get: A list organized around the actual trip instead of a universal packing list.
20. Plan a late arrival
I land at [airport] at [time] on [date] and need to reach [destination]. Compare practical transport options, including when the last service runs. Show estimated cost, travel time, and the safest fallback if my flight is delayed. Say which details require a current check.
What you get: A route plan with a backup, not a promise that a particular train will still be running.
If the first itinerary is weak: “You put two attractions on opposite sides of the city on the same morning. Regroup the days by neighborhood and leave 45 minutes between locations.”
Research & Information Gathering
An assistant is good at organizing information. It can also present an unsupported statement in the same confident tone as a verified one. Ask it to show its sources, label uncertainty, and separate facts from interpretation.
21. Prepare a competitor snapshot
Compare [three organizations] for [specific purpose]. For each, give one documented strength, one limitation, and the source for any current product claim. Use information available as of [date]. If you cannot verify a claim, mark it unverified.
What you get: A starting comparison you can inspect, not a final purchasing decision.
22. Summarize an article
Summarize the article below in five bullets, focusing on its conclusions and any numbers that matter: [paste article or provide link]. Add one bullet explaining what the article does not establish. Do not introduce facts from outside the source.
What you get: A concise summary that stays tied to the material you supplied.
23. Explain an unfamiliar concept
Explain [concept] to someone with no technical background in under 150 words. Use one concrete example. Then tell me which part of the explanation is simplified and what I should learn next.
What you get: A first explanation without pretending the simplified version is the whole subject.
24. Compare two options
Compare [option A] and [option B] for someone whose priorities are [priorities]. Use a two-column table covering time, cost, likely benefits, and downsides. End with the two questions I should answer before choosing.
What you get: A decision aid that makes your priorities explicit.
25. Check a factual claim
Check this claim: “[claim].” Find reliable sources, state what they actually support, and identify any date, definition, or context that changes the answer. If you cannot verify it, tell me what I should check myself.
What you get: A fact-checking path. Open and inspect the cited sources before repeating an important claim.
If a research answer sounds too neat: “Separate facts supported by the sources from your interpretation. Quote the relevant figures with their dates, and remove any claim you cannot substantiate.”
Personal & Life Organization
Daily-life prompts work best when they include the constraints that usually get left out: what is already in the fridge, who is eating, how much energy you have, and whether you actually want a complicated plan.
26. Plan simple meals
Plan three dinners for a family of four. One person is vegetarian, we have [ingredients] to use, and each dinner should take no more than [time]. Give me a menu, a combined grocery list, and any ingredient that needs a substitute.
What you get: A practical starting plan. Check recipes and dietary needs yourself if an allergy or medical requirement is involved.
27. Turn a recipe into a grocery list
Here is a recipe: [paste]. Extract the ingredients and quantities for [number] servings. Group them by grocery section. Put unclear quantities in a separate “check before shopping” list.
What you get: A list drawn from the recipe, with uncertainty left visible.
28. Write a recurring nudge
Write five short weekday reminders to help me start [habit]. Keep each under 20 words, make Monday practical rather than motivational, and vary the wording. Show me the messages before I decide whether to schedule them.
What you get: Reminder text. A prompt by itself does not create a standing notification.
29. Review a budget gap
My planned spending this week was [amounts by category]. Actual spending was [amounts]. Calculate the difference for each category and give me a plain-English summary. Do not recommend cutting a category until you ask whether the expense was unusual or necessary.
What you get: Arithmetic and a useful question, rather than a judgment about your spending.
30. Build a reading habit
I currently read [amount] and want to finish [book or goal] in four weeks. I have [time] available on [days]. Create a realistic weekly plan, a smaller fallback for busy days, and one way to restart after I miss a week.
What you get: A habit plan that can survive an imperfect week.
If the plan ignores real life: “I cannot cook on Tuesdays and I only shop once. Rearrange the dinners and adjust the grocery list without adding another trip.”
Learning & Skill-Building
AI can help you organize practice, explain a topic at different levels, and quiz you. It cannot tell from a fluent answer whether you have actually learned the material. Include a way to test yourself.
31. Make a learning roadmap
I want to learn [skill] from scratch over eight weeks, about 30 minutes a day. My starting point is [experience]. Build a weekly roadmap with one small deliverable per week. Tell me what to cut if I only have half the time.
What you get: A progression with visible milestones instead of “study a little every day.”
32. Ask for two levels of explanation
Explain [topic] twice: first for a complete beginner, then for someone who knows [basic concepts]. Keep the two versions separate. Add three questions I can use to check whether I understood the second one.
What you get: A simple entry point and a deeper pass.
33. Turn notes into flashcards
Here are my notes from [class or reading]: [paste]. Create ten flashcards covering the main terms and relationships. Use only these notes. Mark anything in the notes that is too unclear to turn into a reliable answer.
What you get: Study cards tied to your material, not invented textbook facts.
34. Run a short quiz
Quiz me on [topic] with eight questions: four multiple-choice and four short-answer. Ask one question at a time, wait for my response, then explain the answer. Focus the next questions on anything I miss.
What you get: An actual retrieval exercise rather than a page of questions with the answers immediately below.
35. Plan a practice habit
Help me practice [skill] for 20 minutes a day over three weeks. My schedule is [schedule]. Give me a short session structure, one weekly checkpoint, and a restart plan for a missed day. Avoid adding resources I have not said I can access.
What you get: A practice plan fitted to your available time.
If the study plan is too broad: “I have an exam in ten days, not eight weeks. Prioritize the topics I listed, reserve two days for review, and mark anything we cannot cover.”
Emotional Wellbeing & Self-Reflection
A personal assistant can help you put a thought into words, notice a pattern in what you have written, or prepare for a conversation. Keep it within that role. It should not diagnose you or replace someone qualified to support you.
36. Unpack a difficult day
I had a rough day because [brief context]. Ask me three questions, one at a time, to help me identify what bothered me most. After I answer, suggest one small action I could take tonight. Do not jump straight to a solution.
What you get: A little structure when an open-ended journal page feels like too much.
37. Start a gratitude check-in
Give me one specific gratitude question for tonight. Avoid “What are you grateful for?” Ask about a person, moment, or small detail from today. After I answer, summarize it in one sentence I can save myself.
What you get: A concrete journal entry. Saving or scheduling it depends on what the tool supports.
38. Prepare for a stressful event
I am anxious about [event]. Help me separate what I can prepare, what I can influence, and what I cannot control. Give me one action I can take in the next 15 minutes. Do not promise that the event will go well.
What you get: A practical split, not a pep talk.
39. Look for a pattern in a mood log
Here is my short mood log for the week: [paste]. Point out any pattern that appears in what I wrote and give me two questions worth asking myself. Do not diagnose me or claim a cause that the log cannot establish.
What you get: Observations you can accept, reject, or discuss with a person you trust.
40. Close out the week
Help me review this week. Ask me what went well, what drained me, and one thing I want to carry into next week. Ask only one question at a time. At the end, give me a three-sentence summary in my own words.
What you get: A short reflection you might actually finish.
If a situation feels too heavy for a journaling prompt, take it to a real person or an appropriate professional. An AI response can be supportive, but it does not know your full circumstances.
How to Improve a Weak AI Answer
A useful follow-up identifies the problem. “Try again” leaves the assistant to guess what failed. “You ignored my budget and invented a booking price” gives it a correction it can act on.
Use this revision prompt when the first answer is close but not usable:
This answer is not quite right. Keep [what worked]. Change [what was wrong]. Add [missing detail]. Remove [unwanted part]. Use only [specified source or inputs]. Return the revision as [format]. Before revising, list any assumption you need me to confirm.
For example:
This meal plan is too complicated for a working parent with 30 minutes in the evening. Keep the grocery list. Replace any recipe with more than six steps, use the ingredients I already listed, and put Tuesday’s dinner first because that is my busiest day.
That is a much stronger follow-up than “make it more practical.”
When you cannot immediately see why the answer feels off, ask the assistant:
“What did you assume that I did not tell you?”
“Which part of this answer relies on current information you have not checked?”
“Where might this plan fail on a busy day?”
“What would you need from me to make this more accurate?”
“Show a simpler version that takes half the time.”
Sometimes the right fix is a better prompt. Sometimes it is checking the source yourself. If the assistant has the wrong date or made up a policy, polished wording will not solve the problem.
Here is what the input–output–follow-up loop looks like in three common tasks. The outputs below describe what a good response should contain; they are examples of a workflow, not results from a product test.
Scheduling
Weak prompt:
Help me with my schedule.
Better prompt:
Plan my workday for tomorrow. I have meetings from 10–11 AM and 2–3 PM, need to finish a proposal, and want to leave by 5:30 PM. Build a timed agenda with one deep-work block, two short admin blocks, and a lunch break. Flag anything that does not fit.
Expected output: A proposed agenda with fixed meetings preserved, time for the proposal, and any conflict called out. It should not silently move a meeting.
Revision prompt:
Move the deep-work block earlier. Add 20 minutes of preparation before the 2 PM meeting. If that pushes an admin task past 5:30 PM, move the task to another day and tell me.
Email
Weak prompt:
Write an email to my boss.
Better prompt:
Draft a brief, polite email to my manager asking to move our Thursday 1:1 to Friday. Suggest 10 AM or 2 PM. Apologize for the change, but do not add a reason I have not given you. Do not send it.
Expected output: A draft with the request and two times, ready for review.
Revision prompt:
Make it slightly warmer, remove “I hope this finds you well,” and keep the explanation out. I will add the final meeting time myself.
Travel
Weak prompt:
Plan my trip.
Better prompt:
Draft a relaxed four-day Kyoto itinerary in April for two adults. We care about food, temples, and walkable neighborhoods. Avoid nightlife and more than two major stops a day. Give us morning and afternoon ideas, a dinner area, and anything whose hours or reservations we need to verify.
Expected output: A draft grouped by place and pace, with uncertainties clearly marked.
Revision prompt:
Add realistic travel time between neighborhoods. Replace one temple-heavy afternoon with a market and a cooking activity. Do not invent prices or availability.
The better prompts are not long for the sake of being long. They include the details the assistant would otherwise have to make up.
Turning One-Off Prompts into Reusable Macaron Routines
A prompt becomes more valuable when you can use it again without rebuilding the brief. Start by saving the wording that worked. Give it placeholders for the parts that change: [date], [tasks], [budget], or [notes].
For example, your weekly planning template might be:
Help me make a weekly game plan for [week]. Here are my fixed commitments: [events]. Here are my deadlines: [tasks]. Protect [amount] of time for [priority]. Return my three main priorities, a proposed schedule, and any conflict I need to decide. Do not change my calendar.
Every Monday, you can fill in the current information and run it again. That alone is a useful routine. It requires no special “Routine Builder” screen and makes no promise that the assistant will fetch your calendar automatically.
If your version of an assistant supports saved tools, connected accounts, or scheduled tasks, you can go further. But keep three steps separate:
Save the prompt. You can reuse it by pasting new inputs.
Connect a source. The assistant may be able to use a calendar, inbox, or task list if you grant the necessary access.
Authorize an action or schedule. A recurring briefing, reminder, sent email, or calendar edit requires a feature that supports it and the permissions you choose.
Consider a “Weekly Kickoff” request. With no connections, you paste your events and tasks and get a Monday brief. With a permitted calendar connection, the assistant may be able to read the relevant events. If you want the brief at a set time, you must confirm that scheduled tasks are supported in your account and set one up. If you want the assistant to move meetings, that is a separate permission and decision.
The same approach works for other repeat tasks:
A meeting-prep template that turns an agenda and notes into a one-page brief
An inbox-triage template that sorts pasted messages into reply, delegate, and archive
A travel template that asks for dates, budget, baggage, and pace before building an itinerary
A study template that turns new notes into questions and a review plan
A weekly meal template that starts with the food you already have
After two or three uses, inspect what keeps needing correction. Add that rule to the template. If your trip plans always assume an early start and you hate early mornings, write “do not schedule activities before 10 AM” into the saved prompt. That is a real improvement to the routine; claiming that an app learned a preference without checking its settings is not.
This is also where Macaron’s personal context can be useful. Its AI personal assistant is designed around recurring daily-life preferences and decisions. Still, ask the app what it remembers, correct anything outdated, and check which tools or account connections are available to you before expecting a saved request to run on its own.
Guardrails: Privacy, Approvals, and Audit Trails
The more personal context you give an assistant, the more important it becomes to know what it can access and do. A good guardrail is specific. “Be careful” is vague; “draft the email but do not send it” is testable.
Privacy first. Share the minimum information needed for the task. Redact unnecessary names and account details. Check the privacy policy of the tool you use, especially before connecting email, calendar, health information, or files. Macaron’s privacy policy describes what it collects, how connected-app information may be processed, and the role of third-party AI providers. Read the current policy rather than relying on a general claim that an AI app “keeps everything private.”
Separate proposals from actions. Asking for a meeting time is different from creating the event. Asking for an email draft is different from sending it. State the boundary in the prompt and inspect the final recipient, date, time zone, attachment, or amount before approving an action.
Check the source. For a current flight price, policy, medical claim, or legal rule, ask where the information came from and when it was checked. Then open the source. If the assistant cannot access current information, it should give you a plan for checking rather than a made-up answer.
Keep a record when it matters. For work tasks, save the original inputs, the draft, your corrections, and the final version somewhere your team already uses. Do not assume every AI product has an exportable action log. If a workflow requires an audit trail, confirm that your chosen product and account provide one before using it.
Review permissions. A connected calendar may allow reading, editing, or both. Grant only the access needed. Recheck the connection when your role changes or the task ends. NIST’s generative AI risk guidance is broader than personal-assistant prompts, but its emphasis on identifying and managing risks fits this practical habit: know the task, the data involved, and who remains responsible for the result.
Know when to handle it yourself. AI can help outline questions for a doctor, summarize a contract for your own understanding, or draft a difficult message. It should not be the final authority for a diagnosis, legal judgment, financial decision, hiring decision, or emotionally consequential conversation. Use the draft to prepare; let the appropriate person make the final call.
A personal assistant is most useful when you can trust the process: you know what information went in, what the output is based on, and which actions still require you.
Conclusion & Next Steps
You do not need to start with all 40 prompts. Choose one task you already do every week. Give the assistant the relevant inputs, say what output you need, and correct the first answer. Save the version that worked.
A good first experiment might be tomorrow’s agenda, a draft reply you have been avoiding, or a meal plan built around what is already in your fridge. Notice where the assistant helped and where you still had to supply a missing fact. Put that fact into your next prompt.
That is how to use AI as a personal assistant in a way that holds up beyond the first impressive answer: brief it clearly, inspect what it returns, and keep the decisions that matter in your hands.
Frequently Asked Questions
How long should an AI personal assistant prompt be?
As long as the task needs, and no longer. A short request can work when the assistant already has the right context. For a new or sensitive task, include the goal, relevant inputs, constraints, desired output, and whether it may act. “Draft a PTO request for next Friday; mention that the team has coverage; keep it under 100 words; do not send it” is more useful than a paragraph of general instructions.
What if the assistant gives an incorrect or strange answer?
Identify the error and its source. Did it use the wrong date? Miss a constraint? Assume access to a calendar it cannot see? Give it a precise correction: “You scheduled work after 5 PM. Keep that boundary, move the low-priority task, and show the revised plan.” For factual claims, check the cited source yourself. If the answer keeps failing, narrow the task or complete the critical part manually.
Can an AI personal assistant actually send emails or book meetings?
Only if the product supports that action, you have connected the relevant account, and the permissions allow it. A chat response that says “I’ll book it” is not proof that an event was created. Ask the assistant to show what it did, then check the calendar or sent-mail folder. For important actions, review the details before confirming.
Should I save one master prompt or separate prompts for different tasks?
Keep a short set of stable preferences, then use task-specific prompts. Your writing tone may carry across email requests; your travel budget should not automatically shape a birthday gift recommendation. Separate templates also make errors easier to find and fix.
When should I escalate a task to a person?
When the decision needs professional judgment, private information you should not share, or emotional understanding that a draft cannot provide. An assistant can help you prepare questions, organize facts, and draft wording. A lawyer, clinician, manager, friend, or you should make the consequential decision.
Nora is the Head of Growth at Macaron. Over the past two years, she has focused on AI product growth, successfully leading multiple products from 0 to 1. She possesses extensive experience in growth strategies.
