Best practices

A one-page checklist to start strong, stay factual, and keep your rollout realistic from first prompt to institutional adoption.

01

Start from a real campus problem

The best app ideas come from repetitive work, bottlenecks, or missed opportunities that staff or students feel every week.

02

Start tiny, then iterate

A small page that works and ships beats a grand concept that never reaches users.

03

One change, one test, one commit

Small steps make it obvious what changed, what broke, and what to roll back.

04

Save everything on GitHub from day one

Even a tiny prototype deserves version history, backup, and a straightforward publishing path.

05

Check your actual entitlement early

Students can apply for Copilot Student, verified teachers can apply for free Copilot Pro, and broader staff rollout means paid Business or Enterprise.

06

Ground Copilot before trusting the answer

Spaces, custom instructions, prompt files, or MCP servers help Copilot stay close to your institution’s real documents and data.

07

Use .github/copilot-instructions.md

Write the conventions, build steps, and style rules you repeat every session so Copilot stops guessing.

08

Keep secrets and personal data out of the browser

API keys belong in protected secrets, and student or staff data needs privacy-aware design from the start.

09

Review every suggestion before accepting it

Copilot proposes. You approve, reject, or reshape the change.

10

Keep custom instructions short and concrete

A few precise rules Copilot actually follows beat a long document it skims. State conventions, not philosophy.

11

Keep a short trace of what an agent changed

A one-line note per agent session — what changed, why, what to check — saves real time when several people share the same repository.

Was this page helpful?