Connect a database, give your project durable instructions, and manage your code like a project that is meant to last.
Lesson 1
Working with Copilot's agent mode
Beyond line-by-line suggestions, Copilot offers an agent mode: describe a bigger task (“add a sign-up form to my quiz and make sure it works”), and Copilot plans several changes, applies them, and checks the result, with checkpoints for you to approve.
This is the right tool once your app grows and you no longer want to describe every small line one by one.
TipAlways review the proposed plan before letting the agent work — it's the best moment to correct course.
Try it yourselfDescribe one multi-step task to Copilot's agent mode (for example, adding a results page to your Quick Poll) and review its plan carefully before letting it run.
As soon as your tool needs to remember information from one session to the next (quiz answers, sign-ups, grades), you need a database. Services like Supabase let you create one for free, with no server setup, and Copilot helps you write the connection code.
Describe to Copilot what you want to store (for example: the student's name and their score), and let it propose the database structure and the code needed to read and write to it.
Try it yourselfCreate a free Supabase project and connect it to a small test page that stores just one piece of information, like a name and a vote.
A poorly protected database can expose your students' data. Always ask Copilot to add security rules (who is allowed to read or write what), and never store more personal information than necessary.
Think about your students' data protection from the start (GDPR in Europe): anonymise what can be anonymised, and be clear about what the data you collect is used for.
TipWhen in doubt, ask Copilot: “does this code follow good data protection practice?”
Try it yourselfAsk Copilot to review your database code for security issues, and fix at least one thing it flags.
A good teaching tool isn't just functional, it's designed for learning: immediate feedback after an answer, visible progress, encouragement rather than punishment. Describe these pedagogical intentions to Copilot, not just technical features.
For example, instead of “show the score”, ask for “show the score with an explanation for each mistake, so the student understands why they got it wrong”.
Try it yourselfRewrite one feature request for your project as a learning-or-user-focused prompt, following the example above, instead of a purely technical one.
Before asking Copilot for a big feature, write yourself a short plan in a few lines: the steps, the logical order, what's essential and what can wait. A good plan produces far better suggestions than a vague request.
Then share this plan with Copilot Chat before you start coding — it can flag missing steps or a more logical order.
Try it yourselfWrite a five-line build plan for your next feature before asking Copilot for any code, then share it with Copilot Chat first.
The bigger your project grows, the more tempting it is to ask for several changes at once. Resist that: one change, one test, one commit on GitHub. If something breaks, you know exactly what to undo.
GitHub lets you roll back very easily thanks to its commit history: it's your safety net to keep iterating without stress.
Try it yourselfMake three small, separate commits today, each with one clear change and one clear commit message.
Without specific instructions, Copilot will not automatically keep every project convention in mind. Put a .github/copilot-instructions.md file in the repository and write the rules you repeat every session: naming, tone, build steps, accessibility constraints, or visual conventions.
You can complement that with prompt files, path-specific instruction files, AGENTS.md, or specialised agent files later. Start with the single always-on instruction file first so the project stops resetting to “generic mode”.
TipRevisit and add to this file as the project grows: it's a five-minute investment that improves every future working session.
Try it yourselfCreate your first .github/copilot-instructions.md file with at least three rules that matter in your own context: style, build steps, and one institutional constraint.
Before showing your app to real students, ask Copilot Chat to play a clumsy or distracted user: “try to break this form”, “what happens if I leave this field empty?”.
Also ask it to generate test cases: examples of correct, incorrect, or completely unexpected answers to your quiz or form.
Try it yourselfAsk Copilot Chat to try to break your app in three different ways, then fix whatever it finds.
Managing your code like a real project with GitHub
A project that lasts needs real organisation: clear commits, small branches, pull requests, and a review habit. If your institution wants the GitHub platform at scale, the GitHub Campus Program can provide GitHub Enterprise Cloud or Server to the whole school — but that is the platform layer, not a blanket free Copilot licence for every staff role.
For Copilot itself, students can still use Copilot Student individually and verified teachers can still use free Copilot Pro individually. Wider staff rollout across IT, HR, finance, leadership, and administration means planning for Copilot Business or Copilot Enterprise with the right governance and budget model.
Try it yourselfCreate a branch, make one small change on it, and open your first pull request to merge it back into your main version.