Design rigorous A/B tests with hypotheses, variants, metrics, and sample size calculations.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
FLOW framework integration — evidence-led SEO using the Find → Leverage → Optimize → Win loop. Surfaces stage-specific AI prompts from the FLOW knowledge base (41 prompts, CC BY 4.0). Use when user says "FLOW", "FLOW framework", "seo flow", "evidence-led SEO", "find leverage optimize win", or wants stage-specific SEO prompts.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
FLOW is an evidence-led SEO operating model built for the AI-search era. Claude SEO integrates the FLOW prompt library (41 prompts across 5 stages) so every analysis can be driven by structured, evidence-backed AI prompts rather than improvised queries.
Runtime context: Load references/flow-framework.md on every /seo flow activation.
Load prompt files on demand — only for the stage the user requests.
| Command | What it does |
|---|---|
/seo flow | Show FLOW overview + stage menu |
/seo flow find [url|topic] | Find-stage: keyword research, gap analysis, SERP intent mapping (5 prompts) |
/seo flow leverage [url] | Leverage-stage: backlink strategy, off-site authority (1 prompt) |
/seo flow optimize [url] | Optimize-stage: select 2-3 most relevant of 21 prompts based on context |
/seo flow win [url] | Win-stage: BOFU, conversion rate, dual-surface scorecard (3 prompts) |
/seo flow local [url] | Local-stage: GBP optimization, meta, title tags, local audits (11 prompts) |
/seo flow prompts | Full index of all 41 prompts — stage, name, trigger conditions |
/seo flow sync | Pull latest prompt files from the FLOW prompt repository |
/seo flow (no sub-command)references/flow-framework.md/seo flow find [url|topic]references/prompts/find//seo cluster <seed-keyword>"/seo flow leverage [url]references/prompts/leverage//seo backlinks <url>"/seo flow optimize [url]references/prompts/optimize//seo flow prompts/seo content <url> and /seo geo <url>"/seo flow win [url]references/prompts/win//seo sxo <url>"/seo flow local [url]references/prompts/local//seo local <url> and /seo maps [command]"/seo flow promptsreferences/prompts/README.md/seo flow syncpython scripts/sync_flow_seo.pyThe optimize stage has 21 prompts. Dumping all 21 is noise. Select by priority:
Always surface exactly 2-3 prompts. State which prompts you chose and why.
Load on-demand — do NOT load all at startup:
references/flow-framework.md — FLOW operating model (load on every /seo flow activation)references/bibliography.md — Evidence sources; load when citing studies or statisticsreferences/prompts/README.md — Prompt index; load for /seo flow promptsreferences/prompts/find/ — 5 prompts; load for /seo flow findreferences/prompts/leverage/ — 1 prompt; load for /seo flow leveragereferences/prompts/optimize/ — 21 prompts; load selectively for /seo flow optimizereferences/prompts/win/ — 3 prompts; load for /seo flow winreferences/prompts/local/ — 11 prompts; load for /seo flow localEvery /seo flow activation (any sub-command) outputs before analysis:
Do not omit or modify the attribution.
| Scenario | Action |
|---|---|
references/flow-framework.md missing | "FLOW reference files not synced. Run: /seo flow sync" |
| Prompt file missing | "Run /seo flow sync to pull the latest prompts from the FLOW repo." |
sync_flow_seo.py network error | Display the script's stderr. Check rate limits: gh api rate_limit. |
sync_flow_seo.py auth error | Run gh auth login then retry. |
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Design rigorous A/B tests with hypotheses, variants, metrics, and sample size calculations.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Format CVs for academic positions with publications, grants, and teaching
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Conduct a comprehensive accessibility audit against WCAG guidelines with severity ratings and remediation steps.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create accessibility testing plans covering assistive technologies and WCAG criteria.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform. Also use when the user mentions 'ad copy variations,' 'ad creative,' 'generate headlines,' 'RSA headlines,' 'bulk ad copy,' 'ad iterations,' 'creative testing,' 'ad performance optimization,' 'write me some ads,' 'Facebook ad copy,' 'Google ad headlines,' 'LinkedIn ad text,' or 'I need more ad variations.' Use this whenever someone needs to produce ad copy at scale or iterate on existing ads. For campaign strategy and targeting, see ads. For landing page copy, see copywriting.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.