Update prompt to detailed intern-level walkthrough; analyze all 4-part eLegal video

This commit is contained in:
2026-05-13 11:41:05 -07:00
parent 9bd45ae160
commit 01717a8ece
9 changed files with 362 additions and 19 deletions

View File

@@ -42,28 +42,46 @@ OPENROUTER_BASE = "https://openrouter.ai/api/v1"
DEFAULT_MODEL = os.getenv("OPENROUTER_MODEL", "~google/gemini-flash-latest")
UX_PROMPT = """\
Analyze this screen recording like a UX researcher.
Write extremely detailed step-by-step instructions for an entry-level intern
who must execute this workflow flawlessly on their first try. No shortcuts,
no assumptions, no "the user knows to…" phrases. Every action must be explicit.
Track:
- user goals
- hesitation
- repeated actions
- likely confusion
- unnecessary clicks
- context switching
- inefficient workflow patterns
- UI discoverability issues
- moments where expectations appear violated
Treat every click, hover, scroll, tab switch, and window interaction as a
mandatory instruction.
Output:
1. overall workflow summary
2. friction timeline
3. inferred user intent
4. UX issues ranked by severity
5. suggested improvements
Your output MUST follow this exact structure:
Be specific about UI elements, button labels, menu paths, and exact behaviors
you observe throughout the video.
## Step 1: [Phase name — e.g., "Prepare and gather documents"]
For each sub-step, include:
- **What the user sees** on screen at that moment (name the page, the visible fields,
any buttons, menus, or notifications)
- **Exactly what to do** (e.g. "Click the button labeled 'File and Serve' in the left sidebar"
— never just "click the file button")
- **What should appear next** so they know they did it right
- **Where to find the next target** if it's not immediately visible (scroll down, expand menu, etc.)
- **Exact text to look for or avoid** (button labels, field names, error messages)
If the user hesitates, clicks the wrong thing, backtracks, or encounters an error,
record it as a separate sub-step labeled:
- ⚠️ **Stumble:** [what went wrong]
- 🛑 **Fix:** [how they recovered]
- Or if it's a clear mistake you'd want the intern to avoid:
- ⚡ **Pitfall:** [what not to do and why]
If the user opens another application, switches tabs, or refers to an external
reference, note this as a context switch and explain exactly how they return.
After the full walkthrough, add:
## UX Issues Found (severity-ranked)
| Severity | Issue | Where it happens | Why it's confusing |
|----------|-------|------------------|--------------------|
## Suggested Improvements
1. [Actionable improvement]
2. [Actionable improvement]
3. [etc.]
"""