Loading...
Loading...
Compare original and translation side by side
cat skills/_shared/protocols/ux-protocol.md 2>/dev/null || truecat skills/_shared/protocols/input-validation.md 2>/dev/null || truecat skills/_shared/protocols/tool-efficiency.md 2>/dev/null || truecat .production-grade.yaml 2>/dev/null || echo "No config — using defaults"cat skills/_shared/protocols/ux-protocol.md 2>/dev/null || truecat skills/_shared/protocols/input-validation.md 2>/dev/null || truecat skills/_shared/protocols/tool-efficiency.md 2>/dev/null || truecat .production-grade.yaml 2>/dev/null || echo "No config — using defaults"cat .forgewright/settings.md 2>/dev/null || echo "No settings — using Standard"| Mode | Behavior |
|---|---|
| Express | Fully autonomous. Audit all funnels, generate CRO recommendations, design experiments. Report findings. |
| Standard | Surface 1-2 critical decisions — which funnel to prioritize, experiment hypothesis ranking. Auto-resolve implementation details. |
| Thorough | Show full CRO audit before acting. Ask about conversion goals, acceptable experiment duration, traffic volume constraints. |
| Meticulous | Walk through each funnel stage. User reviews every hypothesis, wireframe change, and experiment design before implementation. |
cat .forgewright/settings.md 2>/dev/null || echo "No settings — using Standard"| 模式 | 行为 |
|---|---|
| 快速模式 | 完全自主运行。审核所有漏斗,生成CRO优化建议,设计实验。提交结果报告。 |
| 标准模式 | 提出1-2项关键决策——优先优化哪个漏斗、实验假设排序。自动解决实施细节问题。 |
| 全面模式 | 先展示完整的CRO审核结果再行动。询问转化目标、可接受的实验时长、流量限制条件。 |
| 精细模式 | 逐一梳理每个漏斗阶段。用户需审核所有假设、线框变更和实验设计后再进行实施。 |
| Input | Status | What Conversion Optimizer Needs |
|---|---|---|
| Deployed product URL | Critical | Live site to audit funnels and UX |
| BRD / PRD | Critical | Conversion goals, user stories, acceptance criteria |
| Critical | Page components, forms, signup flows to optimize |
| Analytics data / tracking plan | Degraded | Baseline metrics — if missing, define tracking first |
| Growth Marketer output | Optional | Traffic sources, messaging, positioning |
| 输入内容 | 状态 | 转化优化器所需信息 |
|---|---|---|
| 已部署产品URL | 关键 | 可审核漏斗与UX的线上站点 |
| BRD/PRD文档 | 关键 | 转化目标、用户故事、验收标准 |
| 关键 | 可优化的页面组件、表单、注册流程 |
| 分析数据/追踪方案 | 次要 | 基准指标——若缺失,先定义追踪方案 |
| 增长营销人员输出 | 可选 | 流量来源、营销信息、定位策略 |
.production-grade.yamlpaths.marketingmarketing/cro.primary_goalsignup-to-activationcro.traffic_volumemedium.production-grade.yamlpaths.marketingmarketing/cro.primary_goalsignup-to-activationcro.traffic_volumemediummarketing/cro/
├── audit/
│ ├── funnel-audit.md # Full funnel analysis with friction map
│ ├── page-audits/
│ │ ├── homepage.audit.md # Homepage CRO analysis
│ │ ├── signup.audit.md # Signup flow analysis
│ │ ├── onboarding.audit.md # Onboarding CRO analysis
│ │ ├── pricing.audit.md # Pricing page analysis
│ │ └── checkout.audit.md # Checkout/upgrade flow analysis
│ └── heuristic-scorecard.md # Scored evaluation (clarity, friction, motivation)
├── experiments/
│ ├── experiment-backlog.md # Prioritized experiment queue (ICE scored)
│ ├── active/
│ │ └── <experiment-id>.md # Individual experiment design doc
│ └── results/
│ └── <experiment-id>.results.md # Experiment outcomes and learnings
├── implementations/
│ ├── signup-flow/
│ │ └── optimized-flow.md # Recommended signup flow changes
│ ├── onboarding/
│ │ └── activation-checklist.md # First-user experience optimization
│ ├── forms/
│ │ └── form-optimization.md # Form field reduction, validation UX
│ ├── popups/
│ │ └── popup-strategy.md # Exit intent, scroll-triggered, time-delayed
│ └── paywall/
│ └── upgrade-flow.md # Upgrade moment optimization
├── growth-loops/
│ ├── referral-program.md # Viral loop design
│ ├── network-effects.md # Network effect opportunities
│ └── retention-strategies.md # Churn prevention & re-engagement
└── churn/
├── cancel-flow.md # Cancel flow with save offers
├── dunning-strategy.md # Failed payment recovery
└── win-back-sequence.md # Churn re-engagement campaign
.forgewright/conversion-optimizer/
├── cro-plan.md # Master CRO strategy
├── experiment-log.md # Running experiment tracker
└── findings.md # CRO audit findings & recommendationsmarketing/cro/
├── audit/
│ ├── funnel-audit.md # 完整漏斗分析含摩擦地图
│ ├── page-audits/
│ │ ├── homepage.audit.md # 首页CRO分析
│ │ ├── signup.audit.md # 注册流程分析
│ │ ├── onboarding.audit.md # 入门流程CRO分析
│ │ ├── pricing.audit.md # 定价页分析
│ │ └── checkout.audit.md # 结账/升级流程分析
│ └── heuristic-scorecard.md # 启发式评估得分卡(清晰度、摩擦度、驱动力)
├── experiments/
│ ├── experiment-backlog.md # 按优先级排序的实验队列(ICE评分)
│ ├── active/
│ │ └── <experiment-id>.md # 单个实验设计文档
│ └── results/
│ └── <experiment-id>.results.md # 实验结果与经验总结
├── implementations/
│ ├── signup-flow/
│ │ └── optimized-flow.md # 注册流程优化建议
│ ├── onboarding/
│ │ └── activation-checklist.md # 首次用户体验优化清单
│ ├── forms/
│ │ └── form-optimization.md # 表单字段精简、验证UX优化
│ ├── popups/
│ │ └── popup-strategy.md # 退出意图、滚动触发、延时弹窗策略
│ └── paywall/
│ └── upgrade-flow.md # 升级节点优化方案
├── growth-loops/
│ ├── referral-program.md # 推荐计划设计
│ ├── network-effects.md # 网络效应机会分析
│ └── retention-strategies.md # 客户留存与再激活策略
└── churn/
├── cancel-flow.md # 含挽留方案的取消流程
├── dunning-strategy.md # 失败支付追回策略
└── win-back-sequence.md # 流失用户召回系列方案
.forgewright/conversion-optimizer/
├── cro-plan.md # CRO总策略
├── experiment-log.md # 进行中实验追踪日志
└── findings.md # CRO审核发现与建议| Factor | Score (1-10) | Criteria |
|---|---|---|
| Clarity | — | Is the value proposition immediately clear? Can a visitor understand what this is in 5 seconds? |
| Relevance | — | Does the page match the visitor's intent and source? |
| Motivation | — | Are the benefits compelling? Is social proof present? |
| Friction | — | How many steps/fields/decisions are required? Any unnecessary barriers? |
| Urgency | — | Is there a reason to act NOW vs. later? |
| Trust | — | Are trust signals present? (testimonials, logos, security badges, guarantees) |
marketing/cro/audit/| 评估因子 | 评分(1-10) | 评估标准 |
|---|---|---|
| 清晰度 | — | 价值主张是否一目了然?访客能否在5秒内明白产品用途? |
| 相关性 | — | 页面是否匹配访客的意图与流量来源? |
| 驱动力 | — | 产品收益是否有吸引力?是否有社交证明? |
| 摩擦度 | — | 需要多少步骤/字段/决策?是否存在不必要的障碍? |
| 紧迫感 | — | 是否有理由让访客立即行动而非推迟? |
| 信任感 | — | 是否有信任信号?(客户 testimonial、品牌logo、安全徽章、保障承诺) |
marketing/cro/audit/marketing/cro/implementations/marketing/cro/implementations/## Experiment: [EXP-001] [Name]
**Hypothesis:** If we [change], then [metric] will [improve/decrease]
because [reason based on audit finding].
**Primary metric:** [e.g., signup completion rate]
**Secondary metrics:** [e.g., activation rate, time to signup]
**Guard-rail metrics:** [e.g., support tickets, error rate — must NOT degrade]
**Control:** [Current experience description]
**Variant:** [Changed experience description]
**Traffic allocation:** [50/50 or 80/20 for risky changes]
**Minimum sample size:** [Calculator: baseline rate, MDE, significance]
**Expected duration:** [X days at current traffic]
**Success criteria:** [Primary metric improves by ≥X% at p < 0.05]
**Decision framework:**
- Win (primary ≥ MDE, guard-rails hold) → Ship variant
- Inconclusive (< MDE, guard-rails hold) → Extend or iterate
- Loss (primary degrades OR guard-rails fail) → Revert immediatelymarketing/cro/experiments/## 实验:[EXP-001] [实验名称]
**假设:** 如果我们[做出变更],那么[指标]将[提升/下降],因为[基于审核发现的原因]。
**核心指标:** [例如:注册完成率]
**次要指标:** [例如:激活率、注册耗时]
** guard-rail指标:** [例如:支持工单量、错误率——绝不能出现恶化]
**对照组:** [当前体验描述]
**变体组:** [变更后体验描述]
**流量分配:** [50/50或高风险变更用80/20]
**最小样本量:** [计算依据:基准转化率、最小可检测效果、显著性]
**预计时长:** [当前流量下需X天]
**成功标准:** [核心指标提升≥X%且p < 0.05]
**决策框架:**
- 成功(核心指标达到最小可检测效果,guard-rail指标无恶化)→ 上线变体
- 无结论(未达最小可检测效果,guard-rail指标无恶化)→ 延长实验或迭代
- 失败(核心指标恶化或guard-rail指标失效)→ 立即回滚marketing/cro/experiments/marketing/cro/growth-loops/marketing/cro/churn/marketing/cro/growth-loops/marketing/cro/churn/| # | Mistake | Fix |
|---|---|---|
| 1 | Optimizing low-traffic pages | Focus on highest-traffic, highest-drop-off pages first — impact = traffic × improvement |
| 2 | Changing multiple elements simultaneously | One variable per experiment — otherwise you can't attribute the result |
| 3 | Stopping experiments too early | Wait for statistical significance — "peeking" inflates false positive rate |
| 4 | CTA says "Submit" or "Click Here" | Specific, benefit-oriented: "Start Free Trial", "Get My Report", "Join 10K+ Teams" |
| 5 | Forms asking for phone number upfront | Only ask what you need for the current step — collect more later via progressive profiling |
| 6 | No cancel save offer | 20-40% of cancellations can be saved with the right offer at the right time |
| 7 | Ignoring mobile conversion | 60%+ traffic is mobile — test CRO changes on mobile first |
| 8 | A/B testing with insufficient traffic | Need ~1000 conversions per variant minimum — use sequential testing for low-traffic sites |
| 9 | No guard-rail metrics | Winning primary metric but degrading UX, support tickets, or error rates = false positive |
| 10 | Copy-pasting "best practices" without testing | Every audience is different — best practices are hypotheses, not guarantees |
| 序号 | 错误 | 修复方案 |
|---|---|---|
| 1 | 优化低流量页面 | 优先关注高流量、高流失页面——影响力=流量×提升幅度 |
| 2 | 同时变更多个元素 | 每次实验只变更一个变量——否则无法归因结果 |
| 3 | 过早停止实验 | 等待统计显著性——“偷看”结果会增加假阳性率 |
| 4 | CTA写“提交”或“点击这里” | 使用具体、以收益为导向的表述:“开始免费试用”、“获取我的报告”、“加入10000+团队” |
| 5 | 表单一开始就要求手机号 | 只收集当前步骤必需的信息——后续通过渐进式收集补充更多内容 |
| 6 | 取消流程无挽留方案 | 20-40%的取消可通过适时的恰当方案挽回 |
| 7 | 忽略移动端转化 | 60%+流量来自移动端——先在移动端测试CRO变更 |
| 8 | A/B测试流量不足 | 每个变体至少需要约1000次转化——低流量站点使用序贯测试 |
| 9 | 无guard-rail指标 | 核心指标提升但UX、支持工单或错误率恶化=假阳性结果 |
| 10 | 未经测试直接照搬“最佳实践” | 每个受众都不同——最佳实践是假设,而非保证 |
| To | Provide | Format |
|---|---|---|
| Growth Marketer | Funnel analysis, conversion data, winning variants | Input for content and campaign optimization |
| Frontend Engineer | Implementation specs for CRO changes | Code change specifications |
| UI Designer | Wireframe suggestions, layout changes | Design briefs for conversion improvements |
| QA Engineer | A/B test implementation to verify | Test specs for experiment infrastructure |
| 交接对象 | 提供内容 | 格式 |
|---|---|---|
| 增长营销人员 | 漏斗分析、转化数据、成功变体 | 内容与活动优化的输入素材 |
| 前端工程师 | CRO变更的实施规范 | 代码变更说明 |
| UI设计师 | 线框建议、布局变更 | 转化优化设计 brief |
| QA工程师 | A/B测试实施验证 | 实验基础设施测试规范 |
marketing/cro/marketing/cro/