AIBuiltProjects.com did not begin because I wanted another general website about artificial intelligence. It began because the projects were already accumulating and I needed one place where their real stories could live together.
The first important project was Gem Forge Idle. I began it as someone who had never built a game before. At the start, I kept ChatGPT open beside Unity. I explained what I wanted, copied the code into Unity, returned with errors or changed ideas, received revised code and pasted it back again. It was slow, repetitive and sometimes confusing, but a real game gradually appeared.
That process changed later when I began working with Codex more directly inside the project. By then, the idea had grown beyond a single game. Swarmloom Idle followed, my long-running photography website GottaPics became an AI-assisted rebuild, and Chaos Booth turned an application idea into a working Android project. Each one had its own history, decisions, mistakes and milestones.
The projects needed their own home
GottaPics was not the right place for all of this. It is a photography website and I want it to remain focused on photography. Publishing development diaries about idle games, WordPress experiments and a photo challenge application there would confuse both readers and the purpose of the site.
I therefore needed a separate home for the building process itself. Not a portfolio containing only finished products and not a stream of generic AI news. I wanted a site where a project could begin as a rough idea, change direction several times, reach testing, get rejected or approved, attract its first users and continue evolving in public.
That became AIBuiltProjects.com. The name is deliberately straightforward. These are projects built with AI assistance, but they are not projects created without human direction. I choose what to make, test the results, reject what does not work and decide what stays. The site records that collaboration instead of pretending either side worked alone.
Not a promise that every experiment will succeed
One of the most important decisions was not to design the site as a collection of guaranteed success stories. Some projects may attract players or visitors. Others may remain small. A feature can sound sensible and still fail in practice. A game can be published and receive disappointing ratings. A website can improve technically and still need months to recover traffic.
Those outcomes are part of the subject. If I only documented the polished ending, I would lose the useful part: how the project changed and why. The articles are therefore written from my perspective and tied to real screenshots, builds, store submissions, statistics and corrections whenever those are available.
This also explains why every major project has a permanent parent page. The page gives a visitor the stable overview: what the project is, how it works and where it currently stands. Blog posts then record individual chapters—an early prototype, a change in direction, a publication milestone or the first feedback from real users.
Games, websites, applications and tools
The main Projects area is divided into clear families. Games include projects such as Gem Forge Idle and Swarmloom Idle. Websites include the GottaPics rebuild and AIBuiltProjects.com itself. Applications include Chaos Booth, while the tools area is available for projects that do not fit naturally into the other groups.
This structure matters because the site is intended to grow without becoming a single long list. Someone interested in one game should be able to reach its page and then find the connected articles. Someone interested in website experiments should not have to search through every game development post.
Why the website belongs inside its own project list
AIBuiltProjects.com is not merely the container surrounding the other work. It is one of the experiments. The domain was selected, the WordPress site was structured, the homepage was designed, menus were revised, legal pages were organised and the visual identity was developed with AI assistance under my direction.
The site also creates measurable questions. Can a completely new domain gain search visibility? Will connected project pages and honest development articles help people understand the work? Can the site remain useful as the number of projects grows? Those questions can be answered over time using real evidence rather than assumptions.
That is why the website has its own permanent AI Built Projects page and its own category under Websites. This article is the beginning of that record. Future posts can document the construction, the mistakes, the technical repairs and the traffic results without crowding the project overview.
The principle I want to keep
The rule is simple: the work must remain real. AI can help me move faster, organise information and implement changes that I could not easily make alone. It can also misunderstand instructions, produce the wrong structure or solve one problem while creating another. My role is not hidden by that process; it becomes more visible because every important choice still needs judgment.
AIBuiltProjects.com exists to preserve that whole process. It is the project about the projects, but it is also a test of whether a website created from the beginning through human direction and AI assistance can build an audience of its own.
Leave a Reply