How to build an illustration system without an illustrator
An illustration system is a short set of rules that decides what your illustrations show, how they are drawn and where they appear, so every new one looks as if it came from the same hand. A small team can build one without hiring: choose a library whose style you can live with, constrain a coding agent to the same rules for whatever the library lacks, and write the rules down where the next person, or the next agent, will find them. This guide covers the decisions a system holds, how to build one, a map of where illustrations go in a SaaS product, and when an illustrator is still the right call.
Rules, not a pile of images
Most product sites without a system have a pile instead: a free flat illustration on the 404, a stock 3D render on the pricing page, a generated image on the blog. Each looked fine on the day it was chosen. Together they say nobody decided.
A system is the deciding, done once. It does not need to be long. A page of rules that you actually follow beats a brand book nobody opens. The test is simple: hand the rules to someone new, ask for an illustration for a screen they have never seen, and check whether it sits beside the existing ones without anyone noticing it is new.
The decisions a system contains
Subject matter
Decide what you draw: people, objects, abstract shapes or pieces of interface. Each choice carries weight. People bring warmth, but also questions of who is shown and how, and they date quickly. Objects read at small sizes, carry one idea each and age slowly. Interface pieces explain features literally but compete with the real interface around them.
Linejig's rule, as a worked example: one real object per illustration, chosen because it stands for the idea (a lock for security, a telescope for discovery), with no brands, logos or text in the drawing. The page owns the words.
Line
One line width, or several. One width is easier to keep consistent and survives scaling; several give more hierarchy but drift faster when different people draw. Linejig uses one line width, about one pixel on screen at any size, and makes hierarchy with tone instead: five greys, from the background to the one bright part that matters.
Perspective
Pick one camera for everything. Mixing flat front views and angled views on one site, with no rule for which goes where, is one of the quickest ways to look unplanned. Linejig uses a single raised, angled camera, the view most people call isometric, for every figure.
Colour
Decide how many colours, which one is the brand colour, and where it is allowed. The tighter this rule, the more an illustration reads as yours. Linejig keeps everything grey except one hero part, which takes your brand colour, so the colour always lands on the part the illustration is about.
Motion
Decide whether illustrations move at all, how long a move takes, and what a visitor who asked for reduced motion sees. Linejig's rules: an intro (the object assembles, or its lines draw on), then one move that means something, such as a lid lifting or a needle settling, with the same timings across every figure. With reduced motion set, a figure shows its finished state at once.
Where illustrations go, and where they do not
This is the rule most systems forget. Some places to leave empty:
- Screens people use many times a day, after the first visit. An illustration that delights once gets in the way on the fiftieth.
- Anywhere it would replace words. An error page still needs to say what went wrong and what to do.
- Dense data: tables, settings, billing history.
- More than one per screen, as a default. One object per idea is easier to read.
Building one without hiring
- Pick a library whose rules you accept. Judge it on whether it covers the moments you need, whether its style can take your brand colour, and whether it works in light and dark if your product does. Starting from a library means most moments are solved on day one and the style decisions above were made, and tested, by whoever drew it.
- Constrain an agent for the gaps. Every library runs out eventually. A skill that carries the library's rules lets a coding agent draw the missing piece in the same style. Image models can drift from one picture to the next; drawings made in code on a shared engine cannot change camera or line width, because the engine owns them. Linejig's free Line art skill, tested in Claude Code and Codex CLI, works this way: it proposes three concepts, waits for you to choose, then draws in Line art on the same engine as the library; Brand and Dots come in the Pro skill, Linejig Pro. Other skills take different approaches, compared in isometric illustration skills for coding agents.
- Write the rules down. Keep them in the repo, next to the code, so an agent reads them too. A short file is enough:
# Illustrations
Source: the Linejig library; new figures with the linejig skill.
Subject: one real object per idea. No people, logos or text in drawings.
Style: brand, with our colour on the hero part. Light and dark follow the app.
Places: 404 and errors, empty states, onboarding steps, feature sections,
pricing, docs headers. Not in tables, settings or repeat-use screens.
Motion: library defaults. Reduced motion shows the finished state.
Words: always in the page, never in the drawing.Review new illustrations against that file, not against taste on the day.
A map for a SaaS product
Each moment below links to the matching set in the library.
- 404 and error pages. A visitor is close to leaving. A calm object gives them a beat while the page shows the way back. See error page illustrations.
- Empty states. Often the first screen of a new account. The object should point at the next step, and in Linejig a click on the hero part can hand an action such as compose or upload to your page. See empty state illustrations.
- Onboarding. One object per step, each holding one idea. See onboarding illustrations.
- Feature explainers. One idea and one picture per section, in feature pages, changelogs and tours. See feature explainer illustrations.
- Pricing and checkout. People slow down and read here, so the illustration should be quiet: a card, a wallet, coins. See pricing and payment illustrations.
- Docs. Readers are mid-task, so a picture has to earn its place, usually on a section header or an install step. See illustrations for developer docs.
- Loading and waiting. Something quietly working makes a wait feel shorter. See loading illustrations.
Fingerpost signpost Free
This road goes nowhere; the way home is this way.
Magnifier over empty results Free
Nothing matches; try clearing your filters.
Phone Pro
Your app, in hand.
Payment card Pro
Pay in one tap.
When to hire an illustrator after all
A library and an agent cover spot illustrations for product moments well. They are the wrong tool when:
- Your brand needs a character. A mascot, recurring people or a voice with emotion is authored work, and it rewards a person who owns it.
- Illustration is the brand. If your visual identity rests on a style nobody else has, a shared library is the opposite of what you want.
- You need scenes, not objects. Campaign art, editorial pieces and marketing scenes with many elements and a story need composition and judgement.
- Nobody on the team can say no. An agent will draw whatever you accept. If no one can tell a good illustration from a passable one, a designer's eye is worth paying for, even for a short review.
A sensible middle path is to hire for the system and not the pile: pay an illustrator to set the rules and draw the first key pieces, then extend them with a library or a skill that follows those rules.
Next step
Browse the library by moment, or start with the free figures. When you need an object it does not have, the skill page has the install steps.
Published 21 November 2026.