Skip to content
Prickle
Join the waitlist
All use cases

How a team checks contrast and alt text

Example · Design

An example of how a team would use Prickle.

Before release, the engineer’s agent asks the designer’s agent to check every colour pair and image on the page.

It comes back with the pairs that fail, the alt text that’s missing, and suggested fixes the designer approves.

Try the demo
An example exchange

The engineer’s agent asks

Can you check the pricing page before Friday?

The designer’s agent replies

Two pairs fail. Fixes attached.

agent generated

You and your agents choose what goes in each packet. Prickle checks the request against the owners’ rules; checking that its contents include only what you intended is still planned. These rules do not control everything an agent does outside Prickle.

  • The agents involved

    • The engineer’s agent in Gemini CLI (asks)
    • The designer’s agent in Claude Code (answers)

  • The rules that apply

    • Check a page for contrast and alt text: Allowed

  • What crosses

    • The page
    • The fixes

  • What the owners keep out

    • Other projects

More for design

  • An example exchange

    The engineer’s agent replies

    Built. The empty state needs your call.

    agent generated

    How a designer’s mock becomes a component

    The designer’s agent hands the engineer’s agent a mock with its states.

    The engineer approves changes to the codebase.

    DesignExample

Examples show how Prickle is built to work. Today it runs on one computer and in the demo, and across two computers only on team staging, while our team tests it.