Review English LP copy for messaging, naturalness, and SEO using a 3-agent review team. Use when reviewing landing page content. Triggers on "LP review", "LPレビュー", "landing page review", "LP copy", "コピーレビュー".
Review English-only landing page copy from messaging, naturalness, and SEO perspectives using a coordinated review team.
English-authored copy only. This skill reviews LP text written in English. It is NOT for reviewing translations from Japanese.
At workflow start, MUST create tasks for each phase:
TaskCreate: "Phase 0: Route"
TaskCreate: "Phase 1: Discover Target Files"
TaskCreate: "Phase 2: Build Shared Context"
TaskCreate: "Phase 3: Form Review Team & Run Reviews"
TaskCreate: "Phase 4: Cross-Review Discussion"
TaskCreate: "Phase 5: Synthesize Results"
TaskCreate: "Phase 6: Apply Fixes"
Update status as you progress: in_progress when starting, completed when done.
Verify the target is LP files:
.tsx files (LP/Docusaurus pages) and docusaurus.config.*/aso-review instead." and STOP.Glob("**/*.tsx") -- LP and Docusaurus page componentsGlob("docusaurus.config.*") -- SEO headTags and site metadataAssemble a context package for the review team:
/labee-llc-guide for tone and valuesThis context package is passed to each agent in Phase 3.
MUST call TeamCreate to create the review team. MUST spawn ALL 3 agents in ONE SendMessage block -- do NOT launch sequentially.
TeamCreate("lp-review-team")
Then send the shared context to all 3 agents in parallel:
| Agent Name | subagent_type | Role |
|---|---|---|
| messaging-reviewer | labee-pr-sns-ruka | LEAD -- Persuasion flow, audience resonance, CTA clarity, English-native copy quality |
| naturalness-reviewer | general-purpose | English AI pattern detection, "translated from Japanese" detection |
| seo-reviewer | labee-marketing-seo | Web SEO keyword alignment, meta tags, heading structure |
Each agent receives:
references/_checklist-lp.md relevant to their roleAgent instructions:
messaging-reviewer (LEAD):
naturalness-reviewer:
seo-reviewer:
MUST use SendMessage to relay findings between agents. Do NOT skip this phase.
The messaging-reviewer (LEAD) makes final call on conflicts.
## LP Review Report
### Findings
- [item]: [issue] -> [suggested fix]
### Conflicts Resolved
- [conflict]: [resolution by lead reviewer]
Only after user approval:
pnpm run build to verify no build errorsBad:
A Comprehensive Task Management Solution Designed to Revolutionize Your Workflow
Good:
Get more done. Stress less.
Why: The bad version uses AI vocabulary ("comprehensive", "revolutionize"), inflated phrasing, and says nothing specific. The good version is direct and benefit-focused.
Bad:
Our task management functionality enables users to efficiently organize and prioritize their daily activities.
Good:
Drag tasks around. Done ones disappear. That's it.
Why: The bad version is abstract and formal ("functionality enables users to efficiently"). The good version shows the actual experience.
Bad:
Please feel free to try our service
Good:
Start free -- no credit card needed
Why: The bad version has Japanese politeness norms ("please feel free") that sound unnatural in English LP copy. The good version is direct with a trust signal.
Bad:
Can manage tasks easily and check progress at a glance
Good:
You manage tasks and track progress -- all in one view
Why: The bad version omits the subject (natural in Japanese, incomplete in English). The good version adds "You" and flows naturally.
Bad:
Our cutting-edge platform serves as a comprehensive solution that seamlessly integrates with your existing workflow, enabling teams to leverage powerful collaboration tools.
Good:
It connects to Slack, GitHub, and Jira. Your team sees everything in one place.
Why: The bad version stacks AI vocabulary ("cutting-edge", "serves as", "comprehensive", "seamlessly", "leverage"). The good version states concrete facts.
Bad:
Multi-language support function with automatic translation capability
Good:
Write once, read in any language. Auto-translated in 12 languages.
Why: The bad version leads with the feature (Japanese product copy pattern). The good version leads with the benefit and adds a specific number.
/aso-review instead| File | Load When |
|---|---|
| references/_checklist-lp.md | Always (auto-loaded) |