Time limit: 2–3 hours max.
You are given a small set of base assets for a fictional indie game — Hollow Crown by Twin Hearth Studios — in /assets/sample-game/. Open STYLEGUIDE.md there for the full brand spec.
Build an AI-powered workflow that takes those base assets and automatically generates a varied set of marketing assets across multiple formats, staying on-brand.
-
Input: the base assets in
/assets/sample-game/(logo, key art, characters, icons, pattern) + theSTYLEGUIDE.md(palette, tone, do's and don'ts). You may upscale, restyle, or re-illustrate them with AI — the assets are intentionally simple so you have room to be creative. -
Output: at least 20 generated assets in
/output/, covering at minimum:- 1:1 (Instagram feed)
- 9:16 (Stories / TikTok / Reels)
- 16:9 (YouTube thumbnail / banner ad)
- A wildcard format of your choice (animated, carousel, gif, short video, etc.)
-
The workflow must be reproducible. Someone else should be able to clone the repo, run your script/workflow, and regenerate the assets. No "I made these by hand in Photoshop".
Use whatever you want — and combine freely:
- Image gen: Midjourney, DALL-E, Stable Diffusion, ComfyUI, Replicate, Nano Banana, Flux, etc.
- Orchestration: Python scripts, Node scripts, n8n, Claude Code, ComfyUI workflows, Make, Zapier.
- Editing/composition: Photoshop scripting, Figma API, Canva API, Pillow, Sharp, etc.
Brand consistency at studio level, A/B testing infra, publishing automation.
Include a file documenting:
- The workflow: diagram or step-by-step of how an asset goes from base → final.
- Tools used and why.
- Prompts (image, text, system) you used. Paste them in.
- How you would scale this to 50+ assets per game and to multiple games per week.
- One failure case you ran into and how you handled it.
| Area | Weight |
|---|---|
Reproducibility of the workflow (PROCESS.md + runnable code) |
30% |
| Visual quality and variety of generated assets | 25% |
| Creative use of AI tools (not just one-shot prompts) | 20% |
| Scalability thinking (how this becomes a pipeline) | 15% |
| Documentation clarity | 10% |
- Fork this repo.
- Create branch
submission/<your-name>. - Commit your code/workflow + the generated assets in
/output/. - Open a Pull Request to
mainof this repo. - In the PR include: time spent, how to run the workflow locally, trade-offs made.