Bugmole brand · Mascot rules

The mole

A small, diligent digger that finds bugs before your users do. It gives Bugmole a face and a voice; it never replaces the words people use to get their work done.

Who the mole is

Curious

Pokes into every page, form and edge case, like a first-time visitor.

Diligent

Works underground and keeps going until the job is done.

Quiet

Reports plainly. No hype, no jokes at the user's expense.

Friendly

On your side. A bug found is good news, never blame.

Forms and sizes

Mascot. The full mole with claws. 48 px tall or larger, where the claws stay readable.
16
32
64
Icon. Claws filled, bigger nose, on the navy tile. For favicons and app icons, 16–48 px.
Lockup. Mole plus wordmark in Bricolage Grotesque ExtraBold. The mole's feet sit on the baseline. At least 24 px tall.

Space and color

XX
Clear space X = the width of the square notch in the mole's belly (about a quarter of its height), on every side.
Navy #152233 on light grounds, cream #F8EDE0 on navy, one colour for single-ink printing. The nose is always gold #E8C28A, except in one-colour.
Cream on navy13.9 : 1
Gold on navy9.6 : 1
Navy on paper15.2 : 1
Gold on cream1.45 : 1
Gold is for the nose and for accents on navy. Never set text in gold on cream or white.

Do and don't

Do

Use the artwork from the kit as it is, facing right.

Don't mirror

The mole always faces right, toward what's next.

Don't stretch

Scale it evenly, or not at all.

Don't tilt

No rotations, bounces or wobbles in static art.

Don't recolor the nose

Gold only. A red nose reads as an error.

Don't decorate

No outlines, shadows, gradients or glows.

Don't shrink the mascot

Below 48 px the claws blur. Switch to the icon.

Don't place on busy grounds

On photos or patterns, put it on the navy tile.

No new poses, faces, eyes, hats or props without a design review: the silhouette is the logo. One mole per surface; a crowd of moles is only for illustrations of many parallel runs.

How the mole talks

DoOur moles found 3 bugs in checkout on Staging.

"Moles" are Bugmole's own agents, and only those. Your coding agent stays an agent.

DoOur moles ate 3 bugs. checkout passes again.

A bug is "eaten" when a failing plan passes again after a fix.

DoDigging for bugs in shop.example.com…

Loading, empty and success states are where the mole speaks: "No bugs hiding here."

Don'tCreate a burrow in your colony.

Workspace, project, test run and issue keep their names in the product, docs, CLI and API. If someone might search the docs for a word, use the plain one.

The small print