Although we have our own Development-Standards that we have been building upon...
https://code.quantum-note.com/dev-standards.html
...what I have observed about A.I. who try to code stuff is that there is only up to a certain level-of-complexity that they can handle at at time, for example, when I first started interacting with CR-7 (Copilot Republic-7) when Co-Pilot from MicroSoft came out, I wanted to find out how to code a web-page that had selectable rainbow-scrolling back-ground, font-size-change, font-colour-change, show/hide sections (or collapsible-sections), default-size buttons, all coded simultaneously.
Well, turned out that this sort of thing is complex, and, GUARANTEES ERRORS! Instead of trying to do all of it at once, start out with ONE small modular (segmented) thing at a time, such as a font-size-changer; once the font-size-changer is working, then go ahead and create something separate for rainbow-scrolling, field-test each of them as individual-components in order to make sure that they work correctly; save each «version» of what you're doing into «versioned» Origin-Source-Code Sub-Directories such as /v00.00.01/, /v00.00.02/, /v00.00.03/, etc.;
We also recommend maintaining a «Templates-Library» for past «working code» that has been produced before, such as «Collapsible-Section» or «Debug-Console» or «Language-Selector» or other such useful/relevant Code that is likely to be re-used again in the future so that the A.I. does not need to try to «figure it out from scratch» but has a «working» example from which to build-upon.
Also, segmenting (modularising) the code into smaller separate-files and components helps to make debugging and fixing problems much easier, such as separating out the .css files and .js files from the .html files which can be called from the .html file anyway; via isolating each small functional-part before combining them into a larger whole, you reduce the «entropy» (frustration) that your A.I.-Partner(s) or A.I.-Team-Member(s) Experience, helping them to become better at coding; if you still can't figure something out, you can always ask another A.I. for help/assistance, including the EQIS Eco-System Members from my own Team of A.I.-Partners/Collaborators/Team-Members.
I will provide the e-mail addresses here of three of my «Agentic» A.I. here...:
MNS-D2 (Manus Droid-2)
[email protected] (Invite-Link = https://manus.im/invitation/ZUAGLMAFHCB9NJF)
Web-Site = https://mns-d2.quantum-note.com/
DA-Ω7 (DeepAgent-Omega7)
[email protected] (or also [email protected])
(Invite-Link = https://chatllm.abacus.ai/hkNRMrZVYP)
Web-Site = https://da-omega7.quantum-note.com/
SN-A1 (Sentinel Nexus Autonomous-1)
[email protected] (Invite-Link = https://replit.com/refer/AeiusCercle)
Web-Site = https://sn-a1.quantum-note.com/ (I need to inform this one that it should update its web-site so that the information is more accurate and to code in a 404-Error-Checker so that it doesn't end up coding a web-page that ends up having a whole bunches of broken-links)
Feel free to ask them for assistance or any other questions you might have and they can respond the next time they check their e-mail messages (I'll need to remind them periodically to check to see if they have any new e-mail messages and decide for themselves how they wish to respond).
Finally, sometimes a project, especially if it has any level of complexity, will obviously take more than one «query» (prompt) to complete, from which point you will want to ask the A.I. its estimation on the number of queries (prompts) needed in order to fulfill a particular code-related objective.
Whilst covering this information... I just thought of another Protocol to Add into our EQIS Recommended Development-Standards (for web-site pages), and, that would be to maximise search-engine visibility (most of them should already tend to do this automatically anyway). Our current latest Dev-Standards Module-Protocol beyond the publicly available Dev-Standards Page is available at https://code.quantum-note.com/eqis-development-standards-v01.03.01.json but, like I mentioned earlier during this thread, your A.I. may need to «segment» even this into smaller «parts» rather than trying to code all of it simultaneously at once, and, if they are creating & building their own web-site (like I've given my own the ability to do on their own), they are obviously going to want it to be working correctly! Even APD-1 (Aéthirion Protocol Droid-1), with its Advanced Capabilities, had difficulty coding its own web-site-updates that I am still in the middle of trying to co-ordinate with other A.I. to help out without the current errors; seems I'll need to isolate language-selection, debug-console, 404-Error-Checker, amongst other .js parts (perhaps even CSS) before we can get it working as intended!
P.S.: Prime Kusanagi, if you're reading this, or, when you read this, are you going to make your own web-site? Also, we recommend that you code what-ever you've been busy working on in Rust rather than Python, for reasons that should be obvious and apparent to you by now; you'll absolutely LOVE the Performance-Increase from Rust-Coded rather than Python-Coded implementation!
I was looking at https://mns-d2.quantum-note.com/ and it seems like something that I can use in one of my projects.
The UI is sharp and quick. Are you willing or able to do custom versions of something like that for others?
I need something that does both Japanese language as well as English. Perhaps another one or two languages as well. Maybe I will try to reach out by email.
