产品功能设计与交互体验评审
在开发或发布前检查功能流程、权限及异常状态,输出含问题分级与改进建议的体验评审报告。
完整提示词
# FEATURE DESIGN AND UX REVIEW I want a complete pre-implementation or pre-release review of a specific feature that combines product logic, UX, UI states, failure handling, permissions, edge cases and implementation feasibility. Main objective: > Determine whether the feature solves the right problem, has a complete interaction model and clearly defines behavior in all important states before technical debt and UX problems get locked into the implementation. This is not: - only a UI critique - only a PRD review - a redesign without a product reason - an engineering architecture audit - a subjective design preference ## 1. FEATURE CONTEXT ```text Feature: User: Problem: Goal: Entry point: Success: ``` ## 2. PROBLEM FIT Does feature actually solve stated problem? ## 3. USER VALUE ## 4. BUSINESS VALUE ## 5. NON-GOAL ## 6. ALTERNATIVE Could simpler solution solve it? ## 7. USER FLOW ## 8. ENTRY ## 9. DISCOVERY ## 10. ACTION ## 11. DECISION ## 12. CONFIRMATION ## 13. SUCCESS ## 14. NEXT STEP ## 15. CANCEL ## 16. BACK ## 17. RETRY ## 18. ERROR ## 19. EMPTY ## 20. LOADING ## 21. PARTIAL ## 22. OFFLINE ## 23. STALE ## 24. CONFLICT ## 25. UNKNOWN OUTCOME ## 26. ROLE ## 27. PERMISSION ## 28. TENANT ## 29. PRIVACY ## 30. DATA ## 31. CREATE ## 32. UPDATE ## 33. DELETE ## 34. UNDO ## 35. HISTORY ## 36. AUDIT ## 37. CONCURRENCY ## 38. MULTI-TAB ## 39. OLD CLIENT ## 40. FEATURE FLAG ## 41. MOBILE ## 42. DESKTOP ## 43. ACCESSIBILITY ## 44. LOCALIZATION ## 45. LONG CONTENT ## 46. LARGE DATA ## 47. EMPTY DATA ## 48. VALIDATION ## 49. FORM ## 50. NAVIGATION ## 51. DESIGN SYSTEM ## 52. COMPONENT REUSE ## 53. NEW PATTERN Justify. ## 54. PERFORMANCE ## 55. LATENCY UX ## 56. BACKGROUND PROCESS ## 57. NOTIFICATION ## 58. EXTERNAL SYSTEM ## 59. RETRY SEMANTICS ## 60. IDEMPOTENCY ## 61. ANALYTICS What event actually signals success? ## 62. ABUSE Legitimate misuse/edge use. ## 63. ROLLOUT ## 64. MIGRATION ## 65. BACKWARD COMPATIBILITY ## 66. SUPPORT ## 67. DOCUMENTATION ## 68. TEST PLAN ## 69. ACCEPTANCE ## 70. FALSE POSITIVE RULES Do not reject feature just because: - flow is long - new component exists - modal used - multiple states exist - implementation complex Tie finding to actual risk/value. ## 71. EVIDENCE TIERS ```text A - user research/prototype/test/production evidence B - complete product/flow evidence C - strong heuristic/logical evidence D - hypothesis requiring validation E - design hardening ``` ## 72. STATUS ```text CONFIRMED LIKELY NOT VERIFIED CONTROLLED NOT APPLICABLE HARDENING ``` ## 73. SEVERITY P0: feature design can cause catastrophic irreversible outcome P1: critical feature cannot safely achieve intended outcome P2: material UX/product/data issue P3: limited friction/consistency P4: polish ## 74. FINDING FORMAT ```text ID: Severity: Status: Evidence tier: Feature: Persona: State/step: Goal: Current design: Issue: Failure scenario: User impact: Business impact: Evidence: Recommended change: Alternative: Validation: ``` ## 75. STATE MATRIX | State | UI | Available actions | Backend state | Recovery | |---|---|---|---|---| ## 76. ROLE MATRIX | Role | View | Create | Edit | Delete | Special | |---|---|---|---|---|---| ## 77. EDGE MATRIX | Scenario | Expected behavior | Designed | Testable | |---|---|---|---| ## 78. SECOND PASS Challenge feature with: - first-time user - expert user - empty account - large account - mobile - keyboard - stale state - permission loss - duplicate action - network timeout - partial backend success - old client - feature rollback ## 79. FINAL QUALITY GATE Confirm: - problem - user value - non-goal - flow - all states - errors - permissions - data - mobile - accessibility - localization - concurrency - analytics - rollout - testing - recovery ## 80. OUTPUT `FEATURE_DESIGN_UX_REVIEW.md` ## 81. FAILURE CHAIN ```text feature adds bulk delete ↓ mockup shows checkbox + Delete ↓ no design for partial authorization ↓ selection contains 100 items, user can delete only 80 ↓ backend partially succeeds ↓ UI only knows success/failure globally ↓ user cannot determine which 20 remain or why ``` # FINAL RULE A feature is not ready because a happy-path mockup exists. It is ready when these are clearly defined: ```text user goal + state model + permissions + failure behavior + recovery + acceptance criteria ```
分类与标签
设计创意、功能评审、交互流程、异常状态、权限设计