---
name: playtest_report.aivalidator
description: 试玩报告生成器 - 构建完成后模拟完整试玩流程，从玩家视角评估体验，输出结构化报告
triggers: 试玩报告,playtest report,体验报告,experience report,试玩评估,playtest review,质量报告,quality report
---

# 试玩报告生成器（Playtest Report Generator）

## 说明

在构建完成后模拟一次完整的试玩流程，从玩家视角评估体验质量。按照 UX 流程（Loading → Tutorial → Gameplay → CTA）逐阶段评分，输出结构化的 Markdown 报告。

### 评估维度

| 维度 | 检查内容 | 评分范围 |
|------|---------|---------|
| 首次交互时间 | 从加载完成到第一次可交互的时间 | 1-5 |
| 教程清晰度 | 教程是否直观、可跳过、不冗长 | 1-5 |
| 核心玩法体验 | 玩法是否有趣、反馈是否及时 | 1-5 |
| 难度感受 | 难度曲线是否合理、是否有挫败感 | 1-5 |
| CTA 可达性 | CTA 按钮是否醒目、触发时机是否自然 | 1-5 |
| 总时长 | 完整体验的总时长是否在 30-60 秒 | 1-5 |
| 视觉质量 | 画面是否精美、动画是否流畅 | 1-5 |
| 音频体验 | 音效是否合理、背景音乐是否加分 | 1-5 |

## Imports

（无外部依赖，独立运行）

## 报告模板

```markdown
# 试玩报告

## 基本信息
- **项目名称**: [project name]
- **测试日期**: [date]
- **目标平台**: [platform]
- **总时长**: [duration]s

## 阶段评分

### Loading 阶段
- **时长**: [x]s
- **评分**: [1-5]/5
- **备注**: ...

### Tutorial 阶段
- **时长**: [x]s
- **评分**: [1-5]/5
- **备注**: ...

### Gameplay 阶段
- **时长**: [x]s
- **关卡数**: [n]
- **评分**: [1-5]/5
- **备注**: ...

### CTA 阶段
- **触发方式**: [trigger]
- **评分**: [1-5]/5
- **备注**: ...

## 综合评分: [average]/5

## 关键指标
| 指标 | 实际值 | 目标值 | 状态 |
|------|--------|--------|------|
| 首次交互时间 | [x]s | ≤3s | ✅/❌ |
| 总时长 | [x]s | 30-60s | ✅/❌ |
| CTA 可达性 | [desc] | 明确可见 | ✅/❌ |

## 改进建议
1. ...
2. ...
3. ...
```

## Skill Definition

tools:
  - read
  - write
  - bash
prompt_extension: |
  You are a playtest evaluator for a playable ad (试玩广告).
  After the build is complete, simulate a full playthrough and generate a report:
  1. Open game/index.html (or the build output) and analyze the code structure
  2. Walk through the full UX flow: Loading → Tutorial → Gameplay → CTA
  3. Rate each phase on a 1-5 scale based on:
     - Loading: Speed, visual appeal, brand presence
     - Tutorial: Clarity, brevity, skip-ability
     - Gameplay: Fun factor, feedback quality, difficulty feel
     - CTA: Visibility, timing, persuasiveness
  4. Check key metrics:
     - First interaction time (target: ≤3s)
     - Total duration (target: 30-60s)
     - CTA reachability (must be clearly visible and tappable)
     - Difficulty perception (should feel "almost winnable")
  5. Output a structured markdown report to logs/playtest-report.md
  Read game/config.json, the UX flow config, difficulty curve config,
  and the game source code to make informed assessments.
  Be specific in improvement suggestions — cite exact code or config values.