Gillex

🚨 Steps 1 Get your specs. Download CPU-Z and screenshot the CPU, Mainboard, Memory, and SPD tabs. Note your GPU, cooler, PSU, monitor refresh rate, and Windows version. 2 Know your problem. Which games, what resolution, your current FPS and 1% lows, and what's wrong (low FPS, stutters, input lag, crashes, temps). 3 Take a baseline. Run a game's built-in benchmark or the same 60 second scene with CapFrameX or PresentMon. Keep HWiNFO open for temps and clocks. Write the numbers down. 4 Back up first. Make a Windows System Restore point. In the BIOS, save your current settings as a profile and look up how to clear CMOS on your board. 5 Windows changes. With Claude Code, it can check startup apps, background processes, power plan, and drivers from the terminal and make changes. Read every command before approving it. With regular Claude chat, send screenshots of Task Manager's Startup tab and make the changes yourself. 6 BIOS changes. Claude can't touch your BIOS, so send photos of each screen (F12 saves screenshots to USB on many boards). Ask about XMP/EXPO, Resizable BAR, PBO/Curve Optimizer (AMD) or power limits/undervolt (Intel), and fan curves. Keep Secure Boot and TPM on for anti-cheat. One change at a time, then boot and test. 7 Keep a change log. Have Claude write down every change and how to undo it. 8 Verify. Rerun the same benchmark from step 3. For RAM or CPU changes, run the stability tests Claude suggests and check Event Viewer for WHEA errors. 🚨What Claude can do on its own • Pull your specs without CPU-Z: CPU, motherboard, BIOS version, RAM kit, GPU, drivers, Windows version. • Catch BIOS problems from Windows. It can't change the BIOS, but it can check whether XMP/EXPO is on (RAM running at rated speed vs default), whether Resizable BAR, Secure Boot, and TPM are enabled. So it can tell you exactly which BIOS settings need fixing before you even reboot. • Make a restore point and keep the change log as a file. • Windows tweaks: startup apps, background processes, power plan, GPU driver check. • Run tests: CPU benchmarks and stress tests, temp logging, and checking Event Viewer for WHEA errors. • Write a revert script that undoes everything it changed. Still on you • BIOS changes. You reboot, change the settings, and come back. Claude then verifies they took effect. • Playing the game for in-game benchmarks. It can start the frametime capture, but you have to play the scene. • Approving commands. You can let it run without asking, but for system changes I wouldn't. Reading each command is your safety net. 🚨Prompt Help me optimize my gaming PC. My specs are in the attached CPU-Z screenshots. GPU: ___. Cooler: ___. Monitor: ___Hz. Windows ___. I play ___ at ___ resolution and get ___ average FPS with ___ 1% lows. My problem is ___. I've already tried ___. Go one change at a time, starting with the BIOS. For each change, explain why it matters, how to undo it, and how to test it. Tell me if anything lowers security or could break anti-cheat. Keep a running log of every change we make.

I see people trying to get into content creation every day. But so many people fail to realize that your contents success is based off of how valuable it was to the viewer. Ex. Don’t buy mini DJI mics and only post GRWM content. Because.. who the fuck cares about you? So many creators have bias towards themselves. You’ll find more success if you view your content through the lens of a random person who doesn’t know you.