Difference between revisions of "AI usage framework"

From MSX Game Library

(Created page with "Here is the framework established regarding the use of AI in the development of MSXgl. I distinguish between three different levels of AI usage: == đŸ€– Vibe coding == Let t...")
 
Line 23: Line 23:
 
* Build tool
 
* Build tool
 
* My MSX games
 
* My MSX games
 +
 +
If anyone would like to contribute to MSXgl, I’m counting on them to respect this approach and submit only code they’ve written themselves.
 +
 +
[[image:Twonks ai.png]]<br/><small>by [https://www.instagram.com/twonks Twonks]</small>

Revision as of 00:11, 28 October 2026

Here is the framework established regarding the use of AI in the development of MSXgl.

I distinguish between three different levels of AI usage:

đŸ€– Vibe coding

Let the AI do its thing without trying to understand the details of the generated code, as long as it gets the job done.

Reserved solely for experimentation on projects that aren't essential to MSXgl and that I simply wouldn't have done otherwise:

  • MSXgl Project Wizard

đŸŠŸ AI assisted

DĂ©velopper avec l'aide de l’IA mais en gardant la maĂźtrise de tout le code. L'IA est lĂ  en soutien pour proposer des amĂ©liorations ĂȘtre amenĂ© Ă  crĂ©er du code.

Réservé aux développements non directement lié à MSXgl, qui m'intéresse, mais

đŸ§‘â€đŸ’» Human scale

Made entirely by hand to maintain total control over the code, work at my own pace, and challenge myself. That’s what I love about MSX development—often even more than the final result. AI can be used to gather information, handle formatting, or provide comments, but it doesn’t write a single line of code for me (as has been the case for several years now).

This concerns the core of MSXgl:

  • Library modules
  • Build tool
  • My MSX games

If anyone would like to contribute to MSXgl, I’m counting on them to respect this approach and submit only code they’ve written themselves.

Twonks ai.png
by Twonks