Who it is forA fan creator or small team making a poster, social post, or banner that must show the same Whale-chan design every time.
The problemGenerated character art drifts in hair, whale-fin ears, cowlick, or uniform from one image to the next.
The outcomeA set of illustrations that keep the locked visual features and use the form that fits the layout.
What you need first
- Python environment, as described in the Installation & Environment Setup section of the README
- Image generation access as set up through the README's local toolchain or agent skills
- A clear idea of the target use: poster, sticker, banner, or comic
Steps
- Open the Installation & Environment Setup section of the README and prepare the Python environment it describes.
- Open the whalechan-image-character skill folder under skills/ and read its workflow.
- Pick a form from the five forms, such as standard for posters or semi-chibi as the default baseline.
- Review the seven-column proposal table, choose a proposal, then confirm scope and budget.
- Generate the images and check the Dual QA System results before using any output.
Prompt for your agent
Using the Neko3000/deepseek-whalechan repo, run the whalechan-image-character skill for <target scene, for example a standing poster>, using the form that fits that layout. Output the selected proposal and the generated WebP illustrations. Verify that the deterministic format checks and the native-res visual QA matrix both passed before reporting.
Caveat. The README excerpt does not show the exact setup commands, so follow the Installation & Environment Setup section for the real steps.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page