FLOW Framework — Find · Leverage · Optimize · Win
Framework and prompts © Daniel Agrici, CC BY 4.0 — github.com/AgriciDaniel/flow
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.
Commands
| 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 |
Report vendor state and verify the lockfile — automatic sync is not implemented |
Orchestration Logic
On /seo flow (no sub-command)
- Read
references/flow-framework.md
- Show the FLOW stage overview with a one-line description of each stage
- Ask: which stage matches the user's current situation?
On /seo flow find [url|topic]
- Read all files in
references/prompts/find/
- Apply each prompt to the URL or topic
- Cross-reference: "For deeper SERP clustering, see
/seo cluster <seed-keyword>"
On /seo flow leverage [url]
- Read the file in
references/prompts/leverage/
- Apply to the URL's current backlink context
- Cross-reference: "For raw backlink data, see
/seo backlinks <url>"
On /seo flow optimize [url]
- Read all file names in
references/prompts/optimize/
- Read prior analysis context (URL, industry vertical, any prior skill output in conversation)
- Select 2-3 most relevant prompts; load only those files
- Apply selected prompts; note the others are accessible via
/seo flow prompts
- Cross-reference: "For full content quality analysis, see
/seo content <url> and /seo geo <url>"
On /seo flow win [url]
- Read all files in
references/prompts/win/
- Apply each prompt to the URL's conversion and BOFU context
- Cross-reference: "For SXO persona scoring, see
/seo sxo <url>"
On /seo flow local [url]
- Read all files in
references/prompts/local/
- Apply to the URL's local SEO context
- Cross-reference: "For full local SEO analysis, see
/seo local <url> and /seo maps [command]"
On /seo flow prompts
- Read
references/prompts/README.md
- Display the full index: all 41 prompts with stage, name, trigger conditions
On /seo flow sync
- Tell the user automatic sync is not implemented — no sync script ships
with Clade. Do not improvise one; that would pull third-party content into
their tree unreviewed.
- The prompts under
references/prompts/ are vendored at the state pinned by
references/flow-prompts.lock. Verify and show the result:
From the skills root (~/.claude/ in an install, configs/ in the repo): sha256sum -c --quiet skills/seo-flow/references/flow-prompts.lock — the manifest's paths are rooted there, not at references/.
- To update, point at github.com/AgriciDaniel/flow to review and re-vendor
deliberately.
- Show attribution notice.
Context Matching (Optimize stage)
The optimize stage has 21 prompts. Dumping all 21 is noise. Select by priority:
- Industry vertical (SaaS → on-page + technical; local → citations + GBP; publisher → E-E-A-T + freshness)
- Prior skill output (seo-technical flagged crawl issues → technical optimize prompts; seo-content flagged E-E-A-T gaps → content optimize prompts)
- URL signals (product pages → conversion; blog → freshness + authority)
Always surface exactly 2-3 prompts. State which prompts you chose and why.
Reference Files
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 local
Attribution
Every /seo flow activation (any sub-command) outputs before analysis:
Framework and prompts © Daniel Agrici, CC BY 4.0 — github.com/AgriciDaniel/flow
Do not omit or modify the attribution.
Error Handling
| Scenario |
Action |
references/flow-framework.md missing |
The vendored reference is gone from the install. Reinstall Clade (./install.sh); do not point at a sync that does not exist. |
| Prompt file missing |
Same: the vendored copy is incomplete. Reinstall, then re-check sha256sum -c --quiet skills/seo-flow/references/flow-prompts.lock from the skills root. |
sha256sum -c reports a mismatch |
A vendored prompt was edited locally. Name the files listed; do not overwrite without asking — the edit may be intentional. |
| User asks to auto-sync from upstream |
Not implemented, and deliberately so. Measured 2026-08-17: upstream has 8 commits total, all from April 2026, none touching a prompt file — the corpus has been frozen since publication, so a fetch mechanism would track content that never changes. Offer to show the upstream diff instead. |
1---2name: seo-flow3description: 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.4license: MIT5---67# FLOW Framework — Find · Leverage · Optimize · Win89> Framework and prompts © Daniel Agrici, CC BY 4.0 — github.com/AgriciDaniel/flow1011FLOW is an evidence-led SEO operating model built for the AI-search era. Claude SEO12integrates the FLOW prompt library (41 prompts across 5 stages) so every analysis can13be driven by structured, evidence-backed AI prompts rather than improvised queries.1415**Runtime context:** Load `references/flow-framework.md` on every `/seo flow` activation.16Load prompt files on demand — only for the stage the user requests.1718---1920## Commands2122| Command | What it does |23|---------|-------------|24| `/seo flow` | Show FLOW overview + stage menu |25| `/seo flow find [url\|topic]` | Find-stage: keyword research, gap analysis, SERP intent mapping (5 prompts) |26| `/seo flow leverage [url]` | Leverage-stage: backlink strategy, off-site authority (1 prompt) |27| `/seo flow optimize [url]` | Optimize-stage: select 2-3 most relevant of 21 prompts based on context |28| `/seo flow win [url]` | Win-stage: BOFU, conversion rate, dual-surface scorecard (3 prompts) |29| `/seo flow local [url]` | Local-stage: GBP optimization, meta, title tags, local audits (11 prompts) |30| `/seo flow prompts` | Full index of all 41 prompts — stage, name, trigger conditions |31| `/seo flow sync` | Report vendor state and verify the lockfile — automatic sync is not implemented |3233---3435## Orchestration Logic3637### On `/seo flow` (no sub-command)381. Read `references/flow-framework.md`392. Show the FLOW stage overview with a one-line description of each stage403. Ask: which stage matches the user's current situation?4142### On `/seo flow find [url|topic]`431. Read all files in `references/prompts/find/`442. Apply each prompt to the URL or topic453. Cross-reference: "For deeper SERP clustering, see `/seo cluster <seed-keyword>`"4647### On `/seo flow leverage [url]`481. Read the file in `references/prompts/leverage/`492. Apply to the URL's current backlink context503. Cross-reference: "For raw backlink data, see `/seo backlinks <url>`"5152### On `/seo flow optimize [url]`531. Read all file names in `references/prompts/optimize/`542. Read prior analysis context (URL, industry vertical, any prior skill output in conversation)553. Select 2-3 most relevant prompts; load only those files564. Apply selected prompts; note the others are accessible via `/seo flow prompts`575. Cross-reference: "For full content quality analysis, see `/seo content <url>` and `/seo geo <url>`"5859### On `/seo flow win [url]`601. Read all files in `references/prompts/win/`612. Apply each prompt to the URL's conversion and BOFU context623. Cross-reference: "For SXO persona scoring, see `/seo sxo <url>`"6364### On `/seo flow local [url]`651. Read all files in `references/prompts/local/`662. Apply to the URL's local SEO context673. Cross-reference: "For full local SEO analysis, see `/seo local <url>` and `/seo maps [command]`"6869### On `/seo flow prompts`701. Read `references/prompts/README.md`712. Display the full index: all 41 prompts with stage, name, trigger conditions7273### On `/seo flow sync`741. Tell the user automatic sync is **not implemented** — no sync script ships75 with Clade. Do not improvise one; that would pull third-party content into76 their tree unreviewed.772. The prompts under `references/prompts/` are vendored at the state pinned by78 `references/flow-prompts.lock`. Verify and show the result:79 From the skills root (`~/.claude/` in an install, `configs/` in the repo): `sha256sum -c --quiet skills/seo-flow/references/flow-prompts.lock` — the manifest's paths are rooted there, not at `references/`.803. To update, point at github.com/AgriciDaniel/flow to review and re-vendor81 deliberately.824. Show attribution notice.8384---8586## Context Matching (Optimize stage)8788The optimize stage has 21 prompts. Dumping all 21 is noise. Select by priority:89901. **Industry vertical** (SaaS → on-page + technical; local → citations + GBP; publisher → E-E-A-T + freshness)912. **Prior skill output** (seo-technical flagged crawl issues → technical optimize prompts; seo-content flagged E-E-A-T gaps → content optimize prompts)923. **URL signals** (product pages → conversion; blog → freshness + authority)9394Always surface exactly 2-3 prompts. State which prompts you chose and why.9596---9798## Reference Files99100Load on-demand — do NOT load all at startup:101- `references/flow-framework.md` — FLOW operating model (load on every `/seo flow` activation)102- `references/bibliography.md` — Evidence sources; load when citing studies or statistics103- `references/prompts/README.md` — Prompt index; load for `/seo flow prompts`104- `references/prompts/find/` — 5 prompts; load for `/seo flow find`105- `references/prompts/leverage/` — 1 prompt; load for `/seo flow leverage`106- `references/prompts/optimize/` — 21 prompts; load selectively for `/seo flow optimize`107- `references/prompts/win/` — 3 prompts; load for `/seo flow win`108- `references/prompts/local/` — 11 prompts; load for `/seo flow local`109110---111112## Attribution113114Every `/seo flow` activation (any sub-command) outputs before analysis:115116```117Framework and prompts © Daniel Agrici, CC BY 4.0 — github.com/AgriciDaniel/flow118```119120Do not omit or modify the attribution.121122---123124## Error Handling125126| Scenario | Action |127|----------|--------|128| `references/flow-framework.md` missing | The vendored reference is gone from the install. Reinstall Clade (`./install.sh`); do not point at a sync that does not exist. |129| Prompt file missing | Same: the vendored copy is incomplete. Reinstall, then re-check `sha256sum -c --quiet skills/seo-flow/references/flow-prompts.lock` from the skills root. |130| `sha256sum -c` reports a mismatch | A vendored prompt was edited locally. Name the files listed; do not overwrite without asking — the edit may be intentional. |131| User asks to auto-sync from upstream | Not implemented, and deliberately so. Measured 2026-08-17: upstream has 8 commits total, all from April 2026, none touching a prompt file — the corpus has been frozen since publication, so a fetch mechanism would track content that never changes. Offer to show the upstream diff instead. |
shenxingy