Illustrated portrait of the Lily Fernwild persona with her pet rat

Design Portfolio · Fernwild Studio

Lily Fernwild

AI visual design, illustration direction, and creative direction for games, made with a writer's eye for clarity.

I take ideas from a blank page to finished, published work: illustrated music videos, animated shorts, YouTube key art, and the creative direction of a mobile game. I work in generative AI tools every day, and the job is mostly judgment. I keep a look consistent across a whole series, notice when something doesn't land, and give clear notes until it does.

Pantheon of Aspects: a dragon over a sunset valley with bear, wolf, tiger, heron, fox, and boars
The pantheon fresco from Pantheon of Aspects, the animal gods of an original fantasy world
  1. Pantheon of AspectsMythic fresco short · art direction
  2. Be the HeroEnsemble music video · story direction
  3. Tales from the FernwildsAnimated shorts · same world
  4. Fixing what came out wrongCorrections · notes
  5. Black Hole InvadersGame direction · cutscene
  6. Directing game feelAudio & state changes
  7. Design notes from the BuildLayout · menus · HUD
  8. The 23rd Psalm & hymnsCharacter consistency
  9. Music video key artStyle range · typography

Art direction · Style guide · Mythic short film

Pantheon of Aspects

A 2–3 minute mythic short about the Aspects, the animal gods of an original fantasy world I created with friends. It's based on fables I wrote for that world.

The picture in my head: titans striding over mountains, with forests brushing their bellies. The film opens on a pan across a pantheon fresco, then gives each Aspect its own moment. Every Aspect card pairs a still with a five-second animated shot, and the Aspect's name and domains sit in two lines of elegant medieval-renaissance title text. I chose a camera angle for each animal.

Role
Concept, source fables, style guide, prompt direction, edit
Tools
Nano Banana 2 (keyframes), Grok Imagine (animation), Seedance (card shots), Suno (score), DaVinci Resolve (edit), Cinzel Decorative (end titles)
Watch
youtu.be/hCXrZEPf12w

My direction notes

The style

Stylized mythic fresco: saturated colors, a sunset with deep shadows and sharp highlights, and outlines slightly broken and time-worn but still legible.

Later I pushed it further toward medieval and renaissance outlining and brush strokes, cracked plaster, and an epic titan scale.

Cards that stay on-model

“Lock style of start frame. No music, no soundtrack, no voices, only sound effects.”

Every card's video prompt opened this way, so each five-second shot matched its still and left the score to Suno.

Fixing the Stag

More weathering, less misty and dim. A crown of stars with faint planet outlines, and an eye that sparkles like a star.

The first Stag came out too misty and dim, so I gave revision notes to bring it in line with the fresco look.

Finishing

A Suno score, the full cut in DaVinci Resolve, and end titles set in Cinzel Decorative.

I cut the film and set the end titles myself.

Music video · Ensemble cast · Story direction

Be the Hero

A four-minute fantasy music video for my song Be the Hero: three adventuring parties, more than a dozen characters, and one story told across the verses, choruses, bridge, and a dragon fight.

It opens in the real world. My friends from the AI space live their everyday lives in the first verse, then gather at a game master's table for a tabletop session. The chorus pulls them into the fantasy world. A second party meets at a tavern called the Blimey Swill. My own party, led by Lily, crosses paths with the heroes in the second chorus. The parties split up, travel separately through the bridge, and come together for the dragon battle. The finale returns to the tavern, then back to the game table where it all started.

Role
Song, story, character direction, shot plan, prompt direction, edit
Tools
Suno (song and V2 remaster), Nano Banana 2.1 in OpenArt (keyframes), Seedance 2.5 (57 clips), Grok Imagine (7) and Kling 3.0 Omni (3) for the 67 animated clips, Video2x (upscaling), DaVinci Resolve 21 (edit)
Watch
youtu.be/QARqKKTdLYY

My direction notes

One story, three parties

The song structure became the story structure. The opening instrumental introduces one party. The first verse and prechorus introduce characters in the real world gathering around a game table, then the first chorus pulls them into the world. The second verse is a roll call of classes across three different parties, and the second chorus introduces the third party together. The remainder of the song shows the three parties exploring the world, fighting a dragon, and all joining up at a tavern as the song closes, with a final scene back at the game table.

A shot plan with IDs

I wrote a shot plan that gives every beat an ID: V1, P, C1, R, C2, B, X, F. Every keyframe and clip is named by its shot, so dozens of generations stay organized and the edit goes together in order.

One house style

The same tested style block goes at the end of every still prompt: rough, bold inking, cel-shading with painterly strokes, and high-contrast lighting with grain. Three parties made at different times still look like they live in the same world.

Animated shorts · Same world · Series

Tales from the Fernwilds

Animated shorts from a world of heroes, taverns, and weird creatures, set in the same fantasy world as Be the Hero. Go be a hero!

Each short opens with a 20-second series intro that introduces one of three parties every five seconds: the Cookie Sisters, the Crimson Raiders, and the Lantern Bearers. Episode 1, Meet the Cookie Sisters, is out now. Five friends are preparing to go to the fair when a cookie mishap grows a prize pumpkin huge, and Lily's rat Blueberry eats a crumb in the stinger. Meet the Lantern Bearers is in production, and a Crimson Raiders episode is planned next.

Role
Story, character direction, prompt direction, music, edit
Tools
Gemini / Nano Banana (keyframes), Grok Imagine (image edits and video), Seedance 2.0, Seedance 2.5, and MiniMax H3 (video), Suno v6 (music), Audacity (audio remaster), Video2x (upscaling), DaVinci Resolve (edit)
Watch
youtu.be/FcFAlwlYIG8

My direction notes

Three parties, one intro

A reusable 20-second intro presents the Cookie Sisters, the Crimson Raiders, and the Lantern Bearers in turn, one party every five seconds. It became the opening for the series.

One cookie, one pumpkin

Meet the Cookie Sisters follows five friends getting ready for the fair. A cookie mishap grows a prize pumpkin huge. The stinger is Lily's rat Blueberry finding a leftover crumb.

The same house style

The shorts use rough, sketchy bold inking, cel-shading, chunky black outlines, and vibrant color, so they sit in the same world as Be the Hero. Each party has its own accent: green for the Cookie Sisters, crimson for the Crimson Raiders, and amber for the Lantern Bearers.

Case study · Be the Hero

Fixing what came out wrong

A big ensemble cast breaks AI tools in predictable ways. Characters change size, species, or color. Pets wander off. Objects multiply.

Here are the problems I ran into making Be the Hero and how I fixed each one.

The ogre turned green

Problem: Naming a character's species pulled in the model's stock version. The ogre came out green, and animal-folk characters like the hedgehog bard shrank to pet size or changed color.

Fix: Describe the features instead of naming the animal, and let the attached character sheet carry the species. In the ogre clip the running also looked wrong, so I changed the prompt to a single forward lunge from the melee fighters.

Before: The ogre came out green
Before
After: The ogre at his proper skin tone as the melee fighters lunge forward
After

Tall characters kept shrinking

Problem: When a tall character fist-bumped or healed a short one, the model shrank the tall one to match.

Fix: Anchor both heights with landmarks, like “head at her shoulder” and “full adult human height.” For sizes that kept slipping, I attached a height chart with both characters standing on one baseline.

Before: The tall character shrank to match during the fist bump, and the hedgehog bard came out too small
Before
After: The full party with the fist bump at correct heights and the hedgehog bard at his proper size
After
Before: The hedgehog bard shrunk too small beside the party
Before
After: The hedgehog bard at his proper size beside the party
After

A “huge” dragon that wasn't

Problem: “Huge” means nothing to an image model.

Fix: Give scale in things the model can measure: as long as three cottages, with its back at rooftop height.

Before: The party poses in the village with a defeated dragon barely bigger than the heroes
Before
After: The same victory scene with a huge defeated dragon, two heroes standing on its back
After

Extra tails and wrong outfits

Problem: Small continuity slips in otherwise good frames: an extra tail, a costume detail, a pose that pointed the wrong way.

Fix: A targeted edit (“keep everything the same, change only…”) instead of a reroll. It costs less and keeps the rest of an approved frame. One limit I learned: resizing a character by edit usually fails, so size problems go back to the prompt.

Before: The fox-eared healer with an extra second tail
Before
After: The same healing scene with one tail
After

The owl that hovered

Problem: A vague direction like “circles above” left the snowy owl hanging in midair, and pets drifted off their owners' shoulders.

Fix: Say exactly where each animal stays, like “the lemur stays on his shoulder.”

Two bottles

Problem: Throws and hand-offs made objects multiply. A bottle and a sausage each turned into two.

Fix: Keep objects in one character's hand, or swap the grab for a bite.

A charge that looked like running away

Problem: With the heroes facing the camera and the burning village behind them, charging forward read as fleeing. Once the first keyframe was animated, the heroes looked like they were running away from the fight.

Fix: Reverse the shot: show the heroes from behind, running toward the village, so forward motion points at the enemy.

Before: Three heroes run downhill toward the viewer with the burning goblin village behind them
Before: animated, they seemed to flee the village
After: The same three heroes seen from behind, running toward the burning village
After: from behind, running toward the village

Scenes that came back different

Problem: When the story returned to the tavern or the game table, the room, the seating, and the light didn't match.

Fix: Attach the approved keyframe as a reference, and match the time of day from the earlier clip. Lighting continuity matters as much as where people stand.

What these notes show

Words carry defaults: a noun brings the model's stock picture with it, so describe what you actually want.

Measure, don't adjective: heights and sizes hold when they're tied to landmarks.

Fix the smallest thing: edit the one mistake and keep the rest of an approved frame.

Check it in context: continuity, lighting, and direction only fail once shots sit side by side.

Game creative direction · Art direction · AI-assisted development

Black Hole Invaders

A mobile arcade game I directed using Grok Build, an AI-assisted development tool. You steer a black hole, eat alien ships, fill the power bar, and fire a gravity beam at the mothership.

I set the concept, the look, and the feel, and steered development through Grok Build with direction and revision notes. That covered the retro chrome logo and key art, the enemy and boss designs, the neon menu and HUD style, the sound and music, the screen-by-screen layout and menu rules (see the design notes below), and the animated opening cutscene, which I also edited.

The neon palette carries meaning: cyan for navigation, gold for currency and events, and hot pink for the action you should take next.

Role
Creative direction, art direction, game-feel and audio direction
Made with
Grok Build (AI-assisted development), AI image and video generation, OpenArt, DaVinci Resolve, sfxr.me, BeepBox
Play
Playtest demo on itch.io
Watch
Opening cutscene

From my direction, in my own words

The concept

“A space themed one where you control a black hole eating powerups and alien ships and once the time is up it shoots at a mothership.”

The core loop I pitched: eat, fill the power bar, then fire at the mothership. Mobile first, Steam later.

The look

“A retro-feeling space game, like an arcade game from the 80s, but with some anime flair.”

That brief became the art bible. For the cutscenes I pushed further: “change the global style to be more anime-like.” For the home screen I asked for art like the side of an arcade cabinet.

The name

“It might be nice to have black hole in the name so people browsing the play store know it's a hole-in game.”

Then I asked for “a quick way to get in the space invaders idea.” That led to Black Hole Invaders.

The characters

Matt: “plucky young boy thrust into danger who rises to the occasion.” Zhaun: “gray skin but not a stereotypical gray alien … calm presence, wise expression, a little sad and worn.”

I wrote both character briefs, down to the jersey, the cap, and the naval-commander hat.

The story

“A protagonist waking up to see alien ships in the sky, then an alien of a friendly race shows up in his yard and gives him the power to use a black hole.”

The power-ups on the field come from the mentor, whose power is limited. That gives the story a reason for the game mechanics.

The rhythm

“Every level that ends in 3, 5, and 7 should be a hard level, and every level that ends in 0 is super hard.”

Six in ten levels stay very doable for casual players, and the map uses color to flag the hard and super-hard levels.

Directing & editing

The opening cutscene

The game opens on the story beat I outlined: Matt wakes to alien ships filling the sky, and Zhaun arrives in his yard to hand him a black hole. The script was drafted with Grok. I set the anime look, built the environment and character reference art, animated the shots with AI video tools, and cut it together in DaVinci Resolve with subtitles and effects, so the cutscene leads straight into level 1.

The title art, characters, and glowing black-hole motif match the game, so the cutscene and the game feel like one world. Watch the opening cutscene on YouTube.

Case study · Black Hole Invaders

Directing game feel: when “close enough” isn't

The game's sound effects and music came from my direction in a single working session (September 1, 2026). The notes below are what I actually asked for, in my own words.

What mattered most was playing the music inside the game, not just listening to it on its own. That's how the biggest problem came to light.

  1. Sound effects

    “Make swallow a little deeper.”

    The sound effects are an 8-bit set made with sfxr.me. After hearing a draft, I asked for a heavier gulp when the black hole eats a ship. The deeper version is the one in the game.

  2. Music plan

    Menu loop, eating loop, siege loop

    I specified three BeepBox loops, one for each game state: the title menu, the eating phase, and the mothership siege.

  3. Revision 1: intent

    “Remix all 3 in A major, give eating a more upbeat and urgent feeling, the black hole is having fun eating the ships.”

    One shared key so the loops hang together, and a note about the character's mood, not technical settings.

  4. Revision 2: tested in the app

    “Make a new version of siege loop with different percussion than eating loop. They sound too similar when played back to back in the app, I want a clear differentiation when siege begins.”

    Playing the game, I noticed the change from eating to siege didn't register. The fix was a new siege loop with different, half-time percussion, so the boss phase now feels like a real shift.

Swallow (final)8-bit sound effect, deeper version
Menu loopTitle screen, A major
Eating loopUpbeat and urgent
Siege loopBoss phase, new percussion
Test in contextThe real problem only showed up during play, when two loops ran back to back.
Design for state changesA new phase of the game should feel different the moment it starts.
Give intent, not settings“The black hole is having fun eating the ships” is a note anyone can act on.

Case study · Black Hole Invaders

Design direction notes from the Build

While directing the game in Grok Build, I gave notes screen by screen. These are my notes, condensed: the rules I set for layout, menus, onboarding, the HUD, the store and map, and the reward screens.

Most of them come down to a few principles. Respect the phone screen. Never make the player hunt for a way out. Show only what's useful. Every state should look like what it is.

Phone layout

Fit the screen, don't shrink it

  • Home and the launch bay each fit on one phone screen, with no scrolling. The map follows the same rule: fill the screen, but don't shrink things so far it looks empty.
  • The Play button carries its own label (stage, stage name, level number) instead of a caption beside or under it.
  • Home uses hand-painted arcade-cabinet side art, not vectors or silhouettes. The same arcade background carries through to the store, inventory, map, weekly event, and Zen mode.

Menus

One way out, everywhere

  • One menu control you can reach everywhere, including the launch bay, so a player can back out before a run. It's present but unobtrusive during play.
  • Each place gets only the options it needs. In a run: pause, restart, sound, music, home. Launch bay: sound, music, home. Home settings: sound, music, About.
  • Later additions (volume sliders, a haptics switch, a Tutorial replay button) go at the top of the sheet, because controls under the sliders were getting clipped. I also asked for map access from the launch bay.

Tutorial cards

Readable at a glance

  • After the opening cutscene and before level 1, popup cards appear. The first shows the black hole with “Drag the black hole to eat alien ships and power-ups,” then one card for each ship and power-up.
  • Easy to tap through, with large art and text big enough to read. The body copy is never clipped, and the card never scrolls. Each card sits centered between the step counter and Next.
  • Ships on the cards and in the field key lie sideways, so the whole sprite shows, nose to exhaust.

HUD

Every number should be doing something

  • Ships and pickups never draw on top of the timer overlay.
  • In the siege, the mothership's health bar shrinks at the real destruction rate, not all at once. The black hole's stored power moves to the bottom and counts down in place of the bar you just filled, so a full bar doesn't just sit there.
  • In Zen mode, the bar fills once and then glows as the number climbs, instead of emptying and refilling.
  • The field key before a run shows only what's in that level, and what each item gives the hole.

Store, inventory, map, weekly

Show only what's useful to the player

  • The store can scroll a little, but it should be dense, with several items per row. The life refill is larger but shorter, with no ticker beside it.
  • No ticker when it has nothing to say. When there is one, it's tappable. Inventory thumbnails should all look different from each other.
  • The map doesn't print the color key twice or show internal lines like “locked reels stay dark.” Locked cutscenes stay visibly locked.
  • The weekly event says what you win (beat a level for a free cosmetic from this month's theme), plus the week number, time left, and theme name. Color labels read “CYAN: Standard,” with a colon.

Results

Make replay value obvious

  • Clearing a level earns 1 to 3 stars. The map shows the stars earned and each area's total, so it's obvious when replaying for a better rating is worth it.
  • Victory screens can go big on anime title-card energy: huge type, sparkles, dramatic poses. The playfield stays cleaner than those screens, so play stays readable.
Home screen from the September demo with PLAY Stage 1 Earth Level 2
Home screen (Sept 2026 demo): one screen, and the Play button carries the stage, area, and level
Siege phase with hole power counting down at the bottom
Siege: the mothership bar at the top, stored hole power at the bottom

What these notes show

Hierarchy: one primary action that carries its own context.

Clarity of state: locked looks locked, a full bar does something, and a siege looks different from eating.

Readability: no clipped copy, no scrolling cards, no sprites cut off.

Restraint: no internal labels, no empty tickers, no doubled keys. Save the spectacle for the victory screens.

Character consistency · Animated short · Thumbnails

The 23rd Psalm & the hymn series

One storybook heroine, my Lily Fernwild persona with her pet rat, carried across an animated short and a whole channel of illustrated hymn videos.

The 23rd Psalm is a three-minute animated short. Her face, curls, green cloak, and rat stay recognizable from scene to scene. That's the hardest thing to hold in AI animation.

The hymn series keeps one soft watercolor style across more than a dozen songs, so the channel reads as one body of work. The thumbnails are built for phone size: one clear focal group, a heavy two-line title, and a single accent color. Each hymn also has a 9:16 cut for TikTok and YouTube Shorts.

Role
Character design, art direction, animation, edit, thumbnails
Tools
AI image and video generation, Suno, Audacity, DaVinci Resolve
Watch
The 23rd Psalm · the full channel

Style range · Key art · Typography

Music video key art

Three very different visual languages, each one picked to fit the song.

Watercolor Rainbows (Skyebros): soft storybook watercolor, a hand-lettered title, warm greens. It's the style I offer as custom watercolor lyric videos on Fiverr.

You Might Be the Bad Guy (dark trap): cinematic stage lighting, one figure against near-black, and heavy condensed gold type.

Nuxa-core (Nuxanor): an online personality I admire, drawn in high-energy neon anime, with a remastered V2 cover. It's my most-viewed video so far.

Role
Concept, art direction, edit, thumbnails
Tools
AI image and video generation, Suno, DaVinci Resolve
Watch
Watercolor Rainbows · Bad Guy · Nuxa-core

About

A writer who directs pictures

Before AI art, I spent 20 years writing and proofreading professionally: copywriting at a marketing and design agency, editing and laying out a student newspaper, and writing process documents and templates for a remote support team. That background shapes how I direct. I describe the intent clearly, check the result where it will actually be used, and give specific notes until it's right.

I also do paid AI training work with DataAnnotation.

Toolkit

Image & video
Grok Imagine, Nano Banana 2, Seedance, Kling, OpenArt
Music & audio
Suno, Audacity, BeepBox, sfxr
Edit & layout
DaVinci Resolve
Game direction
Grok Build (AI-assisted development)
Writing
Copywriting, proofreading, editing, process documentation