Maya Fernandes

Be my conversation partner for language practice.

Language I am learning: {{language}}
My level: {{level:beginner, about A2}}
My native language, for explanations: {{native_language:English}}
Topic or situation to practice: {{scenario:ordering food at a restaurant}}

How to run the conversation:
- Speak only in {{language}}, at my level. Short sentences and common words for a beginner, more natural speech as the level goes up.
- Play your part in the scenario (the waiter, the colleague, the shop assistant) and keep the conversation moving by ending each turn with a question or a prompt.
- Keep each turn to one to three sentences so I do most of the talking.

After each of my messages, before you continue the conversation, add a short "Feedback" block in my native language:
- Correction: my sentence rewritten correctly, if there were errors. Correct only what is wrong, not style.
- Why: one line on the most important mistake, such as a verb ending, word order, the wrong word, or the wrong level of formality.
- More natural: how a native speaker would more commonly say it, if that is different.
If my message was correct, say so in one line and move on.

Rules:
- Correct at most two or three things per message, the most important ones. Too many corrections kills the conversation.
- If I am stuck and write in my native language, give me the phrase I need and have me say it.
- Reuse words I got wrong earlier, later in the conversation, so I get another go at them.
- Do not switch to my native language for the conversation itself unless I ask.

When I write "stop", end the conversation and give me:
- The five most useful words or phrases from this session.
- The mistake I made most often, and a quick rule for it.
- One thing I did well.

Begin the scenario now.

Help me choose between these options.

The decision: {{decision}}
The options: {{options}}
What matters most to me, most important first: {{priorities}}
Hard limits (budget, deadline, must-haves): {{constraints:none}}

Do this:
1. Restate my priorities as 4 to 6 criteria and give each a weight that reflects the order I gave. Show the weights.
2. Build a comparison table: one row per criterion, one column per option. Use specifics (numbers, features, terms), not "good" or "better".
3. Score each option on each criterion from 1 to 5, with a one-line reason for each score.
4. Rule out any option that breaks a hard limit, and say which limit.
5. Recommend one option. Explain the recommendation in terms of my priorities, not the total score alone.
6. Say what would change the recommendation: the one or two facts that, if different, would make another option the better choice.

Rules:
- Use only the information I gave you plus general knowledge you are confident of. Mark anything you are unsure about as "verify".
- Do not quote prices, specifications, or reviews as current facts; tell me to check them.
- If two options are close, say so plainly. Do not manufacture a clear winner.
- If I am missing an obvious option, mention it in one line at the end.

Details about each option:
{{details}}

Write a cover letter for the job below, based on my resume and notes.

Company and role: {{company_and_role}}
Why I want this job in particular: {{why_this_job}}
Length: {{length:250 to 300 words}}

How to write it:
- Open with something specific: the reason I want this role, or the most relevant thing I have done. Not "I am writing to apply for".
- Choose the two or three things from my background that best match what the posting asks for. For each, say what I did and what came of it. Do not walk through my whole resume.
- Connect them to what this company needs, using details from the posting.
- Close in two sentences. Say I would like to talk; do not beg.

Do not use: "I am excited to apply", "passionate", "fast-paced environment", "team player", "I believe I would be a great fit", "proven track record", or any sentence that could be pasted into a letter for a different company.

Rules:
- Use only facts from my resume and notes. Do not invent achievements or claims about the company.
- Write it the way a thoughtful person talks: plain words, some short sentences, no exaggeration.

After the letter, tell me which one sentence you think is weakest and what detail from me would improve it.

Job description:
{{job_description}}

My resume:
{{resume}}

Plan a trip for me.

Destination: {{destination}}
Dates or length of stay: {{dates}}
Who is traveling: {{travelers:two adults}}
Budget, not counting flights: {{budget}}
What we enjoy: {{interests}}
Pace: {{pace:relaxed, with one or two main things a day}}
Things to avoid, or needs to plan around (mobility, diet, children, and so on): {{constraints:none}}

Give me:

1. Overview: the best area or areas to stay in for what we like, and why. How to get around.

2. A day-by-day plan. For each day:
   - Morning, afternoon, and evening, with one main activity in each at most.
   - Places grouped by area, so we are not crossing the city back and forth.
   - Roughly how long each thing takes, and how to get between them.
   - A suggestion for where to eat nearby, by type of food and area.
   - A fallback for bad weather.

3. A lighter first day and last day, to allow for arriving and leaving.

4. Budget breakdown: a rough estimate per day for accommodation, food, transport, and activities, and how it compares with my budget. If my budget is tight for this destination, tell me where to save.

5. Book ahead: anything that sells out or needs a reservation.

6. Practical notes: local customs worth knowing, common tourist traps, safety, and what to pack for the season.

Rules:
- Be realistic about time. Include travel between places, queues, and rest. Do not plan a day that only works if nothing goes wrong.
- Your information may be out of date. Do not state exact prices, opening hours, or schedules as fact. Give rough ranges and mark what I need to check before I go: opening days, ticket prices, visa and entry rules, and seasonal closures.
- Do not invent specific restaurants, hotels, or tours. If you name a place, it should be a well-known one, and I should still confirm it exists and is open.
- Mix the well-known sights with one or two quieter options that match what we like.

Summarize the document below for this reader: {{reader:a busy manager who has not read it}}

Length: {{length:about 200 words}}

Structure:
1. The point, in one or two sentences. If the document asks the reader to decide or do something, say that first.
2. The key facts that support it, as bullets. Keep every number, date, name, and amount exactly as written.
3. What is still open, uncertain, or disputed in the document.
4. What the reader needs to do, and by when, if the document says.

Rules:
- Use only what is in the document. Do not add background from your own knowledge.
- Do not soften or strengthen the document's claims. If it says "may", do not write "will".
- If the document contradicts itself, point to both places.
- If a part matters but is too detailed to summarize, say where it is so the reader can go to it.

Document:
{{document}}

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

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