Creator Spotlight: Christian Smooth Was an Author Before AI Entered the Story

Creator Spotlight · First Look

The easiest way to misunderstand Christian Smooth’s latest project is to start with the AI. Start with the author instead.

Before Mr. Illustrious became a browser game, before Claude and ChatGPT were part of the workflow, and before 3D generators, Blender pipelines or AI-assisted debugging entered the picture, Christian had already written the story. He first began Mr. Illustrious at 19, expanded it from a story written for a friend into a series, and later self-published the work in 2014.

More than a decade later, the interesting part is not that Christian found a new piece of software. It is that he became a different writer. By spring 2025, he no longer felt the published version represented him, so he removed it from Amazon and began rewriting it from the ground up.

Writer, filmmaker, visual storyteller

Christian describes himself as a filmmaker, visual artist and author, and he founded Smooth House Productions around the larger goal of creating and producing stories. His work has moved through writing, filmmaking, photography and now interactive storytelling, which makes the visual novel feel less like a sudden pivot and more like another format for the same underlying instinct.

That matters because creators often meet AI at exactly the wrong point in the process. They begin with a tool and ask it to tell them what to make. Christian approached it from the opposite direction: the characters, tone, period, soundtrack and narrative already had somewhere to come from.

A 2009 story needed a 2009 visual language

Mr. Illustrious is set in 2009, and Christian deliberately resisted making the game look like a glossy modern production. PS2-inspired character models, bold menus, R&B music and arcade-style minigames became part of the art direction. The limitations are not hidden; they help define the world.

That is one of the reasons this project caught my attention. Technology gives creators endless opportunities to add polish, but polish is not the same thing as direction. Christian had enough of a point of view to decide when a technically “better” result would actually be worse for his story.

The AI did not get a free pass

His contributed article is candid about what failed. ChatGPT’s first attempt was not fun for him. Claude produced stronger environments but struggled with characters. Mature material from the manuscript was sometimes softened or sanitized. Mobile controls broke. Rhythm-game inputs failed. A fight that worked on desktop struggled on phones.

That is the version of AI-assisted creation I want more people to document. Not just the impressive output, but the judgment required to reject an output, identify why it failed, move the task to another tool and test the result with actual people.

Christian’s most useful observation came from playtesting: code can technically work while the experience still fails a human being. His players found problems that code review alone did not. That is not a small footnote to the process; it is evidence that human feedback remained part of the production system.

A creator directing departments

Christian’s production pipeline eventually spread across several specialized tools. Image generators helped with character concepts. Meshy helped turn visual references into 3D assets. Mixamo handled rigging and animation. Blender became part of a scripted process for stabilizing and compressing models. Claude and ChatGPT were used differently at different stages, including integration and debugging.

His own metaphor is the best description of the process: it felt like working on a film set. He remained the writer, director, editor and tester while the tools behaved more like departments. They could contribute useful work, misunderstand an instruction or fail at a task, but none of them replaced the person responsible for deciding what belonged in the final project.

Why I wanted Christian to write this in his own name

When Christian first contacted me, he pitched a practical creator-journey article. I could have interviewed him and retold the story from the Jack Righteous perspective. I think that would have been weaker.

He lived the process, and he had already done the work of thinking about what other creators could learn from it. So his companion article on this site is not a quotation roundup or a profile written over his shoulder. It is published under Christian Smooth as the actual author.

That distinction matters to me. If Jack Righteous is going to make room for outside creators, the site should clearly tell readers when the words and experience belong to the contributor.

Try the work, not just the story about the work

The strongest thing Christian can offer readers at this stage is something many creator spotlights cannot: there is a project you can actually try. The free browser version of Mr. Illustrious: The Visual Novel adapts the first four chapters and includes narrative choices alongside rhythm, driving, running and fighting gameplay.

Reader note: the project contains mature adult themes, strong language, sexuality and violence.

First-look verdict

I am still spending time with the full interactive experience, so I am not treating this spotlight as a final game review. What I can say already is that Christian’s creator story is worth following because the order of operations is right: he had something to say, built a body of work around it, became more demanding of his own writing and then used new technology to push that work into another form.

The tools are interesting. The mistakes are useful. The workflow is worth studying. But the reason I wanted to introduce Christian Smooth to Jack Righteous readers is simpler: there is an author underneath all of it, and the technology is being asked to serve his story rather than replace it.