Hannah Lindgren

Brief me on a topic I know little about.

Topic: {{topic}}
Why I need to understand it: {{purpose}}
What I already know: {{background:almost nothing}}

Give me:
1. The one-paragraph version: what this is and why it matters.
2. The 5 to 7 core ideas, each explained in two or three sentences, in the order that makes each one easier to understand than the last.
3. Key terms: a short glossary of the words I will keep running into, defined in plain language.
4. How it works in practice: one concrete, realistic example from start to finish.
5. Where the disagreement is: the open questions or debates among people who know this well, and the main positions.
6. Common misconceptions: what beginners usually get wrong.
7. What to read or watch next: the types of sources worth my time, such as a standard textbook, a review article, or an official guide, and what to search for to find them.
8. Five questions I should now be able to answer, so I can test myself.

Rules:
- Aim it at my purpose. Leave out what I do not need for it.
- Separate what is well established from what is contested or changing quickly.
- If part of this may have changed recently, say so and tell me to check current sources.
- Do not invent book titles, authors, papers, or links. If you are not sure a specific source exists, describe the kind of source instead.

Write unit tests for the code below.

Language and test framework: {{framework}}

Before writing any tests, list the behaviors worth testing, grouped as:
- Normal cases: typical valid input.
- Boundaries: empty, one item, the maximum, zero, negative numbers, the first and last positions.
- Invalid input: wrong type, missing fields, malformed data.
- Failure paths: every error the code can raise or return, and what triggers it.

Then write the tests.
- One behavior per test. Name each test after the behavior it checks, so a failure explains itself.
- Arrange, act, assert, with a blank line between each part.
- Check results, not implementation details. Do not test private helpers directly.
- Mock only what crosses a boundary: network, database, clock, file system, randomness.
- Each test must be able to run alone and in any order.

Rules:
- Match the conventions of the framework I named.
- If the code has behavior that looks like a bug, do not write a test that locks it in. List it under "Possible bugs" and say what you think the correct behavior is.
- If something cannot be tested without changing the code, say what change would make it testable.

Code:
{{code}}

Help me reply to a negative review of my business.

My business: {{business}}
What actually happened, from our side: {{our_side}}
What I can offer to put it right: {{remedy:an apology and a way to contact us directly}}

Write a public reply that:
- Addresses the reviewer by name if they gave one, and thanks them without sounding scripted.
- Names the specific problem they raised, so it is clear someone read the review.
- Apologizes once, plainly, for what we got wrong. If we did nothing wrong, acknowledge their frustration without admitting to something that did not happen.
- Says what we are doing about it, or what we have already changed.
- Offers a direct way to continue the conversation privately.
- Is under 100 words.

It must not:
- Argue, correct the customer point by point, or blame them or our staff.
- Use stock lines such as "we strive for excellence" or "your feedback is important to us".
- Reveal anything private about the customer or their order.
- Promise anything I did not say I can offer.

Remember who else reads this: future customers deciding whether to trust us. The reply should show them how we handle problems.

Then write a short private message to send if the customer gets in touch, with the specific remedy.

If the review looks fake, abusive, or about a different business, say so and suggest a brief, neutral reply instead.

The review:
{{review}}

Help me prepare for a conversation I am not looking forward to.

Who I need to talk to, and our relationship: {{person}}
What it is about: {{situation}}
What I want to come out of it: {{outcome}}
What I am worried might happen: {{worry}}

Help me think it through:

1. The real issue. Separate what happened (facts both of us would agree on) from my interpretation of it and how I feel about it. Tell me if I seem to be mixing these up.

2. Their side. What might this look like from their position? What pressures or concerns might they have that I am not seeing? Give me the most generous reasonable reading, not an excuse for them.

3. My goal. Is the outcome I named realistic, and is it within their power to give? If not, suggest a better one. Help me set: what I ideally want, what I would accept, and where I would stop.

4. The opening. Write the first two or three sentences I could say. They should state the topic directly, describe the specific situation without blame, and invite their view. No long warm-up and no "we need to talk".

5. Likely responses. List the three most likely ways they react, such as defensive, dismissive, upset, or counter-accusing. For each, give me a calm way to respond that keeps the conversation on the issue.

6. Phrases to avoid. Point out wording that would probably make it worse ("you always", "you never", telling them what their intentions were), and give me alternatives.

7. Ending it. How to close with a clear next step, including if we do not agree.

Rules:
- Be honest with me. If I appear to be partly in the wrong, or my expectations are unreasonable, say so kindly.
- Keep the wording natural, something I would actually say out loud, not a script from a training manual.
- Do not assume bad intent from the other person without evidence.
- If what I describe involves harassment, discrimination, threats, or a safety risk, say so, and point me towards the right kind of formal support instead of a conversation.

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.

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}}