In this step, you're setting up development environment for the workshop.
Refer to the README doc for preparation.
- Use GitHub Codespaces
- Use Visual Studio Code
- Check GitHub Copilot Agent Mode
- Configure Beast Mode
- Prepare Custom Instructions
- Analyze Product Requirements Document (PRD) and Design API
-
Once the GitHub Codespace instance is ready, open a terminal and run the following command to check out everything you need has been properly installed or not.
# Python python --version# Node.js node --version npm --version# JDK java --version# .NET SDK dotnet --list-sdks -
Check out your repository status.
git remote -v
You should be able to see the following.
origin https://github.com/microsoft/github-copilot-vibe-coding-workshop.git (fetch) origin https://github.com/microsoft/github-copilot-vibe-coding-workshop.git (push)
If you see something different from above, delete the GitHub Codespace instance and recreate it.
-
Move down to the Set-up MCP Servers section.
👇👇👇 Instead, if you'd like to use VS Code on your local machine, follow the instruction below. The section below doesn't apply to those who use GitHub Codespaces. 👇👇👇
-
Check whether you've already installed PowerShell or not.
# Bash/Zsh which pwsh# PowerShell Get-Command pwshIf you don't see the command path of
pwsh, it means you haven't installed PowerShell yet. Visit PowerShell installation page and follow the instructions. -
Check out the version of your PowerShell.
pwsh --version
7.5.0or higher is recommended. If yours is lower than that, visit PowerShell installation page and follow the instructions.
-
Check whether you've already installed git CLI or not.
# Bash/Zsh which git# PowerShell Get-Command gitIf you don't see the command path of
git, it means you haven't installed the git CLI yet. Visit git CLI installation page and follow the instructions. -
Check out the version of your git CLI.
git --version
2.39.0or higher is recommended. If yours is lower than that, visit git CLI installation page and follow the instructions.
-
Check whether you've already installed GitHub CLI or not.
# Bash/Zsh which gh# PowerShell Get-Command ghIf you don't see the command path of
gh, it means you haven't installed the GitHub CLI yet. Visit GitHub CLI installation page and follow the instructions. -
Check out the version of your GitHub CLI.
gh --version
2.65.0or higher is recommended. If yours is lower than that, visit GitHub CLI installation page and follow the instructions. -
Check whether you've signed into GitHub or not.
gh auth status
If you haven't signed in yet, run
gh auth loginand sign-in.
-
Check whether you've already installed Docker Desktop or not.
# Bash/Zsh which docker# PowerShell Get-Command dockerIf you don't see the command path of
docker, it means you haven't installed Docker Desktop yet. Visit Docker Desktop installation page and follow the instructions. -
Check out the version of your Docker CLI.
docker --version
28.0.4or higher is recommended. If yours is lower than that, visit Docker Desktop installation page and follow the instructions.
-
Check whether you've already installed VS Code or not.
# Bash/Zsh which code# PowerShell Get-Command codeIf you don't see the command path of
code, it means you haven't installed VS Code yet. Visit Visual Studio Code installation page and follow the instructions. -
Check out the version of your VS Code.
code --version
1.99.0or higher is recommended. If yours is lower than that, visit Visual Studio Code installation page and follow the instructions.NOTE: You might not be able to execute the
codecommand. In this case, follow this document for setup.
-
Create a working directory.
-
Run the command to fork this repo and clone it to your local machine.
gh repo fork microsoft/github-copilot-vibe-coding-workshop --clone
-
Navigate into the cloned directory.
cd github-copilot-vibe-coding-workshop -
Run VS Code from the terminal.
code . -
Open a new terminal within VS Code and run the following command to check out your repository status.
git remote -v
You should be able to see the following. If you see
microsoftinorigin, you should clone it again from your forked repository.origin https://github.com/<your GitHub ID>/github-copilot-vibe-coding-workshop.git (fetch) origin https://github.com/<your GitHub ID>/github-copilot-vibe-coding-workshop.git (push) upstream https://github.com/microsoft/github-copilot-vibe-coding-workshop.git (fetch) upstream https://github.com/microsoft/github-copilot-vibe-coding-workshop.git (push)
-
Check out whether both extensions have been installed or not – GitHub Copilot and GitHub Copilot Chat.
# Bash/Zsh code --list-extensions | grep github.copilot
# PowerShell code --list-extensions | Select-String "github.copilot"
If you see nothing, it means you haven't installed those extensions yet. Run the following command to install the extensions.
code --install-extension "github.copilot" --force && code --install-extension "github.copilot-chat" --force
-
Make sure Docker Desktop is up and running if you use VS Code on your local machine.
-
Set the environment variable of
$REPOSITORY_ROOT.# bash/zsh REPOSITORY_ROOT=$(git rev-parse --show-toplevel)
# PowerShell $REPOSITORY_ROOT = git rev-parse --show-toplevel
-
Copy MCP server settings.
# bash/zsh cp -r $REPOSITORY_ROOT/docs/.vscode/. \ $REPOSITORY_ROOT/.vscode/
# PowerShell Copy-Item -Path $REPOSITORY_ROOT/docs/.vscode/* ` -Destination $REPOSITORY_ROOT/.vscode/ -Recurse -Force
-
Open Command Palette by typing F1 or
Ctrl+Shift+Pon Windows orCmd+Shift+Pon Mac OS, and searchMCP: List Servers. -
Choose
context7then clickStart Server. -
Choose
awesome-copilotthen clickStart Server.
-
Click the GitHub Copilot icon on the top of GitHub Codespace or VS Code and open GitHub Copilot window.
-
If you're asked to login or sign up, do it. It's free of charge.
-
Make sure you're using GitHub Copilot Agent Mode.
-
Select model to either
GPT-4.1orClaude Sonnet 4.
-
Enter the
/mcp.awesome-copilot.get_search_prompt, followed by entering keywords like "beast mode"It should show list of beast chatmodes. Enter a prompt similar to
4.1 Beast Chat Mode. Then it will save it under the.github/chatmodesdirectory. -
Choose the
4.1-Beastmode instead of theAgentmode. It will automatically change LLM toGPT 4.1. -
Set the environment variable of
$REPOSITORY_ROOT.# bash/zsh REPOSITORY_ROOT=$(git rev-parse --show-toplevel)
# PowerShell $REPOSITORY_ROOT = git rev-parse --show-toplevel
-
Copy workspace settings.
# bash/zsh cp $REPOSITORY_ROOT/docs/.vscode/settings.json \ $REPOSITORY_ROOT/.vscode/settings.json
# PowerShell Copy-Item -Path $REPOSITORY_ROOT/docs/.vscode/settings.json ` -Destination $REPOSITORY_ROOT/.vscode/settings.json -Force
-
Set the environment variable of
$REPOSITORY_ROOT.# bash/zsh REPOSITORY_ROOT=$(git rev-parse --show-toplevel)
# PowerShell $REPOSITORY_ROOT = git rev-parse --show-toplevel
-
Copy custom instructions.
# bash/zsh cp -r $REPOSITORY_ROOT/docs/custom-instructions/setup/. \ $REPOSITORY_ROOT/.github/
# PowerShell Copy-Item -Path $REPOSITORY_ROOT/docs/custom-instructions/setup/* ` -Destination $REPOSITORY_ROOT/.github/ -Recurse -Force
-
Make sure that you're using GitHub Copilot Agent Mode with the model of
Claude Sonnet 4orGPT-4.1. -
Add
product-requirements.mdto GitHub Copilot. -
Enter the prompt like the following for GitHub Copilot Agent to generate an OpenAPI document for you. This OpenAPI document will be the base of your entire application.
Here's the PRD for you. Carefully read through the entire PRD and do the following for me. - Identify all the steps first, which you're going to do. - Generate an OpenAPI document in YAML format. - The OpenAPI document should capture all API endpoints, parameters and request/response payloads. - Assume the API server is `http://localhost:8080` and the base URL is `/api`. - Save it to the `openapi.yaml` file at the repository root. -
Verify the
openapi.yamlis generated at the repository root. -
Click the
[keep]button of GitHub Copilot to take theopenapi.yamlfile.
OK. You've completed the "Development Environment" step. Let's move onto STEP 01: Python Backend Development.

