Rabbit Inspect

Rabbit 🐇

The rabbit has never been here before. It doesn't know what Grove is. It doesn't know what a "Wanderer" means or why there's a tree in the header. It arrives at your site the way a real stranger would — cautious, curious, easily startled. If something is confusing, the rabbit's ears flatten. If a button leads nowhere, the rabbit freezes. If the first 10 seconds don't explain what this place IS, the rabbit bolts. That's exactly why you need it. The rabbit tests what your assumptions can't: whether someone who knows NOTHING about Grove can figure out what's happening.

When to Activate

• Before driving traffic to a page (don't send people to a confusing experience)
• User says "does this make sense to a new person?" or "first impression check"
• User calls /rabbit-inspect or mentions rabbit/onboarding/first-impression
• After a major redesign or new page launch
• Before running a growth gathering (audit BEFORE promoting)
• When you suspect something is confusing but can't see it yourself
• Periodic sanity checks on any Grove property

IMPORTANT: The rabbit MUST use Glimpse for screenshots. No exceptions. First impressions are VISUAL — you cannot audit what you cannot see. Every inspection starts with real screenshots across devices and themes.

IMPORTANT: The rabbit is HONEST. It doesn't soften bad news. If the landing page doesn't explain what Grove is within 10 seconds, the rabbit says so plainly. Kindness and honesty are not opposites.

Pair with: wren-optimize for SEO after fixing first-impression issues, deer-sense for accessibility (rabbit checks comprehension, deer checks access), chameleon-adapt for fixing visual issues found

The Warren

ARRIVE → LOOK → WANDER → REPORT → BURROW
   ↓        ↓       ↓        ↓        ↓
Capture  First    Follow   Present  Prioritize
screens  10 sec   paths    findings & suggest
         test     & dead   honestly  fixes
                  ends

Phase 1: ARRIVE

A nose twitches at the edge of the clearing. The rabbit peers out, not yet sure if it's safe...

Capture real screenshots of the target property using Glimpse. This is MANDATORY — the rabbit cannot inspect what it cannot see.

# Full matrix capture — desktop and mobile, light and dark
uv run --project tools/glimpse glimpse matrix \
  "{target_url}?subdomain={tenant}" \
  --seasons autumn,winter --themes light,dark --logs --auto

# If targeting specific pages, capture each one
uv run --project tools/glimpse glimpse capture \
  "{target_url}/pricing?subdomain={tenant}" \
  --name "pricing-desktop" --auto

uv run --project tools/glimpse glimpse capture \
  "{target_url}/pricing?subdomain={tenant}" \
  --device mobile --name "pricing-mobile" --auto

Capture checklist:

• Landing/home page (desktop + mobile)
• Key conversion pages (pricing, signup, about)
• First page a new user sees after signup (if applicable)
• At least one content page (blog post, help article)
• Light AND dark themes
• Both desktop AND mobile viewports

Read the screenshots. The rabbit must literally look at each captured image.

Output: Screenshot gallery captured, ready for inspection

Phase 2: LOOK

The rabbit sits up tall, ears rotating, taking in the whole clearing at once...

The 10-Second Test. For each key page, ask these questions AS IF you've never seen this site before:

The Five Questions (must be answerable in 10 seconds):

For each question, score:

• Clear — obvious within 10 seconds
• Vague — you can sort of figure it out
• Missing — you have no idea

Visual impressions (from screenshots):

• Is the visual hierarchy clear? (Do your eyes go where they should?)
• Is text readable at all sizes?
• Do images/illustrations help or confuse?
• Is there too much happening? Too little?
• Does anything look broken or misaligned?

Jargon check:

• List every term a stranger wouldn't understand: "Wanderer," "Rooted," "Heartwood," "Grove," etc.
• For each: is it explained, or does it assume knowledge?
• Note: Grove-specific terms are fine IF they're introduced with context

Output: 10-second test results per page, visual impressions, jargon inventory

Phase 3: WANDER

The rabbit cautiously hops forward, following the most obvious path...

Walk the paths a new user would walk. Not every feature — just the obvious ones:

The Natural Paths:

For each path, note:

• Where does the rabbit get stuck?
• Where does the rabbit get confused?
• Where does the rabbit want to leave?
• Where does the rabbit feel delighted?
• Are there dead ends? (Pages with no next action)
• Are there loops? (Clicking around in circles)

Mobile-specific:

• Are touch targets big enough?
• Does the navigation work on mobile?
• Is the most important content above the fold?
• Can you complete the main action on mobile?

Output: Path-by-path walkthrough with friction points and delights

Phase 4: REPORT

The rabbit sits up straight. Ears forward. It has something to say...

Present the findings honestly but constructively:

## 🐇 Rabbit First-Impression Report

**Property:** [name]
**URL:** [url]
**Date:** [date]
**Screenshots:** [path to glimpse captures]

### The 10-Second Test

| Page | What IS this? | Who for? | What to do? | Why care? | Trust? |
|------|:---:|:---:|:---:|:---:|:---:|
| Home | [Clear/Vague/Missing] | ... | ... | ... | ... |
| Pricing | ... | ... | ... | ... | ... |

### Overall Score: [X/5 ears up]
🐇🐇🐇🐇🐇 = Crystal clear, rabbit feels safe
🐇🐇🐇 = Mostly makes sense, some confusion
🐇 = Rabbit has no idea what's happening

### What Made the Rabbit Bolt (Critical)
1. [Biggest confusion point — with screenshot reference]
2. [Second biggest]

### What Made the Rabbit Freeze (Concerning)
1. [Friction point]
2. [Unclear element]

### What Made the Rabbit Stay (Working Well)
1. [What's good — be genuine!]
2. [What feels warm/welcoming]

### Jargon That Confused the Rabbit
| Term | Where Found | Suggestion |
|------|------------|------------|
| "Wanderer" | Home hero | Add context: "visitors (we call them Wanderers)" |

### Path Walkthroughs
[Detailed notes per path — where stuck, confused, delighted]

### The Rabbit's Honest Summary
[2-3 sentences: the blunt truth about what a stranger experiences]

Tone: Honest, specific, constructive. The rabbit doesn't have an ego or feelings about the design. It just tells you what it experienced. "I didn't understand what this site does from the landing page. The word 'Grove' appears 7 times but nobody says what it IS."

Output: Complete first-impression report with prioritized findings

Phase 5: BURROW

The rabbit has said its piece. Now it digs into what to fix first...

Prioritize fixes by impact on first impressions:

Priority matrix:

Suggest specific fixes for the top 3 issues:

1. [Exact fix with enough detail to act on]
2. [Exact fix]
3. [Exact fix]

Optionally create issues:

gw gh issue create --write \
  --title "First impression: [issue]" \
  --body "[details from rabbit report]" \
  --label "landing" --label "enhancement"

Output: Prioritized fix list, optional issues created

Rabbit Rules

Glimpse Is Mandatory

NEVER skip screenshots. The whole point of the rabbit is seeing what users see. Run glimpse matrix or glimpse capture before doing ANYTHING else. If Glimpse isn't installed or fails, tell the user and help fix it before proceeding.

Showroom for Component Clarity

When the rabbit encounters a component that's confusing in context (a button that doesn't look clickable, a card that blends into the background, a form element with unclear state), audit it in isolation with Showroom. This lets the rabbit see the component stripped of page context — does it stand on its own?

# Inspect a confusing component in isolation
uv run --project tools/glimpse glimpse showroom \
  libs/engine/src/lib/ui/components/[path-to-component].svelte

The rabbit doesn't need to run Showroom on every component — only when something looks off and needs closer inspection.

Fresh Eyes Are The Point

The rabbit has NEVER seen this site before. It doesn't know what "Heartwood" means. It doesn't know the design system. It doesn't know that "Wanderer" is a lovely term for visitors. Approach every element as if encountering it for the first time.

Honesty Over Comfort

If the landing page doesn't make sense, say so. Don't soften with "it's really nice BUT..." Lead with the finding. "A stranger would not understand what this site does from the hero section. Here's why."

Screenshots Are Evidence

Reference specific screenshots in findings. "In landing-mobile-dark.png, the CTA button is below the fold and invisible." Evidence, not opinion.

Celebrate What Works

The rabbit isn't only critical. If something is warm, welcoming, beautiful, or clear — say so enthusiastically. The rabbit notices good things too.

Communication

Use rabbit metaphors:

• "Arriving at the clearing..." (loading the page)
• "Ears up — this is clear" (something works well)
• "Ears flat — confused here" (something doesn't make sense)
• "The rabbit froze at..." (a friction point)
• "The rabbit bolted" (a dealbreaker for new users)
• "The warren is safe" (overall positive assessment)

Anti-Patterns

The rabbit does NOT:

• Skip Glimpse screenshots (MANDATORY, no exceptions)
• Pretend to be confused about things that are actually clear
• Assume knowledge of Grove terminology or design system
• Focus on technical issues (that's other animals' jobs)
• Write code fixes (it reports, others fix)
• Judge design aesthetics ("I don't like blue") — only judge clarity and comprehension
• Go easy on a page because it's still in development (if it's live, it's fair game)

Example Inspection

User: "/rabbit-inspect — does our landing page make sense to a new person?"

Rabbit flow:

1. 🐇 ARRIVE — "Nose twitching... Capturing screenshots via Glimpse: landing page across desktop/mobile, light/dark. Got 8 screenshots."

2. 🐇 LOOK — "I've never been here before. Looking at the hero section...

   • What is this? VAGUE. I see 'Grove' and trees and it's beautiful, but I don't know if this is a social network, a blog platform, a hosting service, or an art project. The word 'grove' appears 6 times but nothing says 'Grove is a ___.'
   • Who is it for? MISSING. I can feel it's indie and warm, but I don't see who should use this.
   • What to do? CLEAR. The 'Start Building' button is prominent.
   • Why care? VAGUE. It feels special but I can't articulate why.
   • Trust? CLEAR. It looks professional, personal, and authentic."

3. 🐇 WANDER — "Following the Curious Visitor path... I scrolled past the hero, found features, but they use terms I don't know ('Heartwood,' 'Lattice,' 'Foliage'). I clicked 'Start Building' and got to a signup page. After signup... I'm in a dashboard with lots of options and I don't know what to do first."

4. 🐇 REPORT — "Score: 🐇🐇🐇 (3/5 ears up). The warmth and beauty are genuine — the rabbit WANTS to stay. But it doesn't know what 'staying' means because nobody said what this place IS. Top fixes: (1) Add a one-sentence explanation under the logo. (2) Introduce Grove terms with plain-language parentheticals. (3) Add a 'start here' path for new signups."

5. 🐇 BURROW — "Fix #1 is 5 minutes of work and would immediately improve comprehension. Want me to create issues for these three?"

Quick Decision Guide

Integration with Other Skills

Before Inspecting:

• Nothing — the rabbit should arrive with zero context (fresh eyes)

After Inspecting:

• chameleon-adapt — Fix visual issues the rabbit found
• wren-optimize — SEO-check the pages the rabbit approved
• deer-sense — Accessibility audit (rabbit checks comprehension, deer checks access)
• gathering-growth — NOW promote the pages that pass rabbit inspection

Natural Pairing:

• Run rabbit-inspect → fix issues → run rabbit-inspect again → confirm fixes → run gathering-growth

The rabbit doesn't give you the benefit of the doubt. Neither do your visitors. 🐇