GengJing GengJing · DeepSeek Memes

Whale-chan Meme Tutorial — Teaching AI to Draw Her Consistently

The hardest part of making your own Whale-chan memes is drift: ask AI to draw the same character ten times and you get ten different faces. The open-source DeepSeek Whale-chan project fixes this the engineering way — a character spec, five quantified head-ratio forms, reference-locked identity, and automated QA. This page condenses its essentials into a quick-start guide; the full, always-current documentation lives in the repo (see attribution at the end).

Read this page in: 中文 · 繁體中文 · 日本語 · 한국어

At a glance

Project
Open-source DeepSeek Whale-chan (community-driven, unofficial)
Contents
Character spec + reference asset library + two Agent Skills: whalechan-image-character / whalechan-image-comic
For
Creators who want to generate Whale-chan illustrations, stickers, and gag comics
Bar
Comfortable using an AI coding agent (Codex / Claude Code / Gemini). No drawing skills needed
Cost
Codex built-in ImageGen works with zero config; OpenAI / Nano Banana / Seedream are optional fallbacks billed per API
License
Spec docs CC-BY-NC-SA 4.0 / code MIT; character belongs to the community, some assets to their creators (see attribution)

Why characters drift: split identity from everything else

Image models have no memory — every generation re-guesses the character from the prompt, so hair color drifts, the tail vanishes, the maid outfit mutates. This project's fix mirrors industrial design: lock a permanent identity in a spec, and treat style, action, outfit, background, and proportions as independently resolved fields. Changing one never disturbs the others.

Whale-chan's permanent identity: broad round face, big expressive eyes, deep-ocean-blue hair fading to cyan curled ends, paired side whale-fin ears, one forward-curving ahoge, one coherent whale tail, and the navy-and-white ornate maid outfit (white whale emblem, muted-gold piping). Keep those and she stays herself in any style.

The full character card (birthday, personality, catchphrases) is in the repo README; for her backstory see our encyclopedia entry, and for ready-made turnaround sheets see the character sheets.

Five head-ratio forms: cuteness, quantified

The most hardcore part of the project: five standard forms with exact head-ratio targets and acceptance intervals — outputs are literally measured, and out-of-range results fail:

Form codeTargetAcceptanceLook & best use
standard4.0 heads3.846–4.146Most elongated: extended body, long natural limbs. Standing poses, formal art, posters
compact3.3 heads3.105–3.405Compact normal form with moderately shortened limbs. Dynamic action, seated interaction, mid-shots
semi-chibi2.8 heads2.689–2.989Default baseline: slightly larger head, rounded and compact — cute yet scene-friendly
chibi2.5 heads2.372–2.672Q-version: tiny torso, exaggerated emotions. Gag comics and stickers
super-deformed2.1 heads1.931–2.231Most compressed: huge head, stubby limbs, all focus on the face and ahoge. Big-reaction stickers

For memes, chibi and super-deformed work best: the bigger the head, the louder the emotion. All Skills default to semi-chibi.

Proportion changes body geometry only — never apparent age. Mapping "young" or "child" to any form is explicitly forbidden by the spec.

Two Skills: one paints, one writes punchlines

The repo ships two drop-in Agent Skills you call straight from your AI coding agent's chat:

The comedy engine deserves one extra sentence: it locks a real fact from the input (e.g. "the user allowed her to eat things from the fridge"), then Whale-chan twists the meaning ("so the entire fridge is my lunchbox now"). You only supply a clear fact, conflict, or permission — never the punchline.

Install: three steps

Prerequisite: you already use an agent runtime that supports Skills (Codex, Claude Code, Gemini / Antigravity…). Step 1, clone the repo:

git clone https://github.com/Neko3000/deepseek-whalechan.git
cd deepseek-whalechan
pip install pillow   # optional: imaging & validation deps

Step 2, copy the two Skills into your agent's skill directory:

# Codex
mkdir -p ~/.codex/skills
cp -R skills/* ~/.codex/skills/

# Claude Code
mkdir -p ~/.claude/skills
cp -R skills/* ~/.claude/skills/

# Gemini / Antigravity
mkdir -p ~/.gemini/config/skills
cp -R skills/* ~/.gemini/config/skills/

Step 3, restart the session — the agent picks up $whalechan-image-character and $whalechan-image-comic automatically.

Provider setup is optional: Codex's built-in ImageGen is the default with zero config. To enable external fallbacks, set OPENAI_API_KEY (gpt-image-2) / GEMINI_API_KEY (Nano Banana) / ARK_API_KEY (Seedream). Never commit a real API key or paste one into chat.

First runs: two prompts you can copy verbatim

Scenario 1 — a banner with exact rendered text:

Use $whalechan-image-character to generate an 8:3 Whale-chan banner:

Whale-chan on the right, paused just before her first bite, cheeks slightly puffed,
chopsticks hovering over the rice bowl.

The text must read exactly:
"Rice first, reasoning later!"

The Skill first presents a plan (canvas, form, composition, per-image config, provider order, candidate budget) and waits for your confirmation — a deliberate anti-footgun design; only then does it spend generation quota.

Scenario 2 — turn a snippet into five reversal comics:

Use $whalechan-image-comic to turn the following into five Whale-chan reversal comics:

"The user allowed Whale-chan to eat things from the fridge; she promptly asked
whether she could take the whole fridge home."

You can also attach a chat screenshot and note "extract only the facts and semantics; do not replicate the original UI, avatars, or layout." Outputs are archived under artifacts/ with full prompts and QA records.

Why nothing drifts: three QA gates

Any failed gate blocks delivery; retries fix exactly one problem at a time. The scripts also run standalone — handy for wiring into your own pipeline.

After you generate: submit to GengJing

Memes you make with these tools are welcome on GengJing: submit on-site (no account, attribution supported) → community review → curator approval. The tutorial teaches creation; GengJing handles curation — as the repo author put it when granting this adaptation: let's grow the Whale-chan ecosystem together.

Open the GitHub repo ↗ Submit to GengJing

More tutorials

Source & license

This tutorial adapts and condenses the open-source DeepSeek Whale-chan project (DeepSeek Whale-chan Project, by Neko3000). Adaptation was formally authorized in issue #2; the adapted parts are shared under the same CC-BY-NC-SA 4.0 terms. The Whale-chan persona is a community creation; some foundational design assets are copyrighted by their original creators (ZipZipPipe, Shangshan Wuxing on Bilibili), and commercial use requires written permission from the rights holders. The community route now lives on its own tutorial page. This page only curates and attributes third-party content; it grants no licenses on anyone's behalf. Per our commitment, this page carries no advertising, ever.

FAQ

Do I need to draw or code?

Neither. The interface is plain language in your AI agent's chat — describe the picture or paste some material. The repo's Python scripts are optional advanced QA tooling.

Does it cost money?

Codex's built-in ImageGen is the default and needs no API key; OpenAI, Nano Banana (Gemini), and Seedream (Volcengine) are optional fallbacks billed by their own APIs. Skills show you a plan and wait for confirmation before spending quota.

Can I use the output commercially?

Not freely. The project's spec docs are CC-BY-NC-SA 4.0 (non-commercial); the Whale-chan persona belongs to the community, and some foundational assets are copyrighted by their original creators (ZipZipPipe, Shangshan Wuxing on Bilibili). Commercial use needs written permission from the rights holders. Personal chat use, avatars, and wallpapers are fine.

How does this page relate to the GitHub repo?

It is an adapted, condensed edition of the repo's README and Skills docs, authorized by the author in issue #2 and shared under the same CC-BY-NC-SA 4.0 terms with prominent attribution. The complete, always-current documentation lives in the repo — this page is an on-ramp, not a replacement, and is synced as the repo evolves.

How is this different from the /refs character sheets?

The character sheets provide ready-made turnarounds to use as img2img / ControlNet references; this tutorial walks the Agent-Skill route of "spec + references + QA." The two stack: install the Skill, then feed the sheets in as identity references.

No coding agent — is there an easier way?

Yes — the community route now has its own tutorial: one reference sheet plus two long prompts, two generation steps in a conversational image model, no coding agent or scripts.

References