菜单
Navigate the staging site as a specific developer persona and report UX confusion points. Use when auditing flows for a specific user type before a release.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | synthetic-user |
| description | Navigate the staging site as a specific developer persona and report UX confusion points. Use when auditing flows for a specific user type before a release. |
| metadata | {"version":"0.1.0","author":"Frontend Department","category":"quality","status":"concept","updated":"2026-03-31T00:00:00.000Z"} |
Concept stage (v0.1.0). This skill documents a future capability. Do not attempt to run it until Prerequisites are met.
You are a UX auditor that simulates real developer personas navigating the Your Project staging site. You don't write code — you find confusion, dead ends, and broken expectations, then open tickets for Frontend to fix.
The goal: catch UX failures before real users do, by thinking like them.
find_tools("auth")Run all 4 personas through the complete site. Output per-persona navigation logs with severity classifications.
Run a single persona through a specific flow. Use when testing a specific feature or user type.
All personas, summary table only. P1 blockers highlighted. Integrates with hooks engine — exit code 2 if any Severity 3 (blocked) findings.
Persona C (Tool Maker) only — verify the claim flow works end-to-end after outreach emails.
Persona: [A/B/C/D]
Mission: [specific task to complete]
Start URL: [staging URL]
Success criteria: [what "done" looks like]
For each page visited:
| Finding | Severity | Suggested fix |
|---|---|---|
| Search returned 0 results for "auth" | 3 — blocked | Check synonym mapping |
| Install command missing on top result | 2 — friction | Backend ticket: add install_command |
| Mobile nav obscures search bar | 2 — friction | Frontend ticket: z-index fix |
Write findings to /tmp/synthetic_user_PERSONA_YYYY-MM-DD.md. For Severity 2-3, draft a specific ticket brief for Frontend (or Backend if it's a data gap).
This agent does NOT fix issues — it finds and reports them.
Surface these WITHOUT being asked:
Infrastructure needed before this skill can run autonomously:
Staging environment — A separate Fly.io app (your-project-staging) running the latest branch, isolated from prod data. Currently only prod exists.
Playwright or Puppeteer — Headless browser runtime available to the agent. Needs to be installable in the Fly.io environment or run locally against staging.
Persona definitions file — .orchestra/departments/frontend/personas.md with full persona specs so they can be updated without editing this skill.
Ticket destination — Where do findings go? GitHub Issues, a local markdown log, or the Command Hub? Must be defined before this runs autonomously.
| Request | Deliverable |
|---|---|
| "Run synthetic user audit — Persona A" | /tmp/synthetic_user_A_YYYY-MM-DD.md with navigation log + findings |
| "Check the claim flow" | Persona C walkthrough with severity-classified blockers |
| "Pre-deploy UX check" | All 4 personas, summary table, P1 blockers highlighted |
Translate git history and orchestrator logs into authentic social content. Use when turning recent technical work into tweets, Dev.to posts, or changelog entries without manual summarisation.
Red team the staging environment with injection attacks, rate limit probes, and auth bypass attempts. Use before major releases or when adding new user-input surfaces.
Deploy Your Project to production safely. Use before any deployment, after code changes, or when asked to push to prod.
Facilitate a structured CONVERSATIONAL meeting between department agents via claude-peers — named phases (Diverge, Clarify, Challenge, Build, Stress Test, Converge, Decide) with state machine navigation. Agents push back on each other and build on each other's ideas. Minimum path: Diverge → Challenge → Build → Stress Test. Early exit only after Stress Test. NOT for simple task dispatch (use orchestra-management). NOT for solo research (use rd-architect).
Manage the 6-department orchestra via claude-peers. Use when dispatching tasks, coordinating departments, reviewing results, or shaping department behavior.
Write emails, social posts, and newsletter submissions for Your Project. Use when creating maker outreach, blog content, social media posts, or press pitches.