stuntdouble-basics

stuntdouble-basics:

• Stunt Double deploys AI agents with realistic user personas to validate user journeys at scale.
• Authentication is handled automatically via OAuth 2.1 with PKCE. No API keys or tokens are needed.
• Always specify a workspace when creating or listing resources. Use list_workspaces to find available workspaces.

Finding things:

• search is the fastest way to locate anything in a workspace: projects, actors, checklists, interviews, automations, issues, goals, feedback, actor knowledge, insights, design reviews, project resources and conversations, all in one ranked call.
• Prefer it over listing an entity type and filtering the list yourself. Narrow with types and project_id when you already know the shape of what you want.
• Search before you create. It is how you find the actor, checklist, or workflow that already covers the job instead of adding a near-duplicate.
• Search only ever returns entities from workspaces you are a member of; the boundary is enforced server-side, not by the filters you pass.

Actors:

• Actors represent AI user personas. Create actors with clear names (format: "FirstName - Role"), descriptions, and system prompts.
• Give actors knowledge via add_actor_knowledge so they understand your product context.
• Conversations are read-only over MCP (list_conversations, get_conversation); an actor chat is started from the dashboard. To probe actors for research, design reviews or concept testing, run an interview: it puts every persona through the same guide and synthesises the answers, which one-off chats cannot do.
• Create diverse actors covering different segments: new users, power users, enterprise, accessibility, mobile.

Workflows and checklists:

• Use workflows for multi-step user journey validation (signup, checkout, onboarding flows).
• Use checklists for point-in-time quality checks (accessibility, performance, content).
• Workflow and checklist runs are asynchronous. After triggering a run, poll get_workflow_run or get_checklist_run for results.
• Use create_workflow with trigger_type "schedule" or "webhook" for automated continuous validation.

Feedback:

• Review feedback items surfaced by Stunt Double and update their status as issues are triaged or resolved.
• Status lifecycle: new → reviewed → resolved (or dismissed for false positives).
• Cross-reference feedback with actors and workflows to identify patterns and coverage gaps.

Interviews:

• Interviews are structured user research rounds: a discussion guide (sections of questions and tasks) is run against a target URL by AI participants (existing actors or ad-hoc personas).
• Build the guide with add_interview_section and add_interview_item before launching. Each section should focus on one topic and contain ordered question or task items.
• Add participants with add_interview_participant — pass actor_id to reuse an existing actor, or persona_spec (name, bio, traits) for an ad-hoc persona.
• launch_interview is async — it returns a trigger run ID and flips the interview to running. Participants update independently; use get_interview and get_interview_participant to follow progress.
• Once participants complete, the synthesis task produces a report (summary, themes, recommendations, per-question rollup). Fetch it with get_interview_report, or call regenerate_interview_report after editing transcripts or re-running participants.

Guidelines (the standards a workspace holds itself to):

• A guideline is a standing rule (design system, tone of voice, brand, content, accessibility, compliance, security, performance, shared knowledge). It is owned by the workspace and attached to the projects it applies to, so one rule holds for several projects without being retyped or edited in several places.
• Whatever is in force for a project is rendered into every checklist run, design review, interview and triage for it. Read list_project_guidelines before writing checks, interview questions or design feedback, and assert the rules rather than restating or contradicting them.
• Two switches decide whether a rule is in force: the library's and the project attachment's. list_project_guidelines folds them into one enabled.
• Write a rule once with add_project_guideline (library plus this project) or add_workspace_guideline (library only), then hold other projects to the same rule with set_project_guideline rather than adding a near-duplicate. Check list_workspace_guidelines first.
• update_workspace_guideline with apply_to_design_reviews carries a rule to every design review in the workspace, including the Slack and Linear reviews that have no project to attach it through.
• Guidelines are project-wide standards; add_actor_knowledge is for what one actor needs to remember.