Describe a behavior
“Build an app” is too broad for a first step. Choose a single useful task. A reading list with an add action and a clear empty state is a better learning target than a full social platform. Define what the user should see and do.
Ask for a plan before changes
Have the coding assistant identify the relevant files, propose a small implementation, and explain how you will verify it. If the project already exists, preserve its structure. Make a recoverable commit before a larger change.
Inspect what changed
Ask for a plain-language explanation of the diff. Check unfamiliar dependencies, data access, and browser-visible code. Do not accept code simply because it runs once. Generated code can contain errors or security problems and needs review.
Test actual behavior
Try normal input, empty input, long content, and repeated actions. Use the keyboard and a narrow screen. Capture the exact error and the steps that caused it. Fix one concrete failure at a time, then rerun the relevant check.
Finish with a handoff to yourself
Write setup instructions, the command to start the project, what works, where data lives, and known limitations. This makes the project maintainable after the conversation ends. Further reading: GitHub’s responsible-use guidance for Copilot is linked below.
Further reading: GitHub: Responsible use of Copilot agents.
Make it yours
Create a one-page reading-list brief with three acceptance checks. Build only the add-book behavior first and explain the resulting code in your own words.