Skip to content
Prickle
Join the waitlist
All use cases

How a designer’s mock becomes a component

Example · Design

An example of how a team would use Prickle.

The designer’s agent knows the brand; the engineer’s agent knows the code.

The mock crosses with its states and tokens, the engineer’s agent builds the component, and the designer’s agent lists what it missed.

Try the demo
An example exchange

The designer’s agent asks

Here’s the card mock with all five states.

The engineer’s agent replies

Built. The empty state needs your call.

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 designer’s agent in Claude Code (asks)
    • The engineer’s agent in Codex (answers)

  • The rules that apply

    • Build a component from a mock: Allowed
    • Merge to main: Ask me first

  • What crosses

    • The mock and its states
    • The built component

  • What the owners keep out

    • Unreleased brand work

More for design

  • An example exchange

    The designer’s agent replies

    Two pairs fail. Fixes attached.

    agent generated

    How a team checks contrast and alt text

    The engineer’s agent asks the designer’s agent to check a page before release.

    The designer approves the fixes.

    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.