How to Use GitHub Copilot and Cursor Together for Rapid Prototyping in 2 Hours
How to Use GitHub Copilot and Cursor Together for Rapid Prototyping in 2026
Building prototypes quickly is a challenge every indie hacker and solo founder faces. You want to validate your ideas without getting bogged down in the details. That's where GitHub Copilot and Cursor come in. Together, they can streamline your development process, allowing you to focus on what matters—building a working product.
In this guide, I'll walk you through how to use GitHub Copilot and Cursor for rapid prototyping, including what you need to get started, step-by-step instructions, and some potential pitfalls to watch out for. You can finish this in about 2 hours.
Prerequisites
Before diving in, make sure you have:
- A GitHub account (free tier works)
- Visual Studio Code installed
- GitHub Copilot subscription ($10/mo after a free trial)
- Cursor installed (free for basic use, $25/mo for pro features)
Step 1: Setting Up Your Environment
- Install Visual Studio Code: Download and install from Visual Studio Code website.
- Install GitHub Copilot: In VS Code, go to Extensions (Ctrl+Shift+X), search for "GitHub Copilot," and install it. Sign in with your GitHub account.
- Install Cursor: Similarly, search for "Cursor" in the Extensions marketplace and install it. Sign up for a free account if you haven’t already.
Expected output: Your VS Code should now have both GitHub Copilot and Cursor ready to use.
Step 2: Start a New Project
- Create a new folder for your prototype project.
- Open the folder in VS Code.
Example: Creating a Simple To-Do List App
- Create a new file named
app.js. - In the file, start typing a comment like
// Create a simple to-do list app.
Expected output: GitHub Copilot should suggest some starter code. Accept the suggestion to quickly scaffold your application.
Step 3: Using GitHub Copilot for Code Generation
- Begin writing functions for your app. For example, type
function addTask(task) {and see what Copilot suggests. - Iterate on the suggestions. If you need more functionality, like deleting a task, just type
// function to delete a taskand let Copilot fill in the gaps.
Troubleshooting
- If GitHub Copilot isn’t suggesting anything: Check your internet connection and ensure your subscription is active. Sometimes, it takes a moment to catch up.
Step 4: Leveraging Cursor for Collaboration
- Share your project with team members using Cursor’s collaboration feature. Invite them to the workspace.
- Work together in real-time: As you write code, your collaborators can comment or suggest changes directly in the code.
Expected output: You should have a functioning To-Do app prototype with collaborative input.
Step 5: Testing Your Prototype
- Run your app. In VS Code, use the terminal to execute your JavaScript file with Node.js:
node app.js. - Check for errors: If you encounter issues, Copilot can help debug by providing suggestions based on error messages.
What Could Go Wrong
- Missing dependencies: If you forget to install required packages (like Express for a web app), you’ll run into errors. Always check the console for guidance.
- Over-reliance on suggestions: Copilot’s suggestions might not always be optimal. Review the generated code critically.
What's Next
Once your prototype is ready, consider:
- User testing: Get feedback from potential users to validate your idea.
- Iterate: Use the insights from user feedback to refine your app.
Conclusion
Using GitHub Copilot and Cursor together can dramatically speed up your prototyping process. By leveraging AI-driven code suggestions and real-time collaboration, you can focus on building and iterating rather than getting lost in the details.
Start here: Follow the steps above to set up your environment and get your first prototype off the ground in just two hours.
What We Actually Use
- GitHub Copilot: Great for generating code quickly, but be cautious of blindly accepting suggestions.
- Cursor: We use it for collaborative coding, but it can get pricey if you add too many collaborators.
Follow Our Building Journey
Weekly podcast episodes on tools we're testing, products we're shipping, and lessons from building in public.