@manayp

Currently I finished the website overall but testing it has been a headache because it is not running and the screen is white… I tried to resolve this with Claude, Github Copilot, and EVEN Chatgpt but none of them could really figure out whats going on so I think it is because of my browsing system so I will need to figure something out. I also worked on my README and completed it ALMOST.

I built a good enough logo using Canva for my product and I also tested the product and found out that there was a LOT of errors and I am going to fix it now in upcoming recordings so STAY TUNED. Plus I added stimulated data for testing.

I am working on the Html and JS part of my project and my goal is basically to make a medical device with hardware to help people with ai insights but currently I am doing the coding and trying to put stimulated data and more.

Claude also helped me a lot and so did Github Copilot: CSS Variables — I set up –primary and other custom variables at the top of the file so I can change one color in one place and have it update everywhere. No more hunting through 50 random lines.100vh — For the activation screen, I used min-height: 100vh so it always fills the full screen height. vh just means “viewport height,” so 100vh = the whole screen.em and rem — When I used em, it scales based on the parent’s font size (like 1em = same size, 1.5em = 1.5× bigger). rem is more predictable because it always uses the root font size instead of the parent.inline-block — I used inline-block for elements that needed to sit next to each other but still have proper width and height. It’s basically the middle ground between inline and block.Flexbox — I used flexbox to lay things out cleanly in rows or columns, like the stat cards and the nav tabs. Way easier than messing with floats.CSS classes for show/hide — Instead of writing display: none in JavaScript everywhere, I just toggled a .hidden class. CSS handles the hiding, JS just switches the class.Activation screen background color — I can change the activation screen’s background by setting background-color on #activation-screen or .overlay in the CSS. I can make it any color or even a gradient. THERE was a lot of errors when I was typing but that was fixed. A big thing is that I also used OneCompilor tool which helped me compile my code and test it before showing it to claude which approved or disapproved it and then I carried on from there.

You have covered topics such as the concept of the IIFE and how it must be enclosed, the distinction between null and 0, what exactly linearSlope, stdDev, classifyTrend and analyzeEntries do, and how Groq API relates to your application through the web browser via your API key. You spotted and corrected some bugs, including the issue with duplicate IDs, typographical error such as entried vs entries, and the discrepancy between escapeHtml and escapeHTML. You came up with your own designs of < 35 || > 42 for flagging temperatures and 40-180 for heart rate, as well as AI safety rules. Not bad for one session! I was a bit confused in a bunch of aspect but that’s fine because Claude and Github Copilot helped a lot and really changed my way of coding and it also taught me stuff like Standard Deviation and moreee.

I am working on the Html and JS part of my project and my goal is basically to make a medical device with hardware to help people with ai insights but currently I am doing the coding and trying to put stimulated data and more.

I fixed the polls because they were not functioning.

I built CleanTone as a browser-based audio enhancement tool, and in this session I focused on polishing the details: I swapped in my own logo image, added a meta description and favicon so the site looks legitimate when shared or searched, set the license to MIT, and cleaned out dependencies in package.json that were leftover from an earlier version I never finished trimming. I also added a small file-counter feature to the footer myself, but in typing it out by hand I used the wrong quote style and accidentally broke the whole script — every single feature on the page stopped working because of one syntax error. I caught it, found the exact line, fixed it, and verified the whole app worked end-to-end again before pushing. The new logo is attached below plus I hosted it in Vercel so other people can see it. Claude helped me signficantly too in fixing and making various changes and so did Github Copilot in fixing mistakes that Claude made and I also helped in coding significantly.

Claude and I teamed up to make everything look more good for the user so that it’s user friendly and helpful in the same time.

I am working on the connections to the browser because I want to run this locally instead of purchasing an api. So with Claude we are figuring out on how change acoustics just enough to make it sound more enhanced and better. I completed the dashboard and the features page with the play buttons where individuals could also compare their two audios.

Recently, I included Flappy Bird-style gameplay and a Snake learning mode on Learnix so that users may learn in an entertaining and interactive manner. The games are based on the subject of your choice, with questions and challenges being converted into a game format that will keep you interested rather than bored. It was all done in a professional manner using GitHub Copilot and Claude, who helped with the creation of the logic for the AI-based learning process.

I have developed the initial iteration of my artificial intelligence learning game platform. In this, there are three mini-games which allow the user to learn about various subjects using games. The design of the system has been done by utilizing Claude AI, and the Groq API has been incorporated in the system for generating learning material via their free API key.

The concept behind the development of the system is that any subject inputted by the user will be converted into a gaming platform to teach him about it. However, currently the system is fully functional but the aesthetic design requires improvements.

Today I finished the final improvements to Astronasamp. I cleaned up the README to make the setup instructions easier to follow, added screenshots showing the bot in use, and improved the testing scripts. I also updated the stress test and smoke test so they provide clearer output and make it easier to verify that every command is working correctly. After that, I committed the final changes to GitHub, checked that everything was pushed correctly, and reviewed the project one last time to make sure the documentation, code, and repository were ready for submission. At this point, the project is complete and ready to submit.