Design-system drift audit
Hard-coded colours, one-off spacing, and the components that bypass the tokens, listed by file.
For the team
Check the real screens without waiting for a build.
The design system is exact in the file and approximate in the app. Finding out which is which usually takes a running build or somebody else’s afternoon; here it takes one question in the channel.
For designers
The wait today
Design intent survives the handoff and then drifts, one hard-coded hex and one off-scale margin at a time. Nobody decides to let that happen; it happens because checking means running the app, and running the app is the one thing the person who cares most about it cannot easily do.
They ask
Ask in your own words. The answer names its commit.
Mention @PRCHD with the question you’d have saved for a colleague, and it reaches the agent exactly as typed. The agent reads the project’s checkout in Act mode, which changes nothing on disk, and the answer lands in the thread footed with the commit it was read from.
- @PRCHD are the new empty states live on main, and what do they look like?
- @PRCHD which components still use the old spacing scale?
- @PRCHD where is this button’s disabled state defined, and what does it actually render?
- @PRCHD does the error toast still truncate to one line?
They run
The jobs that keep coming back, written down once.
Each is a prompt plus a posture that someone on the team writes once. After that, anyone in a private channel the operator enabled for runs starts it with one slash command, and the result comes back in the thread. These are examples for designers, not a catalog to install — PRCHD supplies the engine, and each team writes its own.
Screenshot sweep
The key screens walked in the browser tool, posted into the channel as images.
Accessibility pass
Contrast, focus order, labels, and keyboard traps, reported per screen.
Scheduled and triggered
Some of the work is done before anyone asks.
Put the same recipe on a cron line or behind a webhook URL and it starts on its own, so work that used to wait for someone to wake up or find time is already done when people arrive.
- A weekly drift report covering the colours and spacing values added since the last one.
- A scheduled screenshot sweep of the key screens, so a visual change is noticed the morning after it lands.
What changes
Design QA happens against the real app, without waiting for a build or an engineer.
Where it stops. Slack is words, not widgets — a mention and one slash command are the whole vocabulary. A screenshot sweep arrives as images to read in the thread, rather than screens to click through.
Other roles
The same host answers the rest of the team.
Product managers
@PRCHD is the export limit still 500 rows, and where is it enforced?
Product questions get answered from the code, without booking an engineer.
Engineering managers
@PRCHD what’s changed on main since Friday, and what’s risky in it?
The status an engineering manager currently assembles by asking five people assembles itself.
Founders and CTOs
@PRCHD how hard would it be to support a second currency?
Leadership gets ground truth directly, at 22:00, without pulling anyone off anything.
Where your code lives
The computer you own is the computer that runs.
Repositories, worktrees, prompts, transcripts, diffs, command output, attachments, environment values, and the event log stay on the computer you installed PRCHD on — the one that already has your code and your tools. The agent works there, so there is nothing to copy into a hosted environment and nothing uploaded to be indexed.
One small public service handles what a computer with no open port can’t do on its own: it enrolls your computer’s identity, forwards short push notifications, and holds webhook deliveries until your computer collects them. Each delivery is sealed to your computer’s public key the moment it arrives, so the service only ever holds ciphertext, and it is never in the path of your work.
Standing watch
Send this to whoever runs the shared computer.
One person installs it — an afternoon, not a migration. Everyone else asks from a Slack channel they’re already in, and nobody creates an account, installs an app, or pairs a phone.