---
title: "My Process - Creator Exchange - Yumina Community"
description: "I've had a few people asking, so I wanted to share my process for making cards. Hopefully a few creators find this information useful."
url: https://yumina.io/app/community/thread/0c540902-31b4-4147-863c-df092f972235
lang: en
---

[Community](https://yumina.io/app/community) · [Creator Exchange](https://yumina.io/app/community/creator-exchange)

# My Process

[Jon](https://yumina.io/@jon) · 2026-10-29

I've had a few people asking, so I wanted to share my process for making cards. Hopefully a few creators find this information useful. It might seem long, but I tried to be thorough without wasting time.

Step one is planning. Ask yourself questions like "how many characters" and "what is the theme". It really helps to have a clear vision in mind. Keep your idea manageable, and don't overwhelm yourself by trying to do too much.

Next, create your assets. For music, I use Suno but you can use whatever platform you like. Music can go a long way to setting the mood, but isn't required. I export mine as MP3 files.

I also like to create visual assets like backgrounds and character images in my cards. To create my images, I use Civitai to download models locally, and generate them on my computer using ComfyUI. I render backgrounds at 1920x1080, and character images at 1024x1536. If you're not familiar with prompting AI images, there are plenty of resources on Civitai that explain how it's done. You can also generate images here on Yumina if you click Create, then AI Generation.

I like to create my character illustrations with a blank white background, which I then erase in Clip Studio Paint, and save the file as PNG so it retains alpha channel transparency. This is so the characters can appear on top of any background. Some AI models can natively generate images with transparent alpha channels, and there are tools like Transparify that can do this for you.

I like to generate multiple images of my character so they can have different expressions. To do this, I recommend you have a very clear, specific description of your character's appearance, as AI has a difficult time with consistency. You can also use a LoRA of your character, either one made by the community, or one you make yourself. Then, in the prompt, I change the expression (smile, angry, sad) and leave all the other details alone. Getting good results takes several tries, which is why I like to do this locally.

When saving my assets, I clearly label them. "Motoko\_smile.png" is more useful than "33b6e4c6-3f47-415d-ac68-0.png" and will save you a headache later.

Once I have my assets ready, I start creating my card. I click Create, then Blank Project, then start with the Lorebook. Clearly label each entry so the AI has a good understanding of the purpose of each piece of information. I write one entry per character, then one entry for each location the player can visit. Then I create an entry outlining the Style Guide (how I want the AI to write responses), the Premise (what the central themes of the game are), and Content Rules (what content is and is not allowed in the game).

The next step is creating a good First Message. I like to set the scene, tell the player what they need to know about this world, and establish the vibe. I try to avoid making the First Message too long. Try to keep the writing style in your First Message consistent with your Writing Style entry, using the same formatting that you want the AI to use, as it will write future replies in the same style as your First Message.

Next, under the Assets tab, I create a folder with the same name as my Card, and I upload all the assets I've created to that folder.

Once I have all of this ready, it's time to create the UI and game mechanics. For this step I use the Creation Assistant. I know nothing about coding, yet using the assistant I am able to create visually appealing cards. When you click the Creation Assistant button in the top right corner, it will bring up the assistant panel. I like to use the default Claude Sonnet 5, but you're welcome to use whichever you prefer. One thing to note is that this step is not cheap. It uses a lot of Mushies. You have three options here:

Pay for the Mushies.

Use a Private API Key to use your own AI models.

Ask Yumina via DM for Mushies. This is what I did, and they were very generous and gave me enough Mushies to cover the cost of building and playtesting.

Prompting Claude is easy. Just write in plain language what it is you want to see in your game. Be as specific as possible. Give the AI a little bit of work at a time. Click Playtest in the top right corner to see how your game looks. Be sure to click both the Desktop Preview and the Mobile Preview buttons (top right of the Playtest field) to ensure your game looks good in both formats. Always playtest after every change to see if the AI did what you asked.

The AI can see your entire card, all entries, and asset folders. This is where clear labeling comes in. If you tell the AI to set your backgrounds, it will know that beach.jpg should display when the player is at the beach. The AI will also write Variables and Behaviors for you based on your instructions. The more information you provide, the better the AI will match your vision.

There is a toggle in the Creation Assistant prompt box for Plan and Build. Plan will tell you first what it plans to do and how many Mushies it will cost. Build just gets right to the building. I prefer Build, because in my experience, Claude is very good at coding what I wanted. It also helps to know some of the terminology around UI. If I don't know a term, I use Google. That way I can better describe my vision to the AI.

An example of how I would prompt is "I want the text bubbles to have rounded edges with a white border and a frosted background with 25% opacity." Once that's done, I playtest and if it looks right, I write my next prompt. "I want a large, rounded sans serif font with white text for prose and gold text for speech in quotes." Playtest again, and move on. "I want each background image to display when the player moves to that location, set for Beach, Spa, and Pool." Playtest. "Set images for each character to display on the left side of the screen in desktop mode, on top of the screen for mobile. Change expressions to match the character's mood."

Variables can track all sorts of things, from Player HP to Inventory. Don't worry if you don't understand how this works, the AI does and can create Variable entries for you. Just remember that the more complex your game is, the more chance something can go wrong. Your only limit is your patience (and Mushies).

You can also try to do all this yourself in the Canvas editor.

Once your UI looks the way you want, now it's time to playtest for balance. Edit entries manually or ask the AI to adjust until you get the desired behavior. Go back to Creation Assistant and explain what went wrong and what was supposed to happen. The AI is usually very good at finding and fixing mistakes. Playtest across multiple models, and try to break your game. Your players will do unexpected things, so try to anticipate what might go wrong and see what happens when they do. Then fix it. Don't try for perfection, but make a reasonable effort to make your game playable across as many models as possible.

Once your game looks and plays the way you want, it's time to fill out the Overview and Publish your game. I try to use an eye-catching Cover Image and Gallery Images to show potential players what they can expect. Write a good description, something that tells players the premise, what they can expect to find in the game, and a quick outline of some features that make your game stand out.

And that's it! I hope some creators find this helpful, and if anyone has any questions, I'll try to answer them in the comments. If anyone has any advice they'd like to add, please share here. Thanks!

If you want to check out some of my games, click my profile. My games are intended for adult audiences and are labeled Limitless.
