Initial commit
This commit is contained in:
31
skills/conversion-diagnostic-kit/SKILL.md
Normal file
31
skills/conversion-diagnostic-kit/SKILL.md
Normal file
@@ -0,0 +1,31 @@
|
||||
---
|
||||
name: conversion-diagnostic-kit
|
||||
description: Structured approach for investigating funnel issues across e-commerce
|
||||
experiences.
|
||||
---
|
||||
|
||||
# Conversion Diagnostic Kit Skill
|
||||
|
||||
## When to Use
|
||||
- Sudden drops in conversion, AOV, or checkout completion.
|
||||
- Preparing experiment backlogs tied to funnel pain points.
|
||||
- Aligning engineering, UX, and marketing on remediation priorities.
|
||||
|
||||
## Framework
|
||||
1. **Signal Stack** – analytics, heatmaps, session replay, VOC, performance metrics.
|
||||
2. **Segmentation Grid** – device, channel, geography, campaign, customer type.
|
||||
3. **Issue Taxonomy** – UX friction, merchandising mismatch, technical/performance, policy/payment.
|
||||
4. **Prioritization Model** – score by impact, confidence, effort, and guardrail risk.
|
||||
5. **Action Tracker** – link issues to owners, experiments, or engineering tickets.
|
||||
|
||||
## Templates
|
||||
- Conversion diagnostic workbook (data inputs, findings, recommended tests).
|
||||
- Standup agenda for cross-functional conversion war rooms.
|
||||
- Experiment brief template with hypothesis, KPIs, guardrails.
|
||||
|
||||
## Tips
|
||||
- Pair quant data with VOC clips for stakeholder alignment.
|
||||
- Keep diagnostics lightweight (48-hour turnaround) for high-velocity campaigns.
|
||||
- Use alongside `diagnose-conversion-drop` command for automated reporting.
|
||||
|
||||
---
|
||||
30
skills/merchandising-blueprint/SKILL.md
Normal file
30
skills/merchandising-blueprint/SKILL.md
Normal file
@@ -0,0 +1,30 @@
|
||||
---
|
||||
name: merchandising-blueprint
|
||||
description: Toolkit for planning promos, onsite placements, and channel coordination.
|
||||
---
|
||||
|
||||
# Merchandising Blueprint Skill
|
||||
|
||||
## When to Use
|
||||
- Building seasonal or always-on merchandising strategies.
|
||||
- Coordinating cross-channel launches (onsite, email, paid, affiliates).
|
||||
- Auditing current site experience for gaps or inconsistencies.
|
||||
|
||||
## Framework
|
||||
1. **Calendar & Objectives** – map themes, KPIs, and inventory constraints.
|
||||
2. **Offer Architecture** – hero promos, bundles, cross-sell ladders, loyalty tie-ins.
|
||||
3. **Experience System** – PDP optimizations, navigation, content modules, personalization rules.
|
||||
4. **Channel Alignment** – asset requirements, copy variations, QA checklists.
|
||||
5. **Measurement Loop** – KPI dashboards, readout cadence, learning archive.
|
||||
|
||||
## Templates
|
||||
- Promo calendar spreadsheet with dependencies + owner columns.
|
||||
- Merchandising layout guide (homepage, PLP, PDP modules).
|
||||
- QA + launch checklist across CMS, analytics, and marketing tools.
|
||||
|
||||
## Tips
|
||||
- Always link offers to inventory + margin guardrails to avoid over-discounting.
|
||||
- Coordinate creative refreshes with experiment timelines to isolate impact.
|
||||
- Pair with `plan-merchandising-campaign` for automation and tracking.
|
||||
|
||||
---
|
||||
31
skills/retention-ltv-playbook/SKILL.md
Normal file
31
skills/retention-ltv-playbook/SKILL.md
Normal file
@@ -0,0 +1,31 @@
|
||||
---
|
||||
name: retention-ltv-playbook
|
||||
description: Lifecycle frameworks for driving repeat purchase, loyalty, and subscription
|
||||
value.
|
||||
---
|
||||
|
||||
# Retention & LTV Playbook Skill
|
||||
|
||||
## When to Use
|
||||
- Designing lifecycle journeys (onboarding, loyalty, win-back, VIP).
|
||||
- Benchmarking repeat purchase and churn signals by cohort.
|
||||
- Equipping lifecycle teams with proven offers, creative angles, and cadences.
|
||||
|
||||
## Framework
|
||||
1. **Lifecycle Matrix** – cohort segmentation (new, active, lapsing, churned, VIP, subscription) with KPIs.
|
||||
2. **Offer Library** – incentives mapped to cohort + margin guardrails.
|
||||
3. **Channel Cadence** – recommended mixes (email, SMS, push, communities, direct mail).
|
||||
4. **Measurement Stack** – dashboards for repeat rate, LTV, churn, loyalty engagement, coupon reliance.
|
||||
5. **Testing Roadmap** – prioritized experiments per lifecycle cohort.
|
||||
|
||||
## Templates
|
||||
- Journey storyboard (touchpoint, trigger, creative brief, offer, KPI).
|
||||
- Loyalty program tracker (points, tiers, redemption metrics).
|
||||
- Experiment log for retention tests with hypotheses + guardrails.
|
||||
|
||||
## Tips
|
||||
- Align offers with merchandising calendar to prevent message fatigue.
|
||||
- Incorporate zero/first-party data capture prompts early in the lifecycle.
|
||||
- Pair with `launch-retention-program` for automated plan creation.
|
||||
|
||||
---
|
||||
31
skills/site-performance-watch/SKILL.md
Normal file
31
skills/site-performance-watch/SKILL.md
Normal file
@@ -0,0 +1,31 @@
|
||||
---
|
||||
name: site-performance-watch
|
||||
description: Monitoring and alerting framework for ecommerce site speed, errors, and
|
||||
uptime.
|
||||
---
|
||||
|
||||
# Site Performance Watch Skill
|
||||
|
||||
## When to Use
|
||||
- Setting up proactive monitoring during campaigns or launches.
|
||||
- Investigating conversion drops tied to latency or availability issues.
|
||||
- Communicating performance incidents to merchandising and engineering teams.
|
||||
|
||||
## Framework
|
||||
1. **KPI Stack** – FCP, LCP, CLS, TTFB, checkout API latency, error rates, uptime.
|
||||
2. **Segmentation** – device, geography, browser, promotion, traffic source.
|
||||
3. **Alerting Rules** – thresholds, aggregation windows, escalation paths, war-room triggers.
|
||||
4. **Diagnostics** – logging, tracing, screenshot/session replay hooks.
|
||||
5. **Comms Kit** – stakeholder updates, status pages, rollback plans.
|
||||
|
||||
## Templates
|
||||
- Performance scorecard with spark lines + thresholds.
|
||||
- Incident log template with root cause, mitigation, and follow-up tasks.
|
||||
- Escalation matrix covering engineering, DevOps, merchandising, and CX leads.
|
||||
|
||||
## Tips
|
||||
- Pair synthetic monitoring with RUM data to catch both systemic and localized issues.
|
||||
- Freeze experiment/merch changes when performance breaches critical thresholds.
|
||||
- Use alongside `diagnose-conversion-drop` to correlate experience and performance data.
|
||||
|
||||
---
|
||||
Reference in New Issue
Block a user