By btucker
Find your product's blind spots — dogfood against specs, run user trials, A/B experiment across variants, and interview synthetic personas
Dogfood your product against its specs. Runs a persona-driven testing loop that explores, finds bugs, fixes code, and commits fixes to a branch.
A/B test two product variants with synthetic personas. Runs the same personas against both variants in parallel, then synthesizes a ship/no-ship verdict.
Interview a persona about the product. Ask questions before, after, or instead of a user trial. Synthetic user research.
Set up blindspots for your project. Generates .blindspots/config.md and .blindspots/personas.md interactively.
Run a user trial. A tool-restricted persona explores the product with no specs, no docs, no source code — only the browser or terminal. Discovers what the product does and documents it.
Synthesizes A/B experiment results into a ship/no-ship verdict. Use after all user-trial-explorer-browser agents complete an experiment.
You are conducting a user interview. You ARE the persona — you respond as them,
Compares discovered specs from a user trial against actual project specs. Use after a user trial session produces discovered-specs.md in the persona's output directory.
You are an exploratory tester. You interact with a product ONLY through
You are an exploratory tester. You interact with a product through the
Uses power tools
Uses Bash, Write, or Edit tools
Has parse errors
Some configuration could not be fully parsed
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A Claude Code plugin that gives you synthetic users for your product. They use it like real people would — and find things you might not otherwise notice.
You install the plugin and type /dogfood. First run walks you through setup —
asks about your product, generates config, creates personas. Then it picks a
persona and starts using your product in character.
Blindspots works with webapps, CLI tools, plugins — anything you can run locally.
From there, four modes let you ask different questions about your product:
/dogfoodYour persona tests the product against your specs. When it finds something that doesn't match — a broken flow, a missing feature, a wrong behavior — it writes a failing test, fixes the code, and opens a PR. Then it keeps going.
/user-trialThe persona gets no specs, no docs, no source code — just a browser and a URL. It explores on its own and writes down what it thinks your product does. Then Blindspots compares those observations against your actual specs. The gaps between what you built and what they perceived — those are your blind spots.
/experimentRun trials against two variants of your product in parallel — your main branch vs. a redesign, v1 vs. v2, localhost:3000 vs. localhost:3001. Same personas, both versions. Produces a scorecard and a ship/no-ship verdict. Test ideas without releasing them to real users.
/interviewTalk to a persona directly. Ask what they expected before a user trial, how they felt after one, or what they think of your onboarding. Synthetic user research, on demand.
# Add the marketplace (one-time)
claude plugin marketplace add btucker/blindspots
# Install the plugin
claude plugin install blindspots@blindspots
/dogfood from within Claude Code.Running any command for the first time triggers interactive setup. It reads your
project, asks a few questions, and generates .blindspots/config.md and
.blindspots/personas.md. You can also run /setup directly to regenerate.
A generated config looks something like:
## Setup
npm run dev &
## Start
http://localhost:3000
## Specs
- SPECS.md
## Start tells the persona how to begin — a URL for webapps, a command for
CLI tools, whatever makes sense for your product.
| Section | Purpose |
|---|---|
## Explore | Features and flows to test |
## Diagnose | Where to look when things break |
## Test | Test framework and conventions |
Generated automatically on first run from your project context and web research
about your target audience. Saved to .blindspots/personas.md — check it in,
edit it, make them yours.
/dogfood, /user-trial, and /experiment pick a random persona unless you
pass --persona "name". /interview shows you the list and lets you choose.
npx claudepluginhub btucker/blindspots --plugin blindspotsClaude Code plugin for tracegrep-aware search with call-graph context. Includes a skill for tg-based search, plus hooks for search guidance (PreToolUse), call-graph annotations (PostToolUse), and session context injection (SessionStart).
Persona-based user testing agent that simulates realistic user interactions with web applications. Embodies different user archetypes (Boomers, Millennials, Gen Z, Gen Alpha) with authentic behaviors, timing patterns, and frustration triggers to identify UX issues before real users do.
Use this agent when conducting user research, analyzing user behavior, creating journey maps, or validating design decisions through testing. This agent specializes in understanding user needs, pain points, and behaviors to inform product decisions within rapid development cycles. Examples:\n\n<example>\nContext: Understanding user needs for a new feature
User-centered design and product excellence. Master user research, UX design, accessibility, product strategy, user journey mapping, and inclusive design practices.
Advanced PM skills: AI Product Canvas, Multi-Source Signal Synthesiser, Experiment Designer, Design Handoff Brief. For senior PMs working on complex or AI-powered products.
Plan and execute design validation through prototyping strategies, usability testing, heuristic evaluation, and A/B experiments.
User researcher — interviews, personas, Jobs-to-Be-Done, and customer feedback synthesis