I've been making music for a long time. Half finished projects, songs that lived on hard drives and never saw the light of day. A lifelong passion for video games and a head full of game ideas that never quite made it off the drawing board. The usual story.

EYEBROWZR started as a way to stop overthinking and just ship things. Give it a name, give it a face, separate it from my ego enough that I could actually put it out into the world without second guessing every decision.

What started as an alias became something more — a brand, a persona, an aesthetic. A lens that everything passes through. The music sounds a certain way because of it. The games look a certain way because of it.

What you're looking at now is an artistic playground and a carefully constructed ecosystem — music, art, and games feeding into each other, one project fueling the next.

Stick around, the adventure is just getting started.

I'd like to establish upfront that I depend on AI for this project. I've built it into my workflow and without it, EYEBROWZR would not have come this far. I even used it to help me organize my thoughts before writing this entry — ironically. That said, people have different levels of comfort when it comes to using AI as a creative tool. Some embrace it fully, others avoid it entirely, and everything in between. I think all those positions are valid, but from the discourse I've seen online, I felt it necessary to be fully transparent with how and why I use it for EYEBROWZR. I try not to be careless with my usage, and from the outset I carefully considered where I would draw the line. I'm not here to tell anyone where to draw their own line, and I am fully willing to re-evaluate my own stance as I continue to learn more about AI and its impact on things beyond my own life.

I use Claude AI as a co-developer, a research assistant, and a web/game developer, where I have the final say in all decision making. All the music you hear on this website, the pixel art and animations you see, and the rules to the games you play were completely wrought by me, down to the last pixel and sound.

Claude has had an influence on how I decided on color schemes, the aesthetic, and acted as a creative sounding board to help me reach decisions on how I want a game mechanic to function — but it's all from a place of drawing from other sources of inspiration, no differently than I would on my own. That's the research assistant side of my AI usage.

The HTML of this website was almost entirely generated by Claude. I am not a software or web developer, and for me to have created the same thing on my own would have taken years. I fully acknowledge that software development can be a form of art in itself, but that's not the focus of my art. I view this website as a museum — the exhibits inside are the art I want to share. The building they live in was contracted out and created by something else, with my oversight. This paradigm extends to the web and mobile games I am developing — the code is generated by Claude while I tell it exactly how it should function and the rules. The experience is curated by me, but I rely on AI to execute that vision.

What you see, hear, and interact with on this website came from me. AI is simply the tool I use to help get it here. That feels like the appropriate separation — I am the artist and game designer, AI assists with but does not replace that.

Lastly, this is a solo passion project. I have no intention of monetizing EYEBROWZR. I don't have the means of hiring a team to serve the same purposes as Claude. If I were profiting from this, I would probably reconsider how I depend on AI.

I hope my views resonate with anyone reading and can illustrate just one of the many ways AI can be used to build confidence in hobbyists who might otherwise never have executed on their creative visions.