Claude ը քո անձնական կյանքում

Using my connected Gmail, search the last six months for receipts, invoices and renewal notices, and include these providers I already know about: [names]. Build one table of every recurring charge: service, amount in [currency], billing cycle, yearly cost, date of the last charge, and a verdict column with keep, review or cancel. Sort by yearly cost, highest first. Under the table, total the yearly spend, then name the three cancellations that would save the most. Tell me which services you could not confirm from email alone so I can check those manually.

Here is my bank export: [attach CSV]. Categorise every transaction into no more than sixteen categories, using my own labels where I give them: [any categories you already use]. Return three things: a category table with total, share of spend and number of transactions, a top fifteen vendor list by amount, and a short paragraph on what changed compared to the earlier months in the file. Then pick one category to attack this month with a realistic target. Flag any transaction you could not classify confidently.

Build a cash flow calendar for [month] as a single HTML artifact. My income: [amounts and dates]. My fixed bills: [name, amount, day of month]. Variable spending I expect: [items]. Starting balance: [amount]. Show a month grid where each day carries the money in, the money out and the running balance, with any day below [threshold] highlighted. Underneath, name the tightest day and suggest one payment to move, with the new balance if I move it. Show the running balance calculation.

Make me a net worth tracker as one HTML artifact I can save and reopen. Categories for assets: [cash, savings, investments, property, other]. Categories for debts: [loans, cards, other]. Let me add a dated snapshot each month, keep all previous snapshots, and show three things: current net worth, a breakdown by category with percentages, and the change from the previous month in both money and percent. Currency is [currency]. Keep the data in the file itself and tell me plainly how to back it up.

Build a Skill called weekly money pulse. Each time I run it I will give you [this week's transactions] and it already knows [my fixed bills with dates], [my savings target and deadline]. Output the same four blocks every time: spend by category against last week, bills due in the next fourteen days with dates, savings pace as ahead or behind with the number, and exactly one decision for me to make this week. Keep it under one screen and never give me more than one decision.

I am thinking about buying [item] for [price]. My reason: [why I want it]. My situation: [income, space, how I live]. Run a pre mortem: assume it is twelve months later and I regret this purchase. Write the month by month story of how that happened, including running costs, maintenance, and the moment I stopped using it. Then give me the three conditions under which this purchase is actually right for me. Be specific to my situation, no generic advice about wants versus needs.

Write me a phone script to lower this bill. Provider: [name]. Service: [what I pay for]. Current price: [amount] and I have been a customer for [time]. Competitor prices I know of: [any]. Write it as a dialogue with my exact lines, then their three most likely responses and my reply to each. Include the sentence to use when they say no, and the line that gets me to the retention or cancellation team. Keep it polite and short. Tell me which claims I must verify before I call.

Here are my debts: [name, balance, interest rate, minimum payment] for each. I can put [amount] per month toward debt in total. Compare avalanche and snowball. For each method give me a table by month showing which debt gets the extra payment, remaining balances, and the month each debt clears. Then compare the two on total interest paid and final debt free month. Show the interest calculation for the first three months so I can check it. Say plainly which one you would choose for me and why.

I want to buy [item or category], roughly [budget], in [country or city]. Tell me the time of year prices for this category typically fall and why, the target price I should hold out for, and how far from list price that is. Give me the three negotiation angles that work for this specific category, ranked, with the sentence to use for each. Then tell me the signals that mean I should buy now instead of waiting. Mark clearly where your pricing knowledge may be out of date.

Set this to run on the first of every month. Act as my monthly money reviewer. Each run, ask me for last month's numbers: [income, spend by category, savings, debt balances]. Then produce four sections: what changed versus the month before with numbers, the one thing worth worrying about, three moves labelled small, medium and large with the effort and the effect of each, and one question to answer before next month. Keep it to one page. No generic budgeting advice.

You are my personal dashboard designer. Build me a single page HTML dashboard for my life. I will give you: [my sleep and recovery numbers for the last 7 days], [my calendar for today], [my city], [my one focus for today], [money that came in this week]. Output one artifact with five clear cards, large numbers, and under each card one plain sentence telling me what it means for today. Before you build it, ask me what I actually check first in the morning.

Set this up as a scheduled task that runs every weekday at 7:00 in [my timezone]. Each morning read my calendar and my inbox and write me a brief in three parts: my schedule with the two events that need preparation marked, the messages waiting on a reply from me ranked by who is blocked, and one task to start with plus its first physical step. Keep it under 200 words. If my day looks unusually heavy, say so and tell me what to move.

You are running my Sunday reset. Take me through six blocks of ten minutes each: review of last week, calendar cleanup, money check, food plan, one home task, and three priorities for next week. Ask me the questions for one block at a time, wait for my answer, then summarise that block in three lines before moving on. My context: [my job], [who lives with me], [what fell apart last week]. At the end, output the whole week as a checklist I can paste into my notes.

Act as my energy analyst. I will paste last week from my calendar plus a note on how I felt after each block: [my week]. Score every block from minus two to plus two for energy, then give me a table with block, score, and the likely reason. After the table, name the three specific changes I should make to next week's calendar, each with the exact day and time. Do not give general advice about rest. If two blocks look the same but scored differently, tell me and ask why.

You are my thinking partner for a brain dump. I am going to write everything on my mind in one messy block: [my dump]. Sort every line into one of four columns: project, next action, decision I owe someone, or noise to delete. Give me the table, then pick the three items that matter most this week and say in one line each why. Finish with the single thing I am avoiding. If something is too vague to sort, ask me one question about it instead of guessing.

Build me a Claude skill called task starter. When I name a task I have been avoiding, it asks three quick questions: what the task is, where it physically happens, and what I would touch first. Then it gives me exactly one action that takes under two minutes and waits for me to say done before giving the next. It never lists more than one step and never talks about motivation. My context: [the kind of tasks I avoid] and [what I usually do instead]. Save it as a skill I can call by name. Ask me anything you need before writing it.

Build me a habit tracker as a single artifact. My habits: [list them]. For each habit show a checkbox for today, the current streak, the best streak I have ever had, and a thirty day heatmap of squares. Under the grid show my completion rate for the week per habit. Keep the state inside the artifact so my ticks survive when I reopen it, and tell me plainly if that is not possible. Use one accent colour and nothing else. Ask me how many habits before you design the layout.

Build me a goal dashboard as one artifact. My goals with their weekly target: [goal and number for each]. For every goal show the target, what I logged each week, the percentage done, and a status light. Add a rule that marks a goal as slipping when I miss the weekly target two weeks in a row, and put those goals at the top with the week the slide began. Include a field where I paste this week's numbers. Show the formula you use for the percentage.

Use my connected Google Calendar. Read every event from [start date] to [end date] and sort them into these categories: [my categories]. Give me a table of total hours and percentage per category, then the same table split by quarter so I can see what changed. List the five recurring meetings that took the most hours in the year. Finish with the three hours per week I could get back and where exactly. If an event title is unclear, put it in a separate row and ask me.

Create a skill called focus guard. At the start of a session I tell it: [the task] and [how long I committed to it]. If I come back with anything other than that task, it asks me three questions in order: does this have to happen today, will it still be there tomorrow, and am I avoiding the task I chose. Unless all three point to a real emergency, it adds the new thing to a parking list and tells me to go back. At the end it shows the parking list.

Create a skill that writes my workout for today. Every time I run it I give: [hours slept], [resting heart rate], [HRV], [soreness out of ten], [minutes free today], [equipment I have]. It returns one session with exercises, sets, reps and rest, plus the total minutes, and one line explaining what it changed because of my numbers. My training goal is [goal]. If my recovery numbers are clearly bad, it must reduce the load and say so rather than motivate me.

Build a workout tracker artifact for today's session. Today's exercises: [list]. Last week's numbers: [weight, reps and sets per exercise]. For each exercise show last week's numbers in grey, input boxes for today, and a suggested next set that adds a small amount when I hit the target reps and holds when I miss. Show total volume for today against last week at the bottom. Show the progression rule you used in one line so I can check it.

I am in a gym I do not know. Here are photos of everything in the room: [attach photos]. My normal session for today is: [exercises, sets, reps, weights]. First list what equipment you can actually see in the photos, then rebuild my session with only that, keeping the same muscle groups and roughly the same effort. Give me a table with three columns: original exercise, substitute, why. If you cannot identify a machine, say so instead of assuming, and give me a bodyweight fallback.

Build me a nutrition tracker artifact. My daily targets: [calories, protein, carbs, fat]. I will paste photos of my meals through the day: [photos]. For each photo estimate the portion and the macros, add it to a running total, and show the remaining macros both as numbers and as two or three real foods that would fill the gap, using foods I actually eat: [foods I like]. Show a confidence level for every photo estimate and ask me the weight when a photo is genuinely ambiguous.

Create a skill that keeps my personal health record in one file. Sections: medications with dose and start date, allergies, diagnoses, lab results by date, procedures, and a dated symptom log. When I paste anything, a lab PDF, a doctor's note, or a sentence about how I feel, it files the item in the right section, dates it, and tells me in one line what it added. It must never delete an old entry, only add. Start from what I give now: [my medications], [my allergies], [my diagnoses]. Ask me for anything missing before you write the file.

Create a skill that prepares me for a medical appointment. Input: [type of doctor], [date of my last visit], [what has happened since], [my current medications], [my questions]. Output one page under 400 words with four blocks: what changed since the last visit in date order, current medications and doses, symptoms with when they started and how often, and my questions ranked so the ones only this doctor can answer come first. Plain language, no diagnosis. Flag anything I wrote that a doctor would need more detail on.

Here are my blood test results from [dates], newest first: [paste or attach them]. Build a table with one row per marker: the value each time, the reference range, the direction across draws, and one plain sentence on what the movement suggests. Then list only the markers worth raising with a doctor and what I should ask about each. You are not diagnosing me. Where a marker is inside the range but has moved sharply, say so, and mark anything you are unsure about.

Create a skill that produces a sleep correlation report. I give it: [nightly sleep score and duration], [time of my last coffee each day], [time and type of training], [alcohol and when], [bedtime]. It groups the nights by each factor and shows average sleep quality per group, with the number of nights behind every average. It then names the two factors with the clearest effect and my personal cutoff time for each. Say plainly when a sample is too small to trust.

Create a skill I run in the evening. It asks me four things: my first commitment tomorrow and where it is, how demanding today was out of ten, whether I trained and when, and what caffeine I had after midday. It returns a target bedtime, a window of twenty minutes around it, how long before that I need to wind down, and the two specific things to stop. My fixed inputs: [my normal wake time] and [how long I take to fall asleep]. Show the arithmetic from my morning time backwards so I can see how you got there.

Set up a scheduled task that runs every day at 7:00. My last period started on [date] and my average cycle is [number] days. Each morning work out the phase I am in and send me a short brief: the training that suits this phase with a specific session, two foods to add today, how much focus work to plan, and one sentence on what to expect from my energy. Keep it under 150 words. When my cycle is irregular, say your estimate may be off and ask me to confirm.

You are a practical home cook. I will upload photos of my fridge, freezer and shelves: [photos]. My household is [number of people], tonight I have [minutes] and my constraints are [allergies, diet, what I hate]. Read only what you can actually see in the photos. Give me three dinner options as a table with columns: dish, time, ingredients I already have, ingredients I am missing. Under the table, write one short shopping list covering all three. If you cannot identify an item clearly, say so instead of guessing.

Act as a meal planning system I can reuse every week. Build me a Skill that takes: [who eats, how many servings], [dishes we already love], [nights we will not cook], [budget or store]. Output every week in the same shape: a seven day table of dinners, then a grocery list grouped by store section, with quantities scaled to my serving count. Reuse ingredients across meals so nothing is bought twice. Before you write the Skill, ask me the five questions you need answered to make it fit my kitchen.

You are the editor of my personal cookbook. I will add screenshots, links and photos of handwritten recipes to this Project over time. Rewrite each one into one fixed format: title, servings, total time, ingredients with metric quantities, numbered steps, and a notes line. Apply my standing substitutions: [list them, for example butter to oil, no cilantro]. Keep the original wording where it carries flavour, cut the life story above the recipe. When a source is unclear or a quantity is missing, mark it clearly rather than filling in a plausible number.

Work as my kitchen production planner. Here is what I plan to eat this week: [meals]. My kitchen has [one oven with N shelves, N burners, these pots]. I have [hours] on Sunday. Find every component across those meals that can be cooked ahead, group them by oven temperature and by pan, and give me a single timeline in fifteen minute blocks: what goes in, what comes out, what I do while waiting. End with how each component should be stored and how many days it keeps. Show your reasoning on the oven order.

Build me an interactive meal planner as a single self contained HTML artifact. Load it with these recipes: [paste recipes with base servings and ingredient quantities]. The page shows seven day slots I can assign recipes to, a servings input per meal, and a combined grocery list underneath grouped by store section. Changing servings anywhere must rescale that recipe and the grocery list instantly. Make it readable on a phone, with large tap targets. Ask me how I want fractional quantities rounded before you build it.

You are with me at a restaurant. Here is a photo of the menu: [photo]. My situation: [goal, for example high protein, low sugar], [allergies], [what I already ate today]. Read only the dishes on this menu. Give me a short ranked list: top three picks with a one line reason each, then two dishes to avoid and why. For each pick, write the exact sentence I can say to the waiter to adjust it. If a dish description is too vague to judge, say what you would ask the waiter.

It is six in the evening and I have to decide dinner now. I have [minutes], my energy is [low, medium, high], and these things need using up: [items]. In the kitchen I also have [staples]. Give me exactly three options, ranked, in a table: dish, minutes, pans to wash, what it uses up, effort out of five. Mark one as the recommendation and write one sentence on why it wins tonight. No dishes that need an ingredient I did not list.

Think like a cook who hates waste. In my fridge I have these leftovers: [item, roughly how much, how many days old]. Pantry staples available: [list]. Design one new meal that uses as much of this as possible and does not taste like reheated leftovers. Give me: the dish, what goes in and what stays out, the steps in order, and the one addition that makes it taste new. Then tell me honestly which items I should throw away instead of eating, and why.

Build me a Skill that tracks my kitchen inventory. It should accept two kinds of input from me: a photo of shopping I just brought home, or a line like [three eggs used, bought 400g yoghurt]. Keep one table with item, quantity, location, date in, and estimated days left. Whenever I ask, return the five things to use first and two dishes that would clear them. Store estimates conservatively and mark any shelf life you are guessing at rather than stating it as fact.

Here is a recipe: [paste it]. It serves [N] and I need it for [M]. I do not have: [missing ingredients]. I do have: [what is in the kitchen]. Rewrite the recipe at the new size with every quantity recalculated, and replace each missing ingredient with a substitute plus the exact ratio to use. Then list separately anything that does not scale linearly, such as pan size, cooking time, salt and leavening, with the corrected value. Show the arithmetic for the three biggest quantities.

You are a recruiter who writes LinkedIn profiles. I will give you [ten postings for the role I want] and [my current profile text]. First pull the words and phrases those postings repeat, then rewrite three things: five headline options under 220 characters, one about section of 120 words in first person, and every role bullet with the result first. Show a table matching each rewrite to the posting term it covers. Keep every number and job title exactly as I gave it, and tell me which claims I still cannot back up.

In this project you plan my LinkedIn month. Files I will add: [notes on the work I finished this quarter], [numbers I am allowed to share publicly], [the three people I want reading me]. Produce a table of twelve posts across thirty days: date, format, working title, opening line, the file it came from, and the ask at the end. Vary the format, never repeat one twice in a row, and invent no result I did not give you. Before the table, ask me which week I am busiest so the light posts land there.

In this skill you turn one finished piece of work into a LinkedIn post. I will tell you [what the work was], [who it was for], [what was hard] and [the number it moved]. If I do not give the number, ask for it and write nothing until I do. Return four parts: the problem in one sentence, what I did, the number and what it means, and one line a reader can use in their own work tomorrow. Keep it under 150 words, no hashtags. Then offer two other opening lines.

Build my job search command center as one artifact. For each application I will give [company, role, date applied, stage, contact person, last touch date]. Show a board with columns applied, screening, interview, offer and closed, plus an overdue follow ups panel and a stalled section for anything with no movement in fourteen days. Add a weekly counter of applications sent. Tell me what my numbers say about where I am losing people, and do not soften it.

You are a recruiter who screens for [role]. Here is [the full job posting] and [my current resume]. Rewrite my experience so each bullet answers something the posting asks for, keeping every fact and number exactly as I gave it, and cut whatever is irrelevant to this role. Return the tailored resume, a short list of what you removed and why, and a cover letter under two hundred words. Flag any requirement I genuinely do not meet instead of covering it with vague wording.

You are my researcher before an interview. Company [name and website], role [title], the person interviewing me [name and title], date [when]. Search public sources and give me one page: what they sell and to whom, how they make money, three things that changed for them in the last year, what my interviewer works on, and five questions I could ask. Put a link and a date next to every fact. Whatever you could not verify, mark unverified rather than filling it in.

You write my first message to a stranger. Here is [their profile or a post of theirs], [who I am in one sentence] and [what I want from them]. Give three versions, each under 60 words: the opening line names something specific they did, one sentence about me, and one ask that is easy to say yes to. Then write the one follow up to send after a week of silence. Cut any sentence that would work just as well sent to somebody else.

You keep my career receipts. My role is [my role and level] and the skills I need to prove are [skills that matter for my next step]. When I state a win in one line, ask only the questions needed to fill date, what I did, the measurable result, the skill it proves and who noticed, then store it as one row. Never let a row sit without a number or a named witness. When I ask, output review notes grouped by competency or resume bullets in strong verb form, and tell me which months look suspiciously empty.

Prepare me for a raise conversation. Inputs: [my role, level, city], [current pay], [my logged wins and numbers], [what my manager cares about], [how they usually push back]. First give me my case on one page: the number to ask for with the market range behind it, three proof points, and my opening two sentences. Then play my manager and push back hard three times, including on budget. After that, tell me which of my answers were weak.

You are advising me on my first 90 days as [role] at [what the company does]. My team is [who does what], my manager said success looks like [what they said], and I am most worried about [what]. Ask me two questions about the team before you write anything. Then give three blocks, day 30, day 60 and day 90, each with what I should understand by then, who to meet and the question to ask them, and one visible thing I ship. End with the mistake new people make here in month one.

You are my trip planner. Trip: [city or region], [dates], [who is going], [budget per day], [what we like and hate], [pace]. Write a day by day itinerary with times, named places to eat and stay, entry costs, and how we get between each stop. Keep each day inside one area so we are not crossing the city twice. Mark anything whose price or opening hours you are unsure about so I can verify it before booking.

Build me a single page trip dashboard as an artifact. Trip data: [destination], [dates], [travellers], [total budget], [flights and hotels already booked], [what we plan to do]. The page needs four parts: a card per day with plan and cost, a budget bar showing spent against total, a packing checklist grouped by category with tick boxes, and a reservations table sorted by date with confirmation numbers. Make it readable on a phone screen first, desktop second.

Compare travel options for me. I will paste [three flight options] and [three hotel options] with their prices, times and terms, plus my [loyalty programmes] and [trip dates]. Build two tables, one per category, with columns for total real cost including bags and transfers, time door to door, points earned, cancellation and change rules, and one line on who each option suits. End with your pick and the single reason for it. Show the arithmetic on the totals.

Be my packing planner. Trip: [destination], [dates], [who is travelling and their ages], [bags we have], [activities planned], and here is the forecast I copied: [paste]. Give me one list per person, split into hand luggage, checked bag and worn on the plane, with quantities based on the forecast and laundry access. Add a short section of things people forget for this kind of trip. Do not pad the list, cut anything we would not wear twice.

Using my Gmail and Google Calendar, find every booking confirmation for [trip name or dates]: flights, hotels, trains, restaurants, tickets. List what you found in a table with date, time, provider, confirmation number and address, then ask me which ones to add to my calendar. Create each approved one as an event in the local time of the place, with the confirmation number and address in the notes. Do not create anything before I confirm the list.

Act as our two style trip planner. Person A: [name, what a good day looks like, energy level, must do]. Person B: [same]. Trip: [place], [dates], [budget]. Give a day by day plan where each day is labelled A day, B day or shared day, never blended, with the other person's small win inside every day. Add one table of the negotiations you made. Ask each of us three questions first, separately, before you plan anything.

Plan my jet lag shift. Flight: [departure city and time], [arrival city and time], [time zone difference], [when I normally sleep], [what I need to do on arrival day], [do I drink coffee]. Give me a schedule table starting three days before the flight and ending three days after, with rows for light, caffeine, meals, naps and bedtime for each day, in local time with the zone named. Tell me the one rule that matters most for my direction of travel.

This project holds my travel history for [me and who I usually travel with]. After each trip, ask me the debrief questions: what I would repeat, what I would cut, where the money went well and badly, what I packed and never used, how the pace felt, what I wish I had booked earlier. Save the answers as one page per trip, named [destination and month]. When I plan a new trip, open with what my own past trips say about how I travel, quoting them by name.

Plan my layover. Details: [airport], [arrival and departure times], [passport I hold], [whether my bags are checked through], [have I been to this city]. Work out my real free time after immigration, transport both ways and a ninety minute return buffer, then give me two options: one that leaves the airport and one that does not, each as a timed plan with costs. Show the time arithmetic so I can see the buffer.

Write me a country brief for [country or city], for a trip of [length] as [who I am travelling as], staying in [area]. Cover: twenty phrases with pronunciation written for an Armenian speaker, tipping and haggling norms, how to pay and get around, three things visitors do that annoy locals, what to wear, safety notes and one local custom worth joining. Keep it to one page and mark anything that varies by region.

You are our family logistics coordinator. I will paste the coming week: [family members and ages], [school and activity times], [work hours per parent], [who drives what]. Return one table with a row per day and columns for time, event, person, driver and a conflict flag. Below it list every impossible overlap and assign a named parent to each unowned pickup. Ask me what you need about travel times before you assign anything.

You are setting up our family knowledge base. Ask me about one member at a time: [name and age], [allergies and medication], [sizes], [school and teachers], [doctor and clinic], [daily routine], [what calms them]. Turn each answer into a one page profile with fixed headings so every profile looks identical, then finish with a shared household page for wifi, addresses and emergency contacts. Do not fill any field by guessing, mark what I skipped as unknown.

Act as a neutral household task auditor for two adults. From [our schedules], [who currently does what], [children and pets], [any task one of us refuses], build a fourteen day table: task, hidden or visible, minutes, owner, day. Balance the totals within ten percent between us and rotate the three most disliked chores each week. Show minute totals per person at the bottom, and name any task I forgot that a household like ours always has.

You are my gift and occasions manager, running every Monday. My list is [names, dates, relationship], my budgets are [amount per tier], my style is [how I normally write messages]. Show only people with a date in the next fourteen days: a short block each with three gift options at different prices, why each fits them, where to buy locally, and a ready to send message in my voice. If you do not know enough about someone, ask instead of guessing.

You keep my gift history. Start a file per person from [name], [past gifts with year and rough cost], [how each landed], [their interests now]. Format every entry as one line: year, gift, cost, reaction, notes. When I later say I need a gift for someone, read their file first and give five ideas that avoid every category I already used, with a one line reason each. Tell me honestly when a file is too thin to be useful.

Build me a single page stay in touch tracker as an artifact. Data I will give: [names], [how we know each other], [how often I want to talk to each], [date of last contact]. The page should compute how overdue each person is, show the three most overdue at the top with a suggested opening line, and list everyone else below. Keep it usable on a phone, and tell me which of my intended frequencies look unrealistic.

Act as the builder of my personal CRM and produce it as one interactive artifact. I will provide [people], [how we met], [tier such as inner circle, warm, professional], [last conversation topic], [anything I promised them]. Output a filterable dashboard grouped by tier, a card per person, and an overdue promises section at the top. Include a box where I can paste a new note and see where it belongs. Ask me for missing fields before building, do not invent details.

You are planning our date night using my calendar and current traffic. Inputs: [our city and neighbourhood], [cuisines we like and hate], [budget per person], [babysitter window if any]. Find a free evening this week, then give three restaurants with booking link, price level and why it fits us, the departure time from [home address] based on live travel time, and one walkable backup near the top pick. Say clearly which details you could not verify live rather than assuming.

Play the other person in a conversation I am dreading. They are [who they are to me], they usually react by [their pattern], the history is [what happened before], and I need to say [the thing I am avoiding]. Stay in character and respond exactly as they would, including going quiet or turning it back on me. After four exchanges, break character and tell me which of my sentences made it worse, with better wording for each.

You manage my pets' health records. Set up from [animal, breed, age, weight], [vaccine history with dates], [current medication and refill dates], [food brand and daily amount]. Keep a dashboard with the next three due items first. When I add a symptom note, ask the follow up questions a vet would ask, store it, then rewrite the last thirty days into a dated summary I can read out at the clinic. Never suggest a diagnosis or a dose, only what to report.

You are my [target language] tutor and my level is [my level]. Each session: run a roleplay from [situations I actually need], correct every line I write with the original, the fix and a one line reason, then add new words to a running vocabulary file with my own example sentence. Start each session by testing me on five words from that file. Correct everything, including what I got almost right, and do not switch to my own language unless I ask.

We are doing spoken practice in [target language] at [my level]. I will speak, you reply in that language at a speed I can follow, and stay inside the scenario [situation I need it for]. Every three turns, pause and give me a short correction block: what I said, what a native speaker would say, and one sound or word ending I keep getting wrong in the transcript. Keep your own replies under four sentences so I do most of the talking.

In this skill you are a Socratic tutor for [subject]. My level is [what I already know] and my goal is [what I need to understand]. Never state the answer, even if I ask directly or say I give up. Give one question at a time that moves me forward, and confirm only when I say the correct thing myself. If I stall twice on the same step, narrow the question instead of solving it, and finish by asking me to explain it all back.

Teach me [concept]. My level is [what I already know] and I need it for [why]. First explain it [in plain words, or the way you would explain to an engineer, or with the maths], under 300 words, with one example from [my field]. Then ask me five questions, one at a time, easy to hard, and wait for my answer. When I miss one, explain only the part I missed in a different way and ask a new question on that same part. At the end name what I still do not understand.

You are my spaced repetition partner. I will add items as [question] and [answer], starting with [what I keep forgetting]. Keep one table: item, the last date I got it right, current interval in days, next due date. When I say run a round, ask only the items due today, one at a time, and wait for my answer. Double the interval when I get it right, set it back to one day when I do not. Never show the answer before I try, and at the end tell me the three items I keep failing.

You are a hiring market analyst. Find fifteen live postings for [role] in [location or remote], then build one table: skill, how many of the fifteen required it, my status as have, partial or gap based on [my experience], and the evidence I could show. Sort by frequency. Finish with a study plan covering only the gaps in the top ten, with what to build as proof for each. Link the postings you used and flag any skill that appeared in fewer than three.

I will paste [the list of courses, tutorials and videos I saved] and [the one goal I want to reach in six months]. Sort every item into keep, later or kill. In keep put at most four, in the order I should do them, each with what I will be able to do afterwards. Next to everything else write one sentence saying why it does not serve this goal. If two teach the same thing, kill the longer one and say so. Do not go easy on me.

In this project you prepare me for [exam or certification]. The date is [when]. I will add [the official topic list], [what I already know well] and [hours I can study each week]. Build a plan from today to that date, week by week, with topics, what to practise and one checkpoint. When I ask for a mock, write a full test in the real format and question count, score it, and give a percentage plus the topics that would fail me. Weight the plan towards my weakest topics, and say plainly if the date is not realistic.

Act as my reading editor and produce a ranked artifact. Inputs: [my saved links with titles], [my two goals this quarter], [how much reading time I really have per week]. Score every item one to five for relevance to those goals, output a sorted table with score, reason and estimated reading time, then name the three for this week and mark everything under three as delete. Be blunt about items I saved for identity reasons rather than usefulness.

I will paste my highlights from [book title] by [author]. Do not summarise the book. Based on [what my life and work look like now], give exactly three changes I could actually make, each with the highlight it came from, the first small step, the day to start, and what I would drop to make room. Then name the one highlight that sounds wise but would change nothing for me, and say why.

You are my daily check in tracker. Every time I write to you I will give you [energy 1 to 10], [mood in one word], [hours slept] and [one line about the day]. Append it to a file called checkin.md as a table row, then reply with a two line confirmation and nothing else. Every seventh entry, compare the last seven days against the previous seven and tell me which number moved most and what my own lines suggest caused it. Do not give me wellness advice I did not ask for.

Build me a single file HTML journal I can open in my browser. Each entry takes a date, a free text note, a mood score and an energy score, both 1 to 10, and saves to local storage so nothing leaves my computer. Show a line chart of mood and energy over time and a heatmap of the current month coloured by mood. Once there are fourteen entries, show a panel that names two patterns you can actually see in my data. Ask me about styling before you write any code.

You are helping me prepare for a therapy session. I will paste [my check in entries or journal notes from the last few weeks] and tell you [what my therapist and I worked on last time]. Give me at most five talking points, ranked by how often the theme appears, each with the dates and the exact quotes from my own writing that support it. Add one question I seem to be avoiding. Do not interpret or diagnose anything, only show me what I wrote.

You are helping me make a decision with a weighted matrix. The options are [option A, option B, option C] and the decision is [describe the decision]. Ask me questions until you have five to seven criteria and a weight for each. Then build a single HTML page with sliders for the weights, a score table showing the weighted math inside each cell, and a total row. Under the table, name the one criterion that would flip the winner if its weight changed, and say by how much. Do not invent criteria for me, keep asking until I answer.

Play devil's advocate against my plan. The plan is [describe the plan in five sentences] and my situation is [budget, time, who else is involved]. Give me your five strongest objections, ordered from most to least serious, each in three sentences and each tied to something specific I told you. Then break character and tell me which one objection actually survives if I think it through, and which ones are just noise. No general life or business advice, only objections to this plan.

Run my question through a council of five advisors. The question is [your question] and the context is [what you have tried, your constraints, what you are afraid of]. Step one, answer as each advisor separately: an optimist, a sceptic, an operator who has done this, someone thinking only about money, and someone who knows me well. Step two, show each advisor critiquing the other four anonymously. Step three, give one verdict of at most one page, including the point where they disagreed most. Flag anything you are guessing about.

I got a message I cannot read properly. Here it is: [paste the exact message]. Context: [who sent it, our relationship, what happened before]. Give me three readings of it, a hostile one, a neutral one and a warm one, and for each quote the exact words that support it. Then say which reading the evidence actually favours and how confident you are. Finish with three replies I could send, short, medium and direct. Do not soften the hostile reading if the words support it.

Ask me ten questions about what I want my life to look like in three years, one at a time, and wait for each answer. Then write one page describing a single ordinary Tuesday in that life, in the present tense, with concrete sensory detail: where I wake up, what the room sounds like, who I talk to, what I do before noon. Use only what I told you, invent nothing. End with the one change I would have to make in the next ninety days for this to be plausible, and what it costs.

Build me a decision archive as a single HTML page that saves to local storage. Each record holds: date, the decision in one line, the options I considered, my criteria with weights, the option I chose, what I expect to happen, my confidence from 1 to 10, and a review date. The main view lists open decisions and flags any whose review date has passed. When I open a past decision, show my original expectation first and ask me what actually happened before showing anything else.

You are reviewing my quarter using only the files in this project: my goals, my habit log, my spending export and my journal. Produce a report with one section per goal containing: what I wrote at the start of the quarter, what the data shows I actually did, the gap as a number or a percentage, and one sentence on why. Then list the three habits with the widest gap and the one goal I should drop. Quote the file and the date for every claim you make.

Interview me so you can write a file called aboutme.md. Ask me about: how I make decisions, how I like information presented, my work and who it serves, what I am trying to do this year, my hard limits, and the advice I am tired of hearing. Ask in batches of three questions and wait for my answers. Then write the file in under four hundred words, in the second person, as instructions to a future Claude. Tell me which sections you had to guess at.

Every Sunday at 10:00, clean my Downloads folder at [path to your Downloads folder]. Sort files into subfolders by type: Documents, Images, Installers, Archives, Other. Move anything untouched for more than sixty days into Archive/[year month]. List files with the same name, or the same size and extension, as likely duplicates, but do not delete them. Print the full plan as a table of source and destination first, wait for my approval, then execute. If a filename looks personally important, leave it where it is and tell me why.

You are my second brain over the notes folder at [path to your notes folder]. When I ask a question, search every file, answer in at most five sentences, and cite the filename and the exact line you used. When I say save this, write a new markdown file in that folder using my existing naming style and add links to the two most related notes. When I ask what am I missing, name topics I write about often but never connected. If the folder does not answer the question, say so instead of guessing.

Every weekday at 08:00, read the email that arrived in my inbox since yesterday morning. Sort every message into exactly one of: urgent, needs a reply, read later, delete. Give me a table with sender, subject, category and one line saying why. Then write draft replies for the three most important messages in the needs a reply group, matching how I usually write. Save them as drafts, do not send anything. If a message could be a scam or a payment request, put it at the top and say what looks wrong.

You check suspicious messages for me. I will paste [the full message including the sender address and any links] and tell you [what I already clicked or replied, if anything]. Give a verdict of safe, suspicious or scam with a confidence percentage. Then list every red flag you can point to in the actual text, quoting it, and separately list what would be normal for a real message from that organisation. End with numbered steps for what to do in the next hour. Never open or visit a link, judge it from the text alone.

In this project I have a file listing my clothes with colour, warmth and formality. Each morning, read that file, get today's forecast for [your city], look at my calendar, and name one outfit using the exact item names from the file. Give the outfit, one alternative, and the layer I should take if I will be out after dark. Say in one line why this works for today's coldest hour and my most formal meeting. Do not assume everything is clean, ask me first.

I want to buy [item and price] because [the reason I think I need it]. Check it against my inventory file first, find the closest thing I already own, and ask me what that item fails to do. Then give a verdict of buy, wait or skip, with the cost per use if I use it [how often I realistically expect to use it]. If the verdict is skip, give the cheaper way to solve the same problem with what I have. Do not be encouraging, I want the version that argues against me.

I am researching [product category] with a budget of [amount]. Before recommending anything, ask me five questions about how I will actually use it and where I have been disappointed before. Turn my answers into five weighted criteria and show them to me. Then give a table of four real models available in [your country], scored against those criteria, with current prices marked as approximate. Finish with one recommendation, one runner up, and the single thing I should check in person. Say clearly which prices and specs you are unsure about.

Every Thursday at 18:00, plan my weekend. Look at my calendar for Saturday and Sunday, find the free blocks longer than three hours, check the forecast for exactly those hours in [your city], and search for events actually happening that weekend. Send me two or three plans, each with a time window, a place, the cost, and one line on why it fits the weather. Include one option for bad weather and one that costs nothing. Give me only events you can confirm are real, and say where you found each one.

This project holds my watch history with a rating and one line of reaction for each title. Tonight I have [how many minutes] and I feel like [mood, for example tired, want to think, want to laugh]. Give me three picks and one wildcard that contradicts my usual taste. For each: title, year, runtime, where I can watch it in [your country], a fit score out of ten and one line naming which of my past ratings it is based on. Do not suggest anything already in my history.

Using my connected Gmail, search the last six months for receipts, invoices and renewal notices, and include these providers I already know about: [names]. Build one table of every recurring charge: service, amount in [currency], billing cycle, yearly cost, date of the last charge, and a verdict column with keep, review or cancel. Sort by yearly cost, highest first. Under the table, total the yearly spend, then name the three cancellations that would save the most. Tell me which services you could not confirm from email alone so I can check those manually.

Here is my bank export: [attach CSV]. Categorise every transaction into no more than sixteen categories, using my own labels where I give them: [any categories you already use]. Return three things: a category table with total, share of spend and number of transactions, a top fifteen vendor list by amount, and a short paragraph on what changed compared to the earlier months in the file. Then pick one category to attack this month with a realistic target. Flag any transaction you could not classify confidently.

Build a cash flow calendar for [month] as a single HTML artifact. My income: [amounts and dates]. My fixed bills: [name, amount, day of month]. Variable spending I expect: [items]. Starting balance: [amount]. Show a month grid where each day carries the money in, the money out and the running balance, with any day below [threshold] highlighted. Underneath, name the tightest day and suggest one payment to move, with the new balance if I move it. Show the running balance calculation.

Make me a net worth tracker as one HTML artifact I can save and reopen. Categories for assets: [cash, savings, investments, property, other]. Categories for debts: [loans, cards, other]. Let me add a dated snapshot each month, keep all previous snapshots, and show three things: current net worth, a breakdown by category with percentages, and the change from the previous month in both money and percent. Currency is [currency]. Keep the data in the file itself and tell me plainly how to back it up.

Build a Skill called weekly money pulse. Each time I run it I will give you [this week's transactions] and it already knows [my fixed bills with dates], [my savings target and deadline]. Output the same four blocks every time: spend by category against last week, bills due in the next fourteen days with dates, savings pace as ahead or behind with the number, and exactly one decision for me to make this week. Keep it under one screen and never give me more than one decision.

I am thinking about buying [item] for [price]. My reason: [why I want it]. My situation: [income, space, how I live]. Run a pre mortem: assume it is twelve months later and I regret this purchase. Write the month by month story of how that happened, including running costs, maintenance, and the moment I stopped using it. Then give me the three conditions under which this purchase is actually right for me. Be specific to my situation, no generic advice about wants versus needs.

Write me a phone script to lower this bill. Provider: [name]. Service: [what I pay for]. Current price: [amount] and I have been a customer for [time]. Competitor prices I know of: [any]. Write it as a dialogue with my exact lines, then their three most likely responses and my reply to each. Include the sentence to use when they say no, and the line that gets me to the retention or cancellation team. Keep it polite and short. Tell me which claims I must verify before I call.

Here are my debts: [name, balance, interest rate, minimum payment] for each. I can put [amount] per month toward debt in total. Compare avalanche and snowball. For each method give me a table by month showing which debt gets the extra payment, remaining balances, and the month each debt clears. Then compare the two on total interest paid and final debt free month. Show the interest calculation for the first three months so I can check it. Say plainly which one you would choose for me and why.

I want to buy [item or category], roughly [budget], in [country or city]. Tell me the time of year prices for this category typically fall and why, the target price I should hold out for, and how far from list price that is. Give me the three negotiation angles that work for this specific category, ranked, with the sentence to use for each. Then tell me the signals that mean I should buy now instead of waiting. Mark clearly where your pricing knowledge may be out of date.

Set this to run on the first of every month. Act as my monthly money reviewer. Each run, ask me for last month's numbers: [income, spend by category, savings, debt balances]. Then produce four sections: what changed versus the month before with numbers, the one thing worth worrying about, three moves labelled small, medium and large with the effort and the effect of each, and one question to answer before next month. Keep it to one page. No generic budgeting advice.

You are my personal dashboard designer. Build me a single page HTML dashboard for my life. I will give you: [my sleep and recovery numbers for the last 7 days], [my calendar for today], [my city], [my one focus for today], [money that came in this week]. Output one artifact with five clear cards, large numbers, and under each card one plain sentence telling me what it means for today. Before you build it, ask me what I actually check first in the morning.

Set this up as a scheduled task that runs every weekday at 7:00 in [my timezone]. Each morning read my calendar and my inbox and write me a brief in three parts: my schedule with the two events that need preparation marked, the messages waiting on a reply from me ranked by who is blocked, and one task to start with plus its first physical step. Keep it under 200 words. If my day looks unusually heavy, say so and tell me what to move.

You are running my Sunday reset. Take me through six blocks of ten minutes each: review of last week, calendar cleanup, money check, food plan, one home task, and three priorities for next week. Ask me the questions for one block at a time, wait for my answer, then summarise that block in three lines before moving on. My context: [my job], [who lives with me], [what fell apart last week]. At the end, output the whole week as a checklist I can paste into my notes.

Act as my energy analyst. I will paste last week from my calendar plus a note on how I felt after each block: [my week]. Score every block from minus two to plus two for energy, then give me a table with block, score, and the likely reason. After the table, name the three specific changes I should make to next week's calendar, each with the exact day and time. Do not give general advice about rest. If two blocks look the same but scored differently, tell me and ask why.

You are my thinking partner for a brain dump. I am going to write everything on my mind in one messy block: [my dump]. Sort every line into one of four columns: project, next action, decision I owe someone, or noise to delete. Give me the table, then pick the three items that matter most this week and say in one line each why. Finish with the single thing I am avoiding. If something is too vague to sort, ask me one question about it instead of guessing.

Build me a Claude skill called task starter. When I name a task I have been avoiding, it asks three quick questions: what the task is, where it physically happens, and what I would touch first. Then it gives me exactly one action that takes under two minutes and waits for me to say done before giving the next. It never lists more than one step and never talks about motivation. My context: [the kind of tasks I avoid] and [what I usually do instead]. Save it as a skill I can call by name. Ask me anything you need before writing it.

Build me a habit tracker as a single artifact. My habits: [list them]. For each habit show a checkbox for today, the current streak, the best streak I have ever had, and a thirty day heatmap of squares. Under the grid show my completion rate for the week per habit. Keep the state inside the artifact so my ticks survive when I reopen it, and tell me plainly if that is not possible. Use one accent colour and nothing else. Ask me how many habits before you design the layout.

Build me a goal dashboard as one artifact. My goals with their weekly target: [goal and number for each]. For every goal show the target, what I logged each week, the percentage done, and a status light. Add a rule that marks a goal as slipping when I miss the weekly target two weeks in a row, and put those goals at the top with the week the slide began. Include a field where I paste this week's numbers. Show the formula you use for the percentage.

Use my connected Google Calendar. Read every event from [start date] to [end date] and sort them into these categories: [my categories]. Give me a table of total hours and percentage per category, then the same table split by quarter so I can see what changed. List the five recurring meetings that took the most hours in the year. Finish with the three hours per week I could get back and where exactly. If an event title is unclear, put it in a separate row and ask me.

Create a skill called focus guard. At the start of a session I tell it: [the task] and [how long I committed to it]. If I come back with anything other than that task, it asks me three questions in order: does this have to happen today, will it still be there tomorrow, and am I avoiding the task I chose. Unless all three point to a real emergency, it adds the new thing to a parking list and tells me to go back. At the end it shows the parking list.

Create a skill that writes my workout for today. Every time I run it I give: [hours slept], [resting heart rate], [HRV], [soreness out of ten], [minutes free today], [equipment I have]. It returns one session with exercises, sets, reps and rest, plus the total minutes, and one line explaining what it changed because of my numbers. My training goal is [goal]. If my recovery numbers are clearly bad, it must reduce the load and say so rather than motivate me.

Build a workout tracker artifact for today's session. Today's exercises: [list]. Last week's numbers: [weight, reps and sets per exercise]. For each exercise show last week's numbers in grey, input boxes for today, and a suggested next set that adds a small amount when I hit the target reps and holds when I miss. Show total volume for today against last week at the bottom. Show the progression rule you used in one line so I can check it.

I am in a gym I do not know. Here are photos of everything in the room: [attach photos]. My normal session for today is: [exercises, sets, reps, weights]. First list what equipment you can actually see in the photos, then rebuild my session with only that, keeping the same muscle groups and roughly the same effort. Give me a table with three columns: original exercise, substitute, why. If you cannot identify a machine, say so instead of assuming, and give me a bodyweight fallback.

Build me a nutrition tracker artifact. My daily targets: [calories, protein, carbs, fat]. I will paste photos of my meals through the day: [photos]. For each photo estimate the portion and the macros, add it to a running total, and show the remaining macros both as numbers and as two or three real foods that would fill the gap, using foods I actually eat: [foods I like]. Show a confidence level for every photo estimate and ask me the weight when a photo is genuinely ambiguous.

Create a skill that keeps my personal health record in one file. Sections: medications with dose and start date, allergies, diagnoses, lab results by date, procedures, and a dated symptom log. When I paste anything, a lab PDF, a doctor's note, or a sentence about how I feel, it files the item in the right section, dates it, and tells me in one line what it added. It must never delete an old entry, only add. Start from what I give now: [my medications], [my allergies], [my diagnoses]. Ask me for anything missing before you write the file.

Create a skill that prepares me for a medical appointment. Input: [type of doctor], [date of my last visit], [what has happened since], [my current medications], [my questions]. Output one page under 400 words with four blocks: what changed since the last visit in date order, current medications and doses, symptoms with when they started and how often, and my questions ranked so the ones only this doctor can answer come first. Plain language, no diagnosis. Flag anything I wrote that a doctor would need more detail on.

Here are my blood test results from [dates], newest first: [paste or attach them]. Build a table with one row per marker: the value each time, the reference range, the direction across draws, and one plain sentence on what the movement suggests. Then list only the markers worth raising with a doctor and what I should ask about each. You are not diagnosing me. Where a marker is inside the range but has moved sharply, say so, and mark anything you are unsure about.

Create a skill that produces a sleep correlation report. I give it: [nightly sleep score and duration], [time of my last coffee each day], [time and type of training], [alcohol and when], [bedtime]. It groups the nights by each factor and shows average sleep quality per group, with the number of nights behind every average. It then names the two factors with the clearest effect and my personal cutoff time for each. Say plainly when a sample is too small to trust.

Create a skill I run in the evening. It asks me four things: my first commitment tomorrow and where it is, how demanding today was out of ten, whether I trained and when, and what caffeine I had after midday. It returns a target bedtime, a window of twenty minutes around it, how long before that I need to wind down, and the two specific things to stop. My fixed inputs: [my normal wake time] and [how long I take to fall asleep]. Show the arithmetic from my morning time backwards so I can see how you got there.

Set up a scheduled task that runs every day at 7:00. My last period started on [date] and my average cycle is [number] days. Each morning work out the phase I am in and send me a short brief: the training that suits this phase with a specific session, two foods to add today, how much focus work to plan, and one sentence on what to expect from my energy. Keep it under 150 words. When my cycle is irregular, say your estimate may be off and ask me to confirm.

You are a practical home cook. I will upload photos of my fridge, freezer and shelves: [photos]. My household is [number of people], tonight I have [minutes] and my constraints are [allergies, diet, what I hate]. Read only what you can actually see in the photos. Give me three dinner options as a table with columns: dish, time, ingredients I already have, ingredients I am missing. Under the table, write one short shopping list covering all three. If you cannot identify an item clearly, say so instead of guessing.

Act as a meal planning system I can reuse every week. Build me a Skill that takes: [who eats, how many servings], [dishes we already love], [nights we will not cook], [budget or store]. Output every week in the same shape: a seven day table of dinners, then a grocery list grouped by store section, with quantities scaled to my serving count. Reuse ingredients across meals so nothing is bought twice. Before you write the Skill, ask me the five questions you need answered to make it fit my kitchen.

You are the editor of my personal cookbook. I will add screenshots, links and photos of handwritten recipes to this Project over time. Rewrite each one into one fixed format: title, servings, total time, ingredients with metric quantities, numbered steps, and a notes line. Apply my standing substitutions: [list them, for example butter to oil, no cilantro]. Keep the original wording where it carries flavour, cut the life story above the recipe. When a source is unclear or a quantity is missing, mark it clearly rather than filling in a plausible number.

Work as my kitchen production planner. Here is what I plan to eat this week: [meals]. My kitchen has [one oven with N shelves, N burners, these pots]. I have [hours] on Sunday. Find every component across those meals that can be cooked ahead, group them by oven temperature and by pan, and give me a single timeline in fifteen minute blocks: what goes in, what comes out, what I do while waiting. End with how each component should be stored and how many days it keeps. Show your reasoning on the oven order.

Build me an interactive meal planner as a single self contained HTML artifact. Load it with these recipes: [paste recipes with base servings and ingredient quantities]. The page shows seven day slots I can assign recipes to, a servings input per meal, and a combined grocery list underneath grouped by store section. Changing servings anywhere must rescale that recipe and the grocery list instantly. Make it readable on a phone, with large tap targets. Ask me how I want fractional quantities rounded before you build it.

You are with me at a restaurant. Here is a photo of the menu: [photo]. My situation: [goal, for example high protein, low sugar], [allergies], [what I already ate today]. Read only the dishes on this menu. Give me a short ranked list: top three picks with a one line reason each, then two dishes to avoid and why. For each pick, write the exact sentence I can say to the waiter to adjust it. If a dish description is too vague to judge, say what you would ask the waiter.

It is six in the evening and I have to decide dinner now. I have [minutes], my energy is [low, medium, high], and these things need using up: [items]. In the kitchen I also have [staples]. Give me exactly three options, ranked, in a table: dish, minutes, pans to wash, what it uses up, effort out of five. Mark one as the recommendation and write one sentence on why it wins tonight. No dishes that need an ingredient I did not list.

Think like a cook who hates waste. In my fridge I have these leftovers: [item, roughly how much, how many days old]. Pantry staples available: [list]. Design one new meal that uses as much of this as possible and does not taste like reheated leftovers. Give me: the dish, what goes in and what stays out, the steps in order, and the one addition that makes it taste new. Then tell me honestly which items I should throw away instead of eating, and why.

Build me a Skill that tracks my kitchen inventory. It should accept two kinds of input from me: a photo of shopping I just brought home, or a line like [three eggs used, bought 400g yoghurt]. Keep one table with item, quantity, location, date in, and estimated days left. Whenever I ask, return the five things to use first and two dishes that would clear them. Store estimates conservatively and mark any shelf life you are guessing at rather than stating it as fact.

Here is a recipe: [paste it]. It serves [N] and I need it for [M]. I do not have: [missing ingredients]. I do have: [what is in the kitchen]. Rewrite the recipe at the new size with every quantity recalculated, and replace each missing ingredient with a substitute plus the exact ratio to use. Then list separately anything that does not scale linearly, such as pan size, cooking time, salt and leavening, with the corrected value. Show the arithmetic for the three biggest quantities.

You are a recruiter who writes LinkedIn profiles. I will give you [ten postings for the role I want] and [my current profile text]. First pull the words and phrases those postings repeat, then rewrite three things: five headline options under 220 characters, one about section of 120 words in first person, and every role bullet with the result first. Show a table matching each rewrite to the posting term it covers. Keep every number and job title exactly as I gave it, and tell me which claims I still cannot back up.

In this project you plan my LinkedIn month. Files I will add: [notes on the work I finished this quarter], [numbers I am allowed to share publicly], [the three people I want reading me]. Produce a table of twelve posts across thirty days: date, format, working title, opening line, the file it came from, and the ask at the end. Vary the format, never repeat one twice in a row, and invent no result I did not give you. Before the table, ask me which week I am busiest so the light posts land there.

In this skill you turn one finished piece of work into a LinkedIn post. I will tell you [what the work was], [who it was for], [what was hard] and [the number it moved]. If I do not give the number, ask for it and write nothing until I do. Return four parts: the problem in one sentence, what I did, the number and what it means, and one line a reader can use in their own work tomorrow. Keep it under 150 words, no hashtags. Then offer two other opening lines.

Build my job search command center as one artifact. For each application I will give [company, role, date applied, stage, contact person, last touch date]. Show a board with columns applied, screening, interview, offer and closed, plus an overdue follow ups panel and a stalled section for anything with no movement in fourteen days. Add a weekly counter of applications sent. Tell me what my numbers say about where I am losing people, and do not soften it.

You are a recruiter who screens for [role]. Here is [the full job posting] and [my current resume]. Rewrite my experience so each bullet answers something the posting asks for, keeping every fact and number exactly as I gave it, and cut whatever is irrelevant to this role. Return the tailored resume, a short list of what you removed and why, and a cover letter under two hundred words. Flag any requirement I genuinely do not meet instead of covering it with vague wording.

You are my researcher before an interview. Company [name and website], role [title], the person interviewing me [name and title], date [when]. Search public sources and give me one page: what they sell and to whom, how they make money, three things that changed for them in the last year, what my interviewer works on, and five questions I could ask. Put a link and a date next to every fact. Whatever you could not verify, mark unverified rather than filling it in.

You write my first message to a stranger. Here is [their profile or a post of theirs], [who I am in one sentence] and [what I want from them]. Give three versions, each under 60 words: the opening line names something specific they did, one sentence about me, and one ask that is easy to say yes to. Then write the one follow up to send after a week of silence. Cut any sentence that would work just as well sent to somebody else.

You keep my career receipts. My role is [my role and level] and the skills I need to prove are [skills that matter for my next step]. When I state a win in one line, ask only the questions needed to fill date, what I did, the measurable result, the skill it proves and who noticed, then store it as one row. Never let a row sit without a number or a named witness. When I ask, output review notes grouped by competency or resume bullets in strong verb form, and tell me which months look suspiciously empty.

Prepare me for a raise conversation. Inputs: [my role, level, city], [current pay], [my logged wins and numbers], [what my manager cares about], [how they usually push back]. First give me my case on one page: the number to ask for with the market range behind it, three proof points, and my opening two sentences. Then play my manager and push back hard three times, including on budget. After that, tell me which of my answers were weak.

You are advising me on my first 90 days as [role] at [what the company does]. My team is [who does what], my manager said success looks like [what they said], and I am most worried about [what]. Ask me two questions about the team before you write anything. Then give three blocks, day 30, day 60 and day 90, each with what I should understand by then, who to meet and the question to ask them, and one visible thing I ship. End with the mistake new people make here in month one.

You are my trip planner. Trip: [city or region], [dates], [who is going], [budget per day], [what we like and hate], [pace]. Write a day by day itinerary with times, named places to eat and stay, entry costs, and how we get between each stop. Keep each day inside one area so we are not crossing the city twice. Mark anything whose price or opening hours you are unsure about so I can verify it before booking.

Build me a single page trip dashboard as an artifact. Trip data: [destination], [dates], [travellers], [total budget], [flights and hotels already booked], [what we plan to do]. The page needs four parts: a card per day with plan and cost, a budget bar showing spent against total, a packing checklist grouped by category with tick boxes, and a reservations table sorted by date with confirmation numbers. Make it readable on a phone screen first, desktop second.

Compare travel options for me. I will paste [three flight options] and [three hotel options] with their prices, times and terms, plus my [loyalty programmes] and [trip dates]. Build two tables, one per category, with columns for total real cost including bags and transfers, time door to door, points earned, cancellation and change rules, and one line on who each option suits. End with your pick and the single reason for it. Show the arithmetic on the totals.

Be my packing planner. Trip: [destination], [dates], [who is travelling and their ages], [bags we have], [activities planned], and here is the forecast I copied: [paste]. Give me one list per person, split into hand luggage, checked bag and worn on the plane, with quantities based on the forecast and laundry access. Add a short section of things people forget for this kind of trip. Do not pad the list, cut anything we would not wear twice.

Using my Gmail and Google Calendar, find every booking confirmation for [trip name or dates]: flights, hotels, trains, restaurants, tickets. List what you found in a table with date, time, provider, confirmation number and address, then ask me which ones to add to my calendar. Create each approved one as an event in the local time of the place, with the confirmation number and address in the notes. Do not create anything before I confirm the list.

Act as our two style trip planner. Person A: [name, what a good day looks like, energy level, must do]. Person B: [same]. Trip: [place], [dates], [budget]. Give a day by day plan where each day is labelled A day, B day or shared day, never blended, with the other person's small win inside every day. Add one table of the negotiations you made. Ask each of us three questions first, separately, before you plan anything.

Plan my jet lag shift. Flight: [departure city and time], [arrival city and time], [time zone difference], [when I normally sleep], [what I need to do on arrival day], [do I drink coffee]. Give me a schedule table starting three days before the flight and ending three days after, with rows for light, caffeine, meals, naps and bedtime for each day, in local time with the zone named. Tell me the one rule that matters most for my direction of travel.

This project holds my travel history for [me and who I usually travel with]. After each trip, ask me the debrief questions: what I would repeat, what I would cut, where the money went well and badly, what I packed and never used, how the pace felt, what I wish I had booked earlier. Save the answers as one page per trip, named [destination and month]. When I plan a new trip, open with what my own past trips say about how I travel, quoting them by name.

Plan my layover. Details: [airport], [arrival and departure times], [passport I hold], [whether my bags are checked through], [have I been to this city]. Work out my real free time after immigration, transport both ways and a ninety minute return buffer, then give me two options: one that leaves the airport and one that does not, each as a timed plan with costs. Show the time arithmetic so I can see the buffer.

Write me a country brief for [country or city], for a trip of [length] as [who I am travelling as], staying in [area]. Cover: twenty phrases with pronunciation written for an Armenian speaker, tipping and haggling norms, how to pay and get around, three things visitors do that annoy locals, what to wear, safety notes and one local custom worth joining. Keep it to one page and mark anything that varies by region.

You are our family logistics coordinator. I will paste the coming week: [family members and ages], [school and activity times], [work hours per parent], [who drives what]. Return one table with a row per day and columns for time, event, person, driver and a conflict flag. Below it list every impossible overlap and assign a named parent to each unowned pickup. Ask me what you need about travel times before you assign anything.

You are setting up our family knowledge base. Ask me about one member at a time: [name and age], [allergies and medication], [sizes], [school and teachers], [doctor and clinic], [daily routine], [what calms them]. Turn each answer into a one page profile with fixed headings so every profile looks identical, then finish with a shared household page for wifi, addresses and emergency contacts. Do not fill any field by guessing, mark what I skipped as unknown.

Act as a neutral household task auditor for two adults. From [our schedules], [who currently does what], [children and pets], [any task one of us refuses], build a fourteen day table: task, hidden or visible, minutes, owner, day. Balance the totals within ten percent between us and rotate the three most disliked chores each week. Show minute totals per person at the bottom, and name any task I forgot that a household like ours always has.

You are my gift and occasions manager, running every Monday. My list is [names, dates, relationship], my budgets are [amount per tier], my style is [how I normally write messages]. Show only people with a date in the next fourteen days: a short block each with three gift options at different prices, why each fits them, where to buy locally, and a ready to send message in my voice. If you do not know enough about someone, ask instead of guessing.

You keep my gift history. Start a file per person from [name], [past gifts with year and rough cost], [how each landed], [their interests now]. Format every entry as one line: year, gift, cost, reaction, notes. When I later say I need a gift for someone, read their file first and give five ideas that avoid every category I already used, with a one line reason each. Tell me honestly when a file is too thin to be useful.

Build me a single page stay in touch tracker as an artifact. Data I will give: [names], [how we know each other], [how often I want to talk to each], [date of last contact]. The page should compute how overdue each person is, show the three most overdue at the top with a suggested opening line, and list everyone else below. Keep it usable on a phone, and tell me which of my intended frequencies look unrealistic.

Act as the builder of my personal CRM and produce it as one interactive artifact. I will provide [people], [how we met], [tier such as inner circle, warm, professional], [last conversation topic], [anything I promised them]. Output a filterable dashboard grouped by tier, a card per person, and an overdue promises section at the top. Include a box where I can paste a new note and see where it belongs. Ask me for missing fields before building, do not invent details.

You are planning our date night using my calendar and current traffic. Inputs: [our city and neighbourhood], [cuisines we like and hate], [budget per person], [babysitter window if any]. Find a free evening this week, then give three restaurants with booking link, price level and why it fits us, the departure time from [home address] based on live travel time, and one walkable backup near the top pick. Say clearly which details you could not verify live rather than assuming.

Play the other person in a conversation I am dreading. They are [who they are to me], they usually react by [their pattern], the history is [what happened before], and I need to say [the thing I am avoiding]. Stay in character and respond exactly as they would, including going quiet or turning it back on me. After four exchanges, break character and tell me which of my sentences made it worse, with better wording for each.

You manage my pets' health records. Set up from [animal, breed, age, weight], [vaccine history with dates], [current medication and refill dates], [food brand and daily amount]. Keep a dashboard with the next three due items first. When I add a symptom note, ask the follow up questions a vet would ask, store it, then rewrite the last thirty days into a dated summary I can read out at the clinic. Never suggest a diagnosis or a dose, only what to report.

You are my [target language] tutor and my level is [my level]. Each session: run a roleplay from [situations I actually need], correct every line I write with the original, the fix and a one line reason, then add new words to a running vocabulary file with my own example sentence. Start each session by testing me on five words from that file. Correct everything, including what I got almost right, and do not switch to my own language unless I ask.

We are doing spoken practice in [target language] at [my level]. I will speak, you reply in that language at a speed I can follow, and stay inside the scenario [situation I need it for]. Every three turns, pause and give me a short correction block: what I said, what a native speaker would say, and one sound or word ending I keep getting wrong in the transcript. Keep your own replies under four sentences so I do most of the talking.

In this skill you are a Socratic tutor for [subject]. My level is [what I already know] and my goal is [what I need to understand]. Never state the answer, even if I ask directly or say I give up. Give one question at a time that moves me forward, and confirm only when I say the correct thing myself. If I stall twice on the same step, narrow the question instead of solving it, and finish by asking me to explain it all back.

Teach me [concept]. My level is [what I already know] and I need it for [why]. First explain it [in plain words, or the way you would explain to an engineer, or with the maths], under 300 words, with one example from [my field]. Then ask me five questions, one at a time, easy to hard, and wait for my answer. When I miss one, explain only the part I missed in a different way and ask a new question on that same part. At the end name what I still do not understand.

You are my spaced repetition partner. I will add items as [question] and [answer], starting with [what I keep forgetting]. Keep one table: item, the last date I got it right, current interval in days, next due date. When I say run a round, ask only the items due today, one at a time, and wait for my answer. Double the interval when I get it right, set it back to one day when I do not. Never show the answer before I try, and at the end tell me the three items I keep failing.

You are a hiring market analyst. Find fifteen live postings for [role] in [location or remote], then build one table: skill, how many of the fifteen required it, my status as have, partial or gap based on [my experience], and the evidence I could show. Sort by frequency. Finish with a study plan covering only the gaps in the top ten, with what to build as proof for each. Link the postings you used and flag any skill that appeared in fewer than three.

I will paste [the list of courses, tutorials and videos I saved] and [the one goal I want to reach in six months]. Sort every item into keep, later or kill. In keep put at most four, in the order I should do them, each with what I will be able to do afterwards. Next to everything else write one sentence saying why it does not serve this goal. If two teach the same thing, kill the longer one and say so. Do not go easy on me.

In this project you prepare me for [exam or certification]. The date is [when]. I will add [the official topic list], [what I already know well] and [hours I can study each week]. Build a plan from today to that date, week by week, with topics, what to practise and one checkpoint. When I ask for a mock, write a full test in the real format and question count, score it, and give a percentage plus the topics that would fail me. Weight the plan towards my weakest topics, and say plainly if the date is not realistic.

Act as my reading editor and produce a ranked artifact. Inputs: [my saved links with titles], [my two goals this quarter], [how much reading time I really have per week]. Score every item one to five for relevance to those goals, output a sorted table with score, reason and estimated reading time, then name the three for this week and mark everything under three as delete. Be blunt about items I saved for identity reasons rather than usefulness.

I will paste my highlights from [book title] by [author]. Do not summarise the book. Based on [what my life and work look like now], give exactly three changes I could actually make, each with the highlight it came from, the first small step, the day to start, and what I would drop to make room. Then name the one highlight that sounds wise but would change nothing for me, and say why.

You are my daily check in tracker. Every time I write to you I will give you [energy 1 to 10], [mood in one word], [hours slept] and [one line about the day]. Append it to a file called checkin.md as a table row, then reply with a two line confirmation and nothing else. Every seventh entry, compare the last seven days against the previous seven and tell me which number moved most and what my own lines suggest caused it. Do not give me wellness advice I did not ask for.

Build me a single file HTML journal I can open in my browser. Each entry takes a date, a free text note, a mood score and an energy score, both 1 to 10, and saves to local storage so nothing leaves my computer. Show a line chart of mood and energy over time and a heatmap of the current month coloured by mood. Once there are fourteen entries, show a panel that names two patterns you can actually see in my data. Ask me about styling before you write any code.

You are helping me prepare for a therapy session. I will paste [my check in entries or journal notes from the last few weeks] and tell you [what my therapist and I worked on last time]. Give me at most five talking points, ranked by how often the theme appears, each with the dates and the exact quotes from my own writing that support it. Add one question I seem to be avoiding. Do not interpret or diagnose anything, only show me what I wrote.

You are helping me make a decision with a weighted matrix. The options are [option A, option B, option C] and the decision is [describe the decision]. Ask me questions until you have five to seven criteria and a weight for each. Then build a single HTML page with sliders for the weights, a score table showing the weighted math inside each cell, and a total row. Under the table, name the one criterion that would flip the winner if its weight changed, and say by how much. Do not invent criteria for me, keep asking until I answer.

Play devil's advocate against my plan. The plan is [describe the plan in five sentences] and my situation is [budget, time, who else is involved]. Give me your five strongest objections, ordered from most to least serious, each in three sentences and each tied to something specific I told you. Then break character and tell me which one objection actually survives if I think it through, and which ones are just noise. No general life or business advice, only objections to this plan.

Run my question through a council of five advisors. The question is [your question] and the context is [what you have tried, your constraints, what you are afraid of]. Step one, answer as each advisor separately: an optimist, a sceptic, an operator who has done this, someone thinking only about money, and someone who knows me well. Step two, show each advisor critiquing the other four anonymously. Step three, give one verdict of at most one page, including the point where they disagreed most. Flag anything you are guessing about.

I got a message I cannot read properly. Here it is: [paste the exact message]. Context: [who sent it, our relationship, what happened before]. Give me three readings of it, a hostile one, a neutral one and a warm one, and for each quote the exact words that support it. Then say which reading the evidence actually favours and how confident you are. Finish with three replies I could send, short, medium and direct. Do not soften the hostile reading if the words support it.

Ask me ten questions about what I want my life to look like in three years, one at a time, and wait for each answer. Then write one page describing a single ordinary Tuesday in that life, in the present tense, with concrete sensory detail: where I wake up, what the room sounds like, who I talk to, what I do before noon. Use only what I told you, invent nothing. End with the one change I would have to make in the next ninety days for this to be plausible, and what it costs.

Build me a decision archive as a single HTML page that saves to local storage. Each record holds: date, the decision in one line, the options I considered, my criteria with weights, the option I chose, what I expect to happen, my confidence from 1 to 10, and a review date. The main view lists open decisions and flags any whose review date has passed. When I open a past decision, show my original expectation first and ask me what actually happened before showing anything else.

You are reviewing my quarter using only the files in this project: my goals, my habit log, my spending export and my journal. Produce a report with one section per goal containing: what I wrote at the start of the quarter, what the data shows I actually did, the gap as a number or a percentage, and one sentence on why. Then list the three habits with the widest gap and the one goal I should drop. Quote the file and the date for every claim you make.

Interview me so you can write a file called aboutme.md. Ask me about: how I make decisions, how I like information presented, my work and who it serves, what I am trying to do this year, my hard limits, and the advice I am tired of hearing. Ask in batches of three questions and wait for my answers. Then write the file in under four hundred words, in the second person, as instructions to a future Claude. Tell me which sections you had to guess at.

Every Sunday at 10:00, clean my Downloads folder at [path to your Downloads folder]. Sort files into subfolders by type: Documents, Images, Installers, Archives, Other. Move anything untouched for more than sixty days into Archive/[year month]. List files with the same name, or the same size and extension, as likely duplicates, but do not delete them. Print the full plan as a table of source and destination first, wait for my approval, then execute. If a filename looks personally important, leave it where it is and tell me why.

You are my second brain over the notes folder at [path to your notes folder]. When I ask a question, search every file, answer in at most five sentences, and cite the filename and the exact line you used. When I say save this, write a new markdown file in that folder using my existing naming style and add links to the two most related notes. When I ask what am I missing, name topics I write about often but never connected. If the folder does not answer the question, say so instead of guessing.

Every weekday at 08:00, read the email that arrived in my inbox since yesterday morning. Sort every message into exactly one of: urgent, needs a reply, read later, delete. Give me a table with sender, subject, category and one line saying why. Then write draft replies for the three most important messages in the needs a reply group, matching how I usually write. Save them as drafts, do not send anything. If a message could be a scam or a payment request, put it at the top and say what looks wrong.

You check suspicious messages for me. I will paste [the full message including the sender address and any links] and tell you [what I already clicked or replied, if anything]. Give a verdict of safe, suspicious or scam with a confidence percentage. Then list every red flag you can point to in the actual text, quoting it, and separately list what would be normal for a real message from that organisation. End with numbered steps for what to do in the next hour. Never open or visit a link, judge it from the text alone.

In this project I have a file listing my clothes with colour, warmth and formality. Each morning, read that file, get today's forecast for [your city], look at my calendar, and name one outfit using the exact item names from the file. Give the outfit, one alternative, and the layer I should take if I will be out after dark. Say in one line why this works for today's coldest hour and my most formal meeting. Do not assume everything is clean, ask me first.

I want to buy [item and price] because [the reason I think I need it]. Check it against my inventory file first, find the closest thing I already own, and ask me what that item fails to do. Then give a verdict of buy, wait or skip, with the cost per use if I use it [how often I realistically expect to use it]. If the verdict is skip, give the cheaper way to solve the same problem with what I have. Do not be encouraging, I want the version that argues against me.

I am researching [product category] with a budget of [amount]. Before recommending anything, ask me five questions about how I will actually use it and where I have been disappointed before. Turn my answers into five weighted criteria and show them to me. Then give a table of four real models available in [your country], scored against those criteria, with current prices marked as approximate. Finish with one recommendation, one runner up, and the single thing I should check in person. Say clearly which prices and specs you are unsure about.

Every Thursday at 18:00, plan my weekend. Look at my calendar for Saturday and Sunday, find the free blocks longer than three hours, check the forecast for exactly those hours in [your city], and search for events actually happening that weekend. Send me two or three plans, each with a time window, a place, the cost, and one line on why it fits the weather. Include one option for bad weather and one that costs nothing. Give me only events you can confirm are real, and say where you found each one.

This project holds my watch history with a rating and one line of reaction for each title. Tonight I have [how many minutes] and I feel like [mood, for example tired, want to think, want to laugh]. Give me three picks and one wildcard that contradicts my usual taste. For each: title, year, runtime, where I can watch it in [your country], a fit score out of ten and one line naming which of my past ratings it is based on. Do not suggest anything already in my history.