Example

This section includes an example from a real recorded validation testing session. It showcases the terminal output and Claude's response when using the plugin.

The command

Point the plugin at your product and ask in plain language:

> /archetype:validation validate the signup flow on the Lumina Notes demo app
  url=http://localhost:8321

Token usage

Depending on the page size and test depth, the token usage of a test session may vary between 30k and 200k.

Step 1 — Set up

If the session isn't connected yet, start_run opens the login wizard on its own — you approve once in the browser and the token is saved:

MCP server "plugin:archetype:archetype-setup" requests your input

Connect to Archetype

1) Your browser should open to this URL automatically. If it didn't, open it
   manually: https://www.syntheticarchetype.com/device-auth?user_code=FXBB-KWMW
2) Verification code (shown for cross-check): FXBB-KWMW
3) Once you've approved in the browser, tick the box below and click Accept.

  ✔ I've approved the request in my browser  →  Accept

Step 2 — Persona generation

The start_run result is a full mission brief: a first-person persona card, numbered scenarios with expected results, conduct rules, and the reporting contract. This run drew Persona A:

I am Persona A. You are a Senior Project Manager at a fast-scaling tech startup who is under pressure to find a resource management tool by the end of the week. You have no patience for broken interfaces or hidden pricing […] If a button doesn't respond instantly, I'll spam-click it out of habit. Browsing habits: aggressively closes tabs the moment a site fails; uses Ctrl+F to find "pricing"; very fast skimmer — headers and bolded text only.

Each scenario is concrete enough to act and grade:

1. [SC-1] High-Speed SSO Onboarding
   - Click the 'Sign Up' button in the top navigation bar
   - Click the 'Continue with Google' button to bypass manual form entry
   - …
   Expected: the user is dropped directly into a functional dashboard
   without being forced to complete a multi-step tutorial.

Step 3 — Testing

Claude drives Chrome through each scenario as Persona A, narrating honestly:

⏺ Pricing is visible mid-page ($0 / $12 / $29) — Persona A approves of that at
  least. Still hunting for the actual signup form. Scrolling on.

⏺ Found the "Create your account" form — Full name, Work email, Password.
  Persona A's eyes scan for a "Continue with Google" button…

⏺ The Pro "Start free trial" button also just sets #signup without scrolling —
  the page doesn't move. Persona A spam-clicks it once more out of habit, then
  gives up and scrolls down to the form manually.

Step 4 — Reporting

When the scenarios are done, the plugin submits a structured report — every step with its narration, per-scenario status, and an overall verdict:

Scenario	Title	Status	What actually happened
SC-1	High-Speed SSO Onboarding	blocked	No "Sign Up" nav button and no Google/SSO option exist — the manual form is the only path
SC-2	Pricing Transparency & Trial	fail	Pricing is clear ($0/$12/$29, no credit card) — but the Pro trial CTA only flips the URL hash, and signup ends in a toast with no trial state
SC-3	Efficiency-First Form	fail	Empty submit returns one generic "Something went wrong" banner — no field-level errors

"The pricing is honest and the form is short — but half the buttons on this page don't visibly do anything, and when I fat-finger the form it just shrugs 'something went wrong'. This one's getting the tab closed."

Findings

Ranked by severity:

• Critical: signup dead-ends — account creation yields a transient toast; no session, dashboard, or next step follows.
• High: all anchor navigation is broken — nav links and CTAs update the URL hash but never scroll, so every primary button feels dead.
• High: empty form submission returns one generic error with no field-level validation; CTAs aren't real links/buttons in the accessibility tree.
• The product's one consistent strength: transparent pricing with no credit-card requirement.

Check on it later

Every run lives in your account — in the terminal or the Web Portal Test Hub:

> /archetype:check-run-status dbb06fd3c666479fb5d8b907941cedc5

⏺ Run dbb06fd3… is completed · 100%, and analytics are ready.
  Verdict: mixed — basic manual signup technically works and pricing is
  transparent, but the flow around it is rough: every nav/CTA anchor link
  only changes the URL hash without scrolling, there's no SSO signup, and
  account creation ends in a toast with no dashboard…

That's the whole loop: one sentence in, a persona-driven browser session, and a graded, structured verdict out. Install it yourself in the Plugin Guide.