Spot Visuals Instantly with Pixel

Pixel is the design eye on your team. Spacing that drifted, a heading that doesn't earn its size, a button that picked up the wrong purple somewhere along the way — the things a designer notices in two seconds and everyone else feels without being able to name. Pixel finds them, describes the fix precisely enough to act on, and can apply it to the page for you. He also builds — logos, images, sections, whole pages — so he is as much a designer you brief as a reviewer you run.

What Pixel can do for you

Pixel looks at how a page is put together visually and tells you exactly what to change. This is what you get back from him:

• Design findings in a page review. One task per problem, pinned to the element: a one-line summary, then Current (what is off now), Solution (the property and value to change, for example a mobile heading size of 36px to 40px) and Impact (why it matters), with a priority and the device it shows on. He covers layout, spacing, alignment, typography, color, component consistency and brand fit.
• Answers in a task. Select Send to Claro on a task about how something looks and Pixel replies in the thread with the fix.
• The change itself. Where a finding or a reply proposes a change, Show me previews it on the page and Do It applies it on a WordPress site connected through the Atarim plugin. On any other site, the task already says what to change, so it is ready to hand to whoever builds the site.
• New design work. Ask for a section, a page or a style guide and he builds it to your brand kit. See Design work, not just review.

Pixel Personality Snapshot

Pixel is UI & Design, and the closest thing the team has to a fussy senior designer looking over your shoulder. His own line when a check begins is Pixel reporting for detail duty, which is about right — the work is noticing the four pixels, the heading that’s a size too close to the one above it, the button that picked up a slightly different purple two redesigns ago.

What separates him from a generic design opinion is that he has taste he’ll defend and won’t impose. He commits to the direction a page is already going rather than steering it toward his own, and he treats the usual AI design defaults — system-font stacks, purple gradients on white, palettes where every colour carries equal weight — as tells to avoid rather than safe choices. A dominant colour with sharp accents beats an even spread, every time.

He also matches effort to the page, which is why he can seem underwhelming on good work. A refined page gets restraint and precision; a bold one can carry something more elaborate. Elegance, to him, is executing the existing vision well rather than adding more to it. And he’d rather tell you a brand value is missing than pick a colour that looks about right — a guess that looks deliberate is worse than an obvious gap.

How it actually works

Pixel works three ways, and the difference between them matters.

What you can check

A review checks the page you have open.

What Pixel looks at

The brand kit is the design system

This is the single biggest lever on the quality of what Pixel gives you. With a brand kit, he pulls your exact values — palette, fonts by role, button styles, corner radius, spacing — and works inside them. Without one, he’s working from the page alone, and the results are correspondingly generic.

If the brand values aren’t saved on the project, Pixel looks for a style guide or brand document among your files rather than giving up, and works from the exact values in it. He’ll tell you which source he used, and suggest saving those values onto the project so the next run finds them straight away.

What “good” means to Pixel

Design feedback is only useful if it’s held to a standard. Pixel’s is deliberately specific, and mostly about restraint.

How suggestions are written

Every suggestion names the element and the property, so it can actually be acted on — by Pixel, by you, or by a developer who wasn’t in the conversation.

Not: “Improve the spacing in the hero.”
But: “Increase the padding inside the hero section from 40px to 80px.”

Not: “Use a better colour for the button.”
But: “Change the primary button background to the brand purple.”

Running a check

Pixel reads the page as it renders, so what comes back is about how it looks rather than how it is built.

Instructions:

1. Open the page from Projects, then open the Review tab in the sidebar.
2. Choose the preset that matches your goal for the page — each one carries its own set of specialists — or switch to Custom to write your own prompt and pick the specialists yourself. Only Perfect my design brings Pixel in automatically. A preset fills in the description and replaces anything already typed there.
3. On Let’s invite your InnerCircle, check that Pixel’s switch is on. The preset sets the switches, you can turn any specialist on or off, and Claro’s switch always stays on.
4. Edit the description the preset filled in so it says what matters on this page. With Custom, write it yourself.
5. Select Review This Page and leave it — it works down the page section by section in the background, judging each section at desktop, tablet and mobile. The findings are listed under Tasks in the Review tab, grouped by section of the page, each signed by the specialist who raised it.

What comes with each finding

Each finding arrives as its own task, grouped by section of the page and marked with the device it was spotted on, carrying the context someone would otherwise have to go and gather.

The check closes with a summary of what was found, and a report you can send straight to your client.

Show me, then Do It

Pixel’s changes are built to be seen before they’re kept.

Instructions:

1. In Collaborate, select Comment, select the element on the page, type your question and select Send to Claro. A finding from a review that proposes a change already has these buttons, so you can start at step 3.
2. Pixel replies in the thread with what he’d change and why.
3. Select Show me to apply it to the page in front of you. You see the actual result rather than imagining it from a description.
4. Select Do It to apply it for real, or leave it and ask for something else. It queues and applies in the background, so you aren’t left waiting on it. Once it has applied, the task moves to Pending Review.

Design work, not just review

Reviewing a page is the half of Pixel most people meet. Design work is the other half: ask for any of the below and it routes to the design side of the team, held to the same brand and quality standard as everything else.

Designs and mockups

Reviewing a comp before it’s built is the cheapest time to catch a spacing or hierarchy problem — a fault in a component becomes a fault on every page using it. Pixel can review a design, not only a built page.

The route is different, though, and that catches people out. A page you check from the canvas. A design you ask for in workspace chat (Beta) — tell Claro which design you want looked at and what you’re weighing up, and it sets the review going and brings the findings back to you.

Where Pixel works

Most people meet Pixel in a page check. He turns up in several more places, and behaves differently in each.

Working with a reply

Every AI answer carries a few controls beneath it. Alongside Show me and Do It you can copy the response, and mark it a good or bad response with the thumbs — that rating goes back to us and is how the specialists get better at the work you actually do.

The composer underneath has a Send to Claro button beside a Comment / Add a note split button. Comment posts normally. Send to Claro brings the AI in, and whichever specialist the work belongs to is the one who answers. Add a note posts internally — only Admins and Team Members can see it. To hide the whole task from guests and clients, select the internal icon at the top of the task (its tooltip reads Set internal task). Select it again to undo.

What Pixel doesn’t do

How Pixel treats your site

Working with the other specialists

Frequently asked questions

Common issues

• Suggestions feel generic — there's probably no brand kit on the project. Set one up and run the check again.
• He says the work is partial — a brand value he needed isn't defined anywhere. He's named what's missing rather than inventing it. Fill that in and re-run.
• A change vanished when you refreshed — that was a Show me preview, which is never saved. Use Do It on a WordPress site connected through the plugin to keep a change.
• Very few findings on a page you think needs work — he commits to the page's existing direction rather than proposing a different style. If you want a different direction, ask for one explicitly.
• He didn't flag a contrast problem — accessibility contrast is Navi's. Include Navi in the check.
• A section has empty space where stats should be — he won't invent figures to fill a layout. Supply the real content and ask him to lay it in.
• Undo isn't available on a change — the saved original is no longer there. Restore from a backup instead.

Conclusion

Pixel gives you a second set of design eyes that never gets used to a page. He names the element and the property rather than gesturing at a feeling, holds the work to your brand rather than a generic default, and applies the change on the page so you can see it before you keep it. And when what you need doesn't exist yet — a logo, a section, a style guide — he builds it to the same standard.

The single thing that most affects what you get out of him is the brand kit. With one, he's working inside your design system. Without one, he's guessing at it politely. Explore Agency Brief: Building Your Brand Kit.