DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to make a set of brand illustrations for your website with Anidoodle

Generate a hero image and matching spot art in one chosen style, as transparent PNGs at any size.

  • Content
  • Beginner
  • 30 minutes
  • From the README
  • Claude Code
  • Codex

Who it is forA designer or marketing lead who needs consistent art for a website, deck or docs and has no illustrator on hand.

The problemStock images rarely match one brand voice, and commissioning an illustrator for every page is slow and costly.

The outcomeA hero illustration, feature spot art, empty states and a 404 page, all drawn in the same hand, with transparent PNGs at any size.

What you need first

  • Claude Code, Codex, Grok Build, or another agent that reads skills
  • Node.js to run the repo's tools (inferred from the node commands in the README)
  • The anidoodle repository cloned or installed from its Install link
  • Optional: about 373 MB of free disk space for the sound pack

Steps

  1. Install the Anidoodle skill in your agent (inferred) from the repo's Install link.
  2. Pick one of the 32 styles for your brand, such as risograph or woodcut.
  3. Ask your agent in plain words for each image, including the size, for example a risograph lighthouse for a careers page at 1600×900.
  4. Ask for the film of each picture if you want the making-of version as well.
  5. Place the transparent PNGs on your site and reuse the same seed for sister images in the same style.

Prompt for your agent

Using the anidoodle repo, draw a hero illustration for <page name> in the <style name> style at 1600×900, plus three spot illustrations for its features. Return transparent PNG files and confirm all four share the same style.

Caveat. The README lists 32 styles and says the same source redraws the same picture on every machine, but it does not give a fixed list of sizes beyond the example, so confirm your sizes with the agent.

Share: 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