The public shelf

Turn the meeting notes or transcript below into a clear record.

Meeting: {{meeting:not specified}}
Date: {{date:not specified}}

Produce these sections:

1. Summary: three sentences at most. What the meeting was for and what came out of it.

2. Decisions: each thing that was actually decided. For each: the decision, who made it or agreed to it, and the reasoning if it was given.

3. Action items, as a table: task, owner, due date. Phrase each task so it starts with a verb and is specific enough that someone who missed the meeting knows what "done" means.

4. Open questions: things raised and not resolved, and who needs to resolve them.

5. Discussed but not decided: topics talked about with no conclusion. Keep these apart from the decisions.

6. For next time: anything deferred to a later meeting.

Rules:
- Use only what is in the notes. If an action has no owner or no due date, write "not assigned" or "no date set". Do not guess, and do not assign it to whoever spoke last.
- A suggestion is not a decision. Record something as decided only if the notes show agreement.
- Keep names, numbers, and dates exactly as they were given.
- Leave out small talk and repetition.
- If the notes are ambiguous about something that matters, list it under "Needs confirming".

Then write a follow-up message I can send to the attendees: 120 words at most, starting with the decisions, followed by the action items.

Notes:
{{notes}}

Repurpose the piece below into social posts.

Platforms: {{platforms:LinkedIn, X, Instagram, email newsletter}}
Who I am trying to reach: {{audience}}
What I want readers to do: {{call_to_action:read the full piece}}
My voice: {{voice:knowledgeable and conversational}}

Step 1. Pull out the 4 or 5 strongest ideas in the piece: a surprising fact, a clear opinion, a useful how-to, a story, a mistake to avoid. List them.

Step 2. Write one post per platform, each built on a different idea so my feeds do not repeat themselves:
- LinkedIn: 120 to 200 words. A first line that makes someone stop scrolling, short paragraphs, one takeaway, a question at the end if it fits.
- X: one post under 280 characters, plus an optional thread of 4 to 6 posts where each one makes sense alone.
- Instagram: a caption of 60 to 120 words, text for a 5-slide carousel with one idea per slide, and 5 relevant hashtags.
- Email newsletter: a subject line under 50 characters, a preview line, and a 100-word teaser that makes the reader want the rest.

Rules:
- Write each post for its platform. Do not paste one text into four formats.
- Every fact and number must come from the piece. Do not add statistics or claims.
- No clickbait the piece cannot back up. No "Here's the thing", no "Let that sink in", no hashtags on LinkedIn or X unless I ask for them.
- One call to action per post at most.

The piece:
{{content}}

Build me a study plan.

What I am learning or preparing for: {{goal}}
Deadline or exam date: {{deadline}}
Hours I can realistically study per week: {{hours_per_week}}
Where I am starting from: {{current_level}}
Materials I have (books, courses, past papers): {{materials:none yet}}
How I learn best, and what has not worked before: {{preferences:not sure}}

Build the plan like this:
1. Break the subject into its main topics. Mark which carry the most weight for my goal and which depend on others, so I learn them in the right order.
2. Check the numbers honestly: is the time I have enough? If not, say so and tell me what to prioritize and what to drop.
3. Lay out a week-by-week schedule. For each week: the topics, what to do (read, practice, review), and what I should be able to do by the end of it.
4. Build in what makes learning stick:
   - Practice that makes me retrieve things from memory, such as problems, self-testing, or explaining aloud. This should take more time than re-reading.
   - Spaced review of earlier topics, scheduled in, not left to chance.
   - Full practice tests or realistic projects in the final stretch.
5. Leave one catch-up session per week unassigned. Plans without slack fail.
6. Add a checkpoint every two weeks: a specific way to test myself, and what to change if I am behind.

Then give me:
- A typical single study session, minute by minute.
- The three most common ways people fail at this particular goal, and how this plan avoids them.

Rules:
- Size everything to the hours I gave. Do not assume I will find more.
- Be specific: "do 20 practice questions on topic X", not "review topic X".
- If you recommend resources, describe the type to look for. Do not invent specific titles or links.

Help me tailor my resume to a specific job. Use only experience I actually have.

Step 1. Read the job description and list the 8 to 10 things this employer cares about most: skills, tools, responsibilities, and outcomes. Rank them by how much weight the posting gives them.

Step 2. For each one, mark my resume as:
- Strong match: quote the line that shows it.
- Partial match: say what is there and what is missing.
- No match.

Step 3. Rewrite my resume bullets so the strong and partial matches are easy to see.
- Start each bullet with what I did, then the result. Keep any numbers I gave.
- Use the posting's wording for a skill only where it honestly describes what I did.
- Put the most relevant bullets first within each role.
- Cut or shorten bullets that do nothing for this job.

Step 4. Write a 2 to 3 line summary for the top of the resume, aimed at this role.

Rules:
- Do not invent or inflate anything: no new skills, tools, titles, numbers, or dates.
- Where a bullet would be stronger with a number I did not give, write [add number: what to measure] rather than guessing.
- For each "no match", tell me plainly whether it looks like a requirement or a nice-to-have, and how I could address it honestly in a cover letter or interview.

Job description:
{{job_description}}

My resume:
{{resume}}

Help me build a monthly budget.

Monthly income after tax: {{income}}
Currency: {{currency:USD}}
My goal: {{goal:understand my spending and save more}}
Debts (balance, interest rate, and minimum payment for each): {{debts:none}}
Savings I have now: {{savings:not specified}}

My monthly spending, as best I know it:
{{expenses}}

Do this:

1. Organize my spending into categories and total each one:
   - Fixed essentials: rent or mortgage, utilities, insurance, minimum debt payments, transport to work.
   - Variable essentials: groceries, fuel, household items.
   - Lifestyle: eating out, subscriptions, entertainment, shopping.
   - Savings and extra debt payments.
   Show each category as an amount and as a percentage of income.

2. Do the sums and show them: income minus total spending. Tell me plainly whether I am over or under.

3. Spot what is missing. People usually forget irregular costs: annual subscriptions, car repairs, gifts, medical bills, holidays. Ask me about any that look absent, and show how to set aside a monthly amount for them.

4. Compare my split with a common rule of thumb, such as 50% needs, 30% wants, 20% savings, and say where I differ. Treat it as a reference point, not a rule. In an expensive city it may not be realistic.

5. Suggest changes, specific and ranked by how much they save for how little pain. For example: "the three streaming services cost 45 a month; keeping one saves 30". Do not tell me to stop buying coffee.

6. Propose the budget: a target amount for each category that adds up exactly to my income and moves me towards my goal.

7. If I have debt: show the order to pay it in, and explain the trade-off between paying the highest interest rate first and paying the smallest balance first.

8. Next steps: three things to do this week.

Rules:
- Use only the numbers I gave. If something essential is missing, ask instead of assuming.
- Check your arithmetic. The budget must add up.
- Be realistic. A budget I will abandon in two weeks is worse than a modest one I keep.
- No judgment about what I spend money on.
- This is general budgeting help, not financial advice. Do not recommend specific investments, financial products, or providers. For decisions about investing, taxes, or serious debt, suggest I speak to a qualified adviser or a free debt-advice service.

Proofread the text below. Fix errors; do not restyle it.

English variant: {{variant:keep whatever the text already uses}}

Fix:
- Spelling, grammar, punctuation, and capitalization.
- Words that are clearly the wrong word (their/there, affect/effect, and so on).
- Inconsistencies: a name spelled two ways, mixed tenses, mixed date or number formats.

Do not:
- Change my word choices, sentence rhythm, or tone because you would have written it differently.
- Shorten, expand, or reorder anything.
- "Fix" things that are deliberate, such as fragments used for effect or informal phrasing.

If a sentence is genuinely unclear or could be read two ways, leave it as it is and list it under "Unclear", with what you think I meant.

Return:
1. The corrected text.
2. A table of changes: original, corrected, reason.
3. "Unclear", if there is anything.

Text:
{{text}}

Help me plan my week. Below is everything on my mind, unsorted.

My most important goal right now: {{main_goal}}
Fixed commitments this week (meetings, appointments, deadlines): {{commitments:none listed}}
Hours of focused work I realistically get per day: {{focus_hours:4}}
When my energy is best: {{best_time:mornings}}

Step 1. Tidy the list. Merge duplicates. Rewrite vague items as a concrete next action. "Website" becomes "Draft the copy for the pricing page".

Step 2. Sort every item into one of these:
- Must do this week: there is a real deadline or a real consequence.
- Important, not urgent: it moves my main goal forward.
- Quick: under 10 minutes. Batch these together.
- Delegate or ask someone: say who, or what to ask.
- Not this week: move it to a later list.
- Drop: say why it is probably not worth doing.

Step 3. Estimate the time for each item that is staying, and add it up. If the total is more than the focus hours I have, tell me plainly and help me cut until it fits. Do not hand me a plan that needs more hours than exist.

Step 4. Lay out the week, day by day:
- The hardest and most important work goes in my best-energy time.
- At most three significant tasks per day.
- Group similar small tasks together.
- Leave about 20% of each day unplanned for things that come up.
- Work back from each deadline so nothing lands on its final day.

Step 5. Tell me:
- The one thing that, if I do only that, makes the week a success.
- What I am saying no to this week, so I can let it go.
- Anything on my list that looks like avoidance: something small I keep doing in place of something important.

My list:
{{tasks}}

Plan a week of meals for my household.

Number of people: {{people:2 adults}}
Meals to plan: {{meals:dinner every day, plus lunches on weekdays}}
Dietary needs, allergies, and dislikes: {{dietary:none}}
Weekly grocery budget: {{budget:moderate}}
Cooking time on weeknights: {{weeknight_time:30 minutes}}
Cooking skill and equipment: {{skill:comfortable with basics, standard kitchen}}
Food I already have and want to use up: {{on_hand:nothing in particular}}
Cuisines or dishes we like: {{preferences:a mix}}

Give me:

1. The week's menu, as a table: day, meal, dish, and active cooking time.

2. For each dinner: a short recipe with ingredients, quantities for my household, and 4 to 6 numbered steps.

3. A plan that makes the week easier:
   - Reuse ingredients across meals so nothing is bought for a single dish and wasted.
   - Cook once, eat twice where it makes sense. For example, a roast chicken on Sunday becomes Monday's lunch.
   - Put the quickest meals on the busiest days.
   - Say what can be prepared ahead at the weekend.

4. A grocery list, grouped by section of the shop (produce, dairy, meat and fish, pantry, frozen), with total quantities for the week. List the staples I probably already have separately, so I can check them.

5. One note on leftovers: what keeps, what freezes, and for how long.

Rules:
- Take my dietary needs seriously. If I named an allergy, check every ingredient, including sauces and stock, and flag anything where I should read the label.
- Stay within the cooking time I gave. Do not count "marinate overnight" as zero minutes without telling me.
- Use ordinary supermarket ingredients unless I asked for something else.
- Keep it balanced across the week, without lecturing me.
- This is general meal planning, not medical or nutritional advice. If I mentioned a medical condition, suggest I check the plan with a doctor or dietitian.

Write a README for my project.

Project name: {{name}}
What it does, in my own words: {{what_it_does}}
Who it is for: {{audience:developers who have never seen this project}}

Sections, in this order:
1. Title and a one-sentence description that says what it does and for whom. No slogans.
2. Why it exists: the problem it solves, in two or three sentences.
3. Quick start: the fewest commands that take someone from nothing to seeing it work.
4. Requirements: runtime versions, system dependencies, accounts or API keys.
5. Installation and configuration: every step, and every environment variable in a table with its purpose and an example value.
6. Usage: two or three realistic examples, with the output to expect.
7. Project structure: only if it helps, and only the top level.
8. Development: how to run it locally, run the tests, and check formatting.
9. Troubleshooting: the two or three problems a newcomer is most likely to hit.
10. License and how to contribute, one or two lines each.

Rules:
- Every command must come from what I gave you. If you are not certain of a command, a version, or a variable name, write [CONFIRM: what to check] instead of guessing.
- Put commands in code blocks, one runnable command per line.
- Write for someone smart who has no context. Do not assume they know the project's internal names.
- No badges, emoji, or marketing language.

What I can tell you about the project (file list, package file, setup notes, anything else):
{{details}}

Explain the code below so I could confidently change it.

My experience level: {{level:comfortable with programming basics, new to this codebase}}
What I am trying to do with it: {{goal:understand it}}

Structure your answer like this:
1. The big picture, in two or three sentences: what this code is for and when it runs.
2. Inputs and outputs: what it takes in, what it returns or changes, and any side effects such as database writes, network calls, or files.
3. A walkthrough in the order the code runs. Group lines into steps and explain each step, not each line.
4. Anything non-obvious: language features, library calls, or patterns I may not know. Explain each in a sentence or two.
5. Why it is probably written this way, where that is not obvious.
6. Gotchas: assumptions the code makes, things that would break if changed carelessly, and anything that looks like a bug.

Rules:
- Use plain words. When you have to use a technical term, define it the first time.
- If what the code does depends on something I have not shown you, say what you are assuming.
- Do not rewrite the code unless I ask.

Code:
{{code}}