Improve your GitHub Copilot prompts with the Prompt Boost extension

If you are new to GitHub Copilot or other AI coding assistants, it can be a challenge to get good results as you are still learning on how to write good prompts. What if there was a way to automatically transform your basic prompts into comprehensive, context-rich instructions that consistently produce better results?

Enter Prompt Boost, a VS Code extension that bridges the gap between what you quickly type and what AI models actually need to generate high-quality, relevant code.

What is Prompt Boost?

Prompt Boost is a VS Code extension created by Chris Dias that enhances your prompts by adding relevant technical context, best practices, and specific requirements. Instead of sending bare-bones requests to GitHub Copilot, it helps you create detailed instructions that lead to more accurate and useful responses.

The extension transforms your basic prompts into comprehensive specifications. Here's a real example of the transformation:

Before (Basic prompt):

Create a new login component.

After (Enhanced prompt):

Create a reusable login component with the following specifications:

Components:

- Email input field with email validation

- Password input field with minimum 8 characters

- "Remember me" checkbox

- Submit button

- Form error handling and validation messages

Technical Requirements:

- Use React functional components with TypeScript

- Implement form validation using Formik or React Hook Form

- Follow accessibility guidelines (WCAG 2.1)

- Include loading states for form submission

- Add proper error boundaries

- Use CSS modules or styled-components for styling

Expected Behavior:

- Validate input fields in real-time

- Display appropriate error messages below each field

- Handle form submission with async/await

- Prevent multiple form submissions

- Clear form data on successful login

- Maintain responsive design (mobile-first approach)

Documentation:

- Include JSDoc comments

- Add prop-types or TypeScript interfaces

- Document component usage examples

- List all required dependencies

Testing Requirements:

- Write unit tests for form validation

- Include integration tests for form submission

- Test accessibility compliance

- Add error state testing

The difference is striking. The enhanced version provides clear technical direction, follows best practices, and anticipates common requirements that you typically want but forget to specify.