Meet Alex

Alex is studying a course with a programming component, helps a student society, and works part-time. Today is busy, not exceptional.

The group is building a student survival hub. Alex owns the study planner. A teammate is writing campus guidance. Another is checking the launch budget. Everything must fit together before the group can publish.

You play Alex for the coding path. On the alternative path, play a teammate contributing to the same outcome. No real student identity or personal data is needed.

How each scene works

1. Read the moment and name the friction.
2. Attempt the task briefly before asking Copilot.
3. Supply context, a goal, constraints, and a way to check the result.
4. Inspect the response and make a decision yourself.
5. Save a small artifact another person could use.

Use this prompt pattern throughout:

Here is the context and my attempt. Help me achieve this specific goal. Respect these constraints. Identify assumptions and missing information. Explain how I can verify the result. Ask before changing files.

You do not need to type prompts exactly as written. Adapt them to your task and available client. Attach or explicitly supply the named files; Copilot does not automatically see private chats, lectures, calendars, or every repository file.

Keep a lightweight learning log

Use your issue or pull request, not a new tracking system:

Moment	What slowed me down?	What assistance helped?	What did I verify?
Morning
Build or draft
Review

Start at 08:15: on the bus.