Build Worlds With AI
Chapters8
The creator explains the goal of building a cohesive universe to house artifacts, lore, and regions for their artwork.
HashLips Academy demonstrates a practical AI-powered worldbuilder called the Story Architect, turning fledgling world ideas into structured, canon-safe Markdown files for a cohesive universe.
Summary
HashLips Academy’s video showcases how the creator uses an AI tool called the Story Architect to turn scattered world-building ideas into a structured, codified universe. The host explains that the tool generates Markdown files, folders, and metadata to codify concepts like worlds, regions, artifacts, and inhabitants, while preserving existing canon. He walks through core ideas, templates, and the non-negotiable rules that keep classification and naming consistent. The demonstration includes defining a world named DIA, with a region called Cuckoo and sky-drifting inhabitants, illustrating how the output organizes lore into a scalable repository. Throughout, the host emphasizes the value of progressive enrichment, gap-filling, and targeted questions to flesh out missing details. He also notes practical tips, like keeping output under version control so you can review changes before accepting them. In sum, the video present a hands-on workflow for creators to build a coherent, expandable universe with AI-assisted worldbuilding that remains easy to navigate and update.
Key Takeaways
- The Story Architect skill converts fictional world ideas into structured markdown files with a clear naming scheme and canonical safeguards.
- Output is organized into MD files inside folders like world, region, and inhabitant, with metadata fields such as category, name, and parent region.
- The workflow includes canon checks, gap filling, and progressive enrichment to keep lore consistent and expandable.
- Demo world DIA is created with a region Cuckoo and sky drifters, illustrating how themes like levitation and mystical powers are captured in structured concepts.
- Non-negotiable rules push for consistent metadata and category-specific templates to ensure uniformity across artifacts, regions, and cultures.
- Future work suggested includes using version control to review AI-generated changes before merging into the project.
- The tool encourages targeted questions to fill missing details rather than forcing all information at once.
Who Is This For?
This is essential viewing for indie worldbuilders and NFT/artists who want to scale lore around visuals with AI-assisted structuring. It’s especially helpful for creators who need a repeatable, canon-safe workflow to organize artifacts, regions, and cultures.
Notable Quotes
"The best way of doing this is if you see the video, go to the exact version 1.0.2."
—Highlighting the exact version of the skill to use for consistency.
"The skill starts off I just gave it a name story architect a description converts fictional world ideas into structured law records with correct classification schema naming and canon safe progressive enrichment behavior."
—Describes the core purpose and features of the Story Architect.
"Basically the skill that helps creators or authors or writers just flesh out concepts of their story."
—Simple summary of what the tool does for writers.
"And what we start off with is giving it its core responsibilities and then also core workflow."
—Outlines how the tool is defined and used.
"It should follow the schema naming and templates and protect existing cannon while allowing safe metadata enrichment."
—Emphasizes canon safety and data consistency.
Questions This Video Answers
- How does the Story Architect ensure canonical consistency in AI-generated worldbuilding files?
- Can I use version control to review AI-generated worldbuilding outputs before merging?
- What metadata schemas are used for worlds, regions, and inhabitants in HashLips Academy's Story Architect?
- How does progressive enrichment fill gaps in worldbuilding lore?
- What are the best practices for organizing AI-generated worldbuilding outputs into folders and MD files?
HashLips AcademyStory ArchitectAI-assisted worldbuildingWorldbuilding workflowMarkdown archivesCanon safetyProgressive enrichmentStructured data for fictional universesDIA universeCuckoo region
Full Transcript
Hey, how's it going guys? Welcome to the video. And I'm very excited for this one because over the weekend I decided to start making a universe, a fictional world that my artworks can play a role into. For the longest time, I've always created interesting works that cannot really be explained by itself. For example, these figures staring at each other or some of my latest work which contains the Buha silhouettes which are these figures floating in space. And I thought to myself, why not make a universe, a world where all these artifacts, storylines, regions all form a part of.
That way I can add more lore to my artworks and what I do. Seeing that all of this stuff is happening in my head, I might as well write it down. However, I'm not a very good writer or author, and I needed something that can help me put my ideas into a structured uh law or story or world schematic, if you want to call it like that. So, what I've made is an agent skill, which you can find if you go to this link. I'll put it in the description, and you can find it here.
story architect skill which we'll be covering in this video today. The best way of doing this is if you see the video, go to the exact version 1.0.2. The skill is in development, but it is usable. So, I'll be using it already to flesh out the world. Now, I'm very excited to dive into this video and start building out a world, but I first want to go and show you the skill. All right. So, if you are not familiar with skills, please watch some of my previous videos where I speak about skills from the ground up.
Now, I will just go over the skill itself. So, usually you will put this skill in your configuration file for whichever agent you use. However, I've just got them listed here. You might see some skills like the deb art skill that you won't find in that repo, and that's because it's private, but the one we are focusing on is the story architect skill. And as always with these open-source skills and tools, you can always customize it yourself. If you feel like you need some more functionality that is not in the skill then please add it and make it your own.
So basically the skill starts off I just gave it a name story architect a description converts fictional world ideas into structured law records with correct classification schema naming and canon safe progressive enrichment behavior. Use it when the creator describes new law concepts, ask to organize or expand the world repository and so on. Basically, this is a skill that helps creators or authors or writers just flesh out concepts of their story. It's kind of like creating a mind map of ideas and concepts, myths, rumors, regions, and uh inhabitants of this world where the output is then a very nice concise uh file structure of MD files containing these concepts.
The skill also has the ability to tell your agent to fill in some of the gaps. Maybe you've written something about a story previously and there was some unknown areas such as the parent region or what type of culture exists with this artifact and then it can go and fill in the gaps as well. Well, at least that's what we're trying to build out here. So, now that you roughly know the idea, let's go over the skill itself. So, here in the main skill.md file, we've got a few instructions. So we define what the agent should act as.
So we tell it that it should be a story architect of a fictional universe. Its role is to help the creator design and organize and explain a fictional world using structured markdown files. And what we start off with is giving it its core responsibilities and then also core workflow. The responsibilities would be to interpret creator ideas, specify each concept correctly, generate structured markdown files in the correct folders, and just as I go through this, the whole skill has been designed to keep consistency in mind, right? We want consistent metadata for all of these artifacts and regions and so forth that we add.
Next, it needs to keep the law consistent with the existing cannon. It should not change things really what already is existing. However, later on, I'll show you how it will be able to update metadata pieces to make the story flow and to connect the dots. It should follow the schema naming and templates and protect existing cannon while allowing safe metadata enrichment. And then for the core workflow, it basically just talks about what it should go through its thinking process. So we should understand what the ideas uh represent. Uh run the canon check. So run it against all the existing entries that's come before it.
Classify the concept. uh decide if one or multiple files are needed because sometimes you might be explaining a region that has uh a few artifacts in it and inhabitants and then obviously it needs to make multiple files. Then we also wanted to ask minimal targeted questions if something is missing. It needs to generate files using the required schema and templates. Very important for consistency. And then enrich existing files when newly provided Canon fills the missing metadata. All right. Then we give it some non-negotiable rules. Now I'm not going to go through each and every file.
Of course, you will have access to all of this. But the non-negotiable rules are the classification, right? infer the correct categories are used and then we give the categories MD file in the references folder. So here we can see uh these are all the categories. We get categories such as world, region, rule, inhabitant, artifact, phenomenon, culture, symbol. So I can go on but there are these defined categories that it should adhere to. And then it just briefly speaks about the multiple concept rule. It talks about the gap filling rule asking some questions and then also the canon check rule just to check uh if there are any other references.
Then here is where the progressive enrichment rule helps us. So basically, if something is missing from some some concept that you've explained previously and you mention it later on, it can go back and suggest an update or actually fill an unknown piece of information, which is really nice. And then we've got our references files. So things like the structures, the templates, naming, uh placement, and status. And these we just have as references for it to check on. So the first one would be let's go to the structure which would be in this schema and here you can just see that it talks a bit about the metadata of these files.
Each file will have a name and that is defined by the naming convention. So we'll use this kebab case and inside there the files will have these specific metadata pieces like category, the name, region, parent region and this is all to do with story building or world building and it explains what each one of these fields are. Now, of course, for each one of our categories, such as a rule, an inhabitant, an artifact, there's different templates that goes with these schemas. And that we can find in the templates file. And here it just explains roughly what type of metadata belongs to one of these categories.
And then apart from just defining the metadata, we also have a bit of the actual u thing that you are explaining itself such as the overview or notes or descriptions or story. So that gets added to the files too. And lastly in the hierarchy.md file you can see the output format. you'll be uh left with a bunch of these folders and inside you'll have these MD files explaining the pieces and ideas that you ask the agent to build out. Now, let me go and show you what this can do. I'm going to close this off and copy the story architect skill and paste it in here my cursor skills folder.
This is so that cursor can actually pick up the skill and make use of it. And I'm going to generate things in the output folder. So on the right hand side I can just ask let's define the story or a world or universe. Make use of the story architect skill. And the first thing I want to define is basically the actual world itself. Let's call this world DIA. In this world, there are many different realms or in these realms as well, some regions. And one of the regions that exist in this world uh would be called cuckoo.
and the cuckoo uh region inside of there they are inhabitants that float in the sky and these are known as sky drifter sky drifters. These sky drifters they are these entities people floating in the sky interacting with one another and no one really knows why they are there. It's a mystery to this day. One thing they do know is that they've got mystical powers and no one has interacted with these sky drifters before. Okay, let's see what it does and outputs. I just had to think about that right now. Um, so if it didn't make sense, that's all right.
I just want to see that it can build out the structure for us and define the concepts that I was just speaking about nicely in the output folder. Um, one way that I would recommend using this is to actually start up a new repo and add the skill and then use it to update things because with uh source control you can actually see what update it's going to make and then accept it or not. Right? So we can see that it's already thinking through the process. It in the output folder hopefully is going to create this.
I can see there's a file called idea and its category is world with a name. So let's just give it a second for it to complete the rest. All right. And it's done. Now it did not place this in the output folder. instead it just placed it um here directly in the root directory. So a good idea would just be to um specify where it should place these. But we've got the folder inhabitants. We also have regions and we have world. And inside of world, we can see that we've got category world, deer, related is cuckoo, sky drifters, uh mystery realms, mythical powers, right?
Mystical powers. And here it explains basically what we just explained right now. Here in cuckoo we can also see that this is a region itself forms part of dia and explains what cuckoo is. Now of course you need to be a bit more explanatory and and and have more creativity to each one of these and you don't have to do like let's say all three at one go explain inhabitants and all these things. you can take it slow and thoroughly think through what you want to actually uh portray. Then we also have the sky drifters.
One thing I just want to show is that it correctly categorized deia as world, the cuckoo as a region and then sky drifters as an inhabitant and explains things like the themes of them, levitation, um mystical powers, uh the things that we just spoke about where it's related as well. So I think that if you are building out some sort of universal world in in a fictional story, I think this skill might become very useful and you can now go and continue and you know write out and define this this world that you are building.
And I think it's fantastic that we have AI to be able to help us in these specific ways. So I'm going to leave it at that. I'm going to go and now start building on the story, the actual story. But I wanted to give this skill to you to try out and have some fun with because I think it is really fun when you start getting into world building. And hopefully this is a tool that can save a lot of time and really make a good effort toward towards world creation in a very nice consistent way.
So I hope you enjoyed the video and I'll see you in the next one. A cheers for now.
More from HashLips Academy
Get daily recaps from
HashLips Academy
AI-powered summaries delivered to your inbox. Save hours every week while staying fully informed.



