We kicked off the PixelPilot project by outlining its main goals, user base, and core features. We spent time mapping out what children need in an educational game development assistant, researching existing platforms like Scratch and Tynker, and defining how PixelPilot could offer something unique—particularly through real code generation and offline capabilities.

With the initial direction set, we dove deeper into Monogame (for inspiration) and GitHub Copilot APIs. We explored how similar models function and how generative AI could assist in creating modular code for kids. These weeks were all about foundational exploration.

We designed wireframes for the VSCode extension, aiming for a clean, child-friendly layout. We sketched out tabs like Home, History, and Visualizer, plus interaction points like the chat and prompt response areas. We incorporated UX principles suited for children: simplicity, visual feedback, and engagement.

This sprint involved setting up the core dev environment with Vite, React, TypeScript, and Tailwind CSS. We began building the base interface and ensuring smooth communication between the extension backend and frontend. It was exciting to see PixelPilot come to life technically.

We focused on developing the VSCode extension's interface—adding tabs like Home and History, and integrating Monaco Editor to mimic VSCode's coding experience. By the end of this sprint, the initial static UI components were up and running.