Flow alignment in claude blog skill
This reference explains how claude-blog adopts the FLOW framework.
by AgriciDaniel·MIT license·★ 2,219 Stars on the repo·GitHub ↗
Use now
Files of Flow alignment in claude blog
AgriciDaniel/
flow-alignment.md
Show the full text66 lines
FLOW Alignment in claude-blog
This reference explains how claude-blog adopts the FLOW framework. Load it on demand when a user asks about FLOW, evidence standards, surface coverage, or how the blog skills route to FLOW stages.
1. What FLOW is and why claude-blog adopted it
FLOW is an evidence-led 2026-search operating model published at github.com/AgriciDaniel/flow (CC BY 4.0 prompt content, MIT code), authored by Daniel Agrici. It treats modern discovery as a multi-surface system rather than a single SERP, and it enforces a strict provenance discipline on every public claim. claude-blog v1.7.0 integrates FLOW as the blog-flow sub-skill (which exposes the upstream stages and prompts) plus this alignment doc, which informs how every other blog skill in the suite plans, writes, optimizes, and audits content. The intent is that FLOW provides the principles and prompts; claude-blog provides the production tooling that applies them at scale.
2. The FLOW evidence triple (the rule blog-write enforces)
Every public statistic in a claude-blog post must satisfy three components.
- Year anchor in prose. Write "In 2026," or "As of Q1 2026," BEFORE the statistic, not buried in a parenthetical. Example: "In 2026, Ahrefs found a 58% lower CTR for position-one results when an AI Overview was present." Not: "Position-one CTR dropped 58% (Ahrefs, 2026)."
- Inline citation. Publisher plus title (or document name) inline with the claim. Example: "Ahrefs, AI Overviews CTR update, December 2025."
- URL with retrieval date. Full URL plus
retrieved YYYY-MM-DDin compact retrieval notes, footnotes, or a bibliography at the end of the post. This is provenance discipline; it lets future readers and AI crawlers verify the source still says what was claimed.
Public claims must use verified sources OR stay qualitative. Unverifiable stats get dropped, contradicted stats get replaced with a verified alternative. This is the FLOW quality bar adopted verbatim.
3. The FLOW 5-surface model
In 2026 a query reaches a buyer through 5 parallel surfaces, often without a site visit. Coverage on each surface is planned independently.
| Surface | What it is | Where claude-blog handles it |
|---|---|---|
| 1. Owned site | Direct organic ranking on the publisher's domain | blog-write, blog-rewrite (on-page), blog-seo-check |
| 2. SERP + AI Overviews | Google SERP including AIO panels | blog-geo, blog-schema, blog-seo-check |
| 3. AI assistant citations | ChatGPT, Perplexity, Claude, Gemini, Copilot, You.com | blog-geo (citation readiness), blog-flow optimize (visibility prompts) |
| 4. Local pack | Map listings, Google Business Profile | Out of scope for blog content. Use claude-seo (/seo local, /seo maps) for local SEO. |
| 5. Communities + video | Reddit, YouTube, LinkedIn, Quora, niche forums | blog-repurpose (multi-platform), skills/blog/references/distribution-playbook.md, blog-cluster (interlinked content) |
claude-blog operationalizes surfaces 1, 2, 3, and 5 directly. Surface 4 is delegated to claude-seo. When a blog post targets a query that also surfaces in a community (Reddit thread, YouTube comment), the writer should consider dual-surface thinking: optimize the post for extraction AND consider whether the same answer should also live in the community where the query is asked.
4. FLOW stages mapped to existing claude-blog skills
| FLOW stage | claude-blog skills that consume this | When to invoke /blog flow <stage> directly |
|---|---|---|
| Find (5 prompts) | blog-brief, blog-outline, blog-strategy, blog-cluster (planning) |
When you want raw FLOW prompts for keyword discovery, audience avatar, content prioritization without invoking a full brief/outline workflow |
| Optimize (21 prompts) | blog-rewrite, blog-seo-check, blog-geo, blog-schema, blog-audit, blog-factcheck |
When you want a specific optimization prompt (CTR audit, AI detector test, ChatGPT visibility, schema, PAA rewording, technical audit) for one-shot use |
| Win (3 prompts) | blog-audit, blog-repurpose, blog-analyze |
When you want the BOFU page brief, conversion audit, or dual-surface scorecard for a specific URL |
| Prompts | (umbrella index) | When browsing all 30 blog-applicable prompts, including the 1 leverage-stage prompt that has no top-level command |
| Sync | (no skill consumes this) | When you want to refresh the synced FLOW reference files from the upstream repo |
The Leverage stage (off-site authority, 1 prompt) and Local stage (11 GBP/citation prompts) are intentionally not exposed as top-level claude-blog commands. Leverage is reachable through /blog flow prompts. Local is delegated to claude-seo.
5. What claude-blog adds beyond FLOW
- Visual media pipeline: AI image generation via Gemini (
blog-image), inline SVG charts (blog-chart), Pixabay/Unsplash/Pexels integration. FLOW does not prescribe asset generation. - Writing-persona system (
blog-persona) for voice/tone profiles. FLOW is voice-agnostic. - 5-category 100-point scoring (
blog-analyze). FLOW provides quality bars but no numeric scoring. - Topic-cluster execution engine (
blog-cluster). FLOW prescribes content planning; claude-blog also executes clusters end-to-end with auto-interlinks. - Multilingual publishing (
blog-multilingual,blog-translate,blog-localize,blog-locale-audit). FLOW is single-locale by default. - Audio narration (
blog-audio). Not in FLOW scope. - Google API integration (
blog-google: PSI, CrUX, GSC, GA4, NLP, YouTube, Keywords). FLOW references measurement; claude-blog provides API tooling. - Source-grounded research via NotebookLM (
blog-notebooklm). Adjacent to FLOW's evidence discipline; provides the research side. - CMS taxonomy sync (
blog-taxonomy). Operational layer FLOW does not address.
These additions implement the FLOW principles in production tooling; they do not modify the principles.
6. When to consult this doc vs. the synced FLOW source
- This doc (
flow-alignment.md): the orchestrator and any sub-skill loads this when the user asks "what does claude-blog do for AI citations / evidence / surfaces", to give a claude-blog-specific answer with skill names and routing. - The synced FLOW source (
skills/blog-flow/references/flow-framework.mdplus 30 prompts): load when applying a specific FLOW prompt or quoting the framework verbatim. CC BY 4.0 attribution is required for any quote. - The bibliography (
skills/blog-flow/references/bibliography.md): load when verifying sources for a statistic.
Last updated 2026-07-08 for claude-blog v1.10.0.
| 1 | # FLOW Alignment in claude-blog |
| 2 | |
| 3 | This reference explains how claude-blog adopts the FLOW framework. Load it on demand when a user asks about FLOW, evidence standards, surface coverage, or how the blog skills route to FLOW stages. |
| 4 | |
| 5 | ## 1. What FLOW is and why claude-blog adopted it |
| 6 | |
| 7 | FLOW is an evidence-led 2026-search operating model published at `github.com/AgriciDaniel/flow` (CC BY 4.0 prompt content, MIT code), authored by Daniel Agrici. It treats modern discovery as a multi-surface system rather than a single SERP, and it enforces a strict provenance discipline on every public claim. claude-blog v1.7.0 integrates FLOW as the `blog-flow` sub-skill (which exposes the upstream stages and prompts) plus this alignment doc, which informs how every other blog skill in the suite plans, writes, optimizes, and audits content. The intent is that FLOW provides the principles and prompts; claude-blog provides the production tooling that applies them at scale. |
| 8 | |
| 9 | ## 2. The FLOW evidence triple (the rule blog-write enforces) |
| 10 | |
| 11 | Every public statistic in a claude-blog post must satisfy three components. |
| 12 | |
| 13 | **Year anchor in prose.** Write "In 2026," or "As of Q1 2026," BEFORE the statistic, not buried in a parenthetical. Example: "In 2026, Ahrefs found a 58% lower CTR for position-one results when an AI Overview was present." Not: "Position-one CTR dropped 58% (Ahrefs, 2026)." |
| 14 | **Inline citation.** Publisher plus title (or document name) inline with the claim. Example: "Ahrefs, AI Overviews CTR update, December 2025." |
| 15 | **URL with retrieval date.** Full URL plus `retrieved YYYY-MM-DD` in compact retrieval notes, footnotes, or a bibliography at the end of the post. This is provenance discipline; it lets future readers and AI crawlers verify the source still says what was claimed. |
| 16 | |
| 17 | Public claims must use verified sources OR stay qualitative. Unverifiable stats get dropped, contradicted stats get replaced with a verified alternative. This is the FLOW quality bar adopted verbatim. |
| 18 | |
| 19 | ## 3. The FLOW 5-surface model |
| 20 | |
| 21 | In 2026 a query reaches a buyer through 5 parallel surfaces, often without a site visit. Coverage on each surface is planned independently. |
| 22 | |
| 23 | | Surface | What it is | Where claude-blog handles it | |
| 24 | |---|---|---| |
| 25 | | 1. Owned site | Direct organic ranking on the publisher's domain | `blog-write`, `blog-rewrite` (on-page), `blog-seo-check` | |
| 26 | | 2. SERP + AI Overviews | Google SERP including AIO panels | `blog-geo`, `blog-schema`, `blog-seo-check` | |
| 27 | | 3. AI assistant citations | ChatGPT, Perplexity, Claude, Gemini, Copilot, You.com | `blog-geo` (citation readiness), `blog-flow optimize` (visibility prompts) | |
| 28 | | 4. Local pack | Map listings, Google Business Profile | Out of scope for blog content. Use `claude-seo` (`/seo local`, `/seo maps`) for local SEO. | |
| 29 | | 5. Communities + video | Reddit, YouTube, LinkedIn, Quora, niche forums | `blog-repurpose` (multi-platform), `skills/blog/references/distribution-playbook.md`, `blog-cluster` (interlinked content) | |
| 30 | |
| 31 | claude-blog operationalizes surfaces 1, 2, 3, and 5 directly. Surface 4 is delegated to claude-seo. When a blog post targets a query that also surfaces in a community (Reddit thread, YouTube comment), the writer should consider dual-surface thinking: optimize the post for extraction AND consider whether the same answer should also live in the community where the query is asked. |
| 32 | |
| 33 | ## 4. FLOW stages mapped to existing claude-blog skills |
| 34 | |
| 35 | | FLOW stage | claude-blog skills that consume this | When to invoke `/blog flow <stage>` directly | |
| 36 | |---|---|---| |
| 37 | | Find (5 prompts) | `blog-brief`, `blog-outline`, `blog-strategy`, `blog-cluster` (planning) | When you want raw FLOW prompts for keyword discovery, audience avatar, content prioritization without invoking a full brief/outline workflow | |
| 38 | | Optimize (21 prompts) | `blog-rewrite`, `blog-seo-check`, `blog-geo`, `blog-schema`, `blog-audit`, `blog-factcheck` | When you want a specific optimization prompt (CTR audit, AI detector test, ChatGPT visibility, schema, PAA rewording, technical audit) for one-shot use | |
| 39 | | Win (3 prompts) | `blog-audit`, `blog-repurpose`, `blog-analyze` | When you want the BOFU page brief, conversion audit, or dual-surface scorecard for a specific URL | |
| 40 | | Prompts | (umbrella index) | When browsing all 30 blog-applicable prompts, including the 1 leverage-stage prompt that has no top-level command | |
| 41 | | Sync | (no skill consumes this) | When you want to refresh the synced FLOW reference files from the upstream repo | |
| 42 | |
| 43 | The Leverage stage (off-site authority, 1 prompt) and Local stage (11 GBP/citation prompts) are intentionally not exposed as top-level claude-blog commands. Leverage is reachable through `/blog flow prompts`. Local is delegated to claude-seo. |
| 44 | |
| 45 | ## 5. What claude-blog adds beyond FLOW |
| 46 | |
| 47 | Visual media pipeline: AI image generation via Gemini (`blog-image`), inline SVG charts (`blog-chart`), Pixabay/Unsplash/Pexels integration. FLOW does not prescribe asset generation. |
| 48 | Writing-persona system (`blog-persona`) for voice/tone profiles. FLOW is voice-agnostic. |
| 49 | 5-category 100-point scoring (`blog-analyze`). FLOW provides quality bars but no numeric scoring. |
| 50 | Topic-cluster execution engine (`blog-cluster`). FLOW prescribes content planning; claude-blog also executes clusters end-to-end with auto-interlinks. |
| 51 | Multilingual publishing (`blog-multilingual`, `blog-translate`, `blog-localize`, `blog-locale-audit`). FLOW is single-locale by default. |
| 52 | Audio narration (`blog-audio`). Not in FLOW scope. |
| 53 | Google API integration (`blog-google`: PSI, CrUX, GSC, GA4, NLP, YouTube, Keywords). FLOW references measurement; claude-blog provides API tooling. |
| 54 | Source-grounded research via NotebookLM (`blog-notebooklm`). Adjacent to FLOW's evidence discipline; provides the research side. |
| 55 | CMS taxonomy sync (`blog-taxonomy`). Operational layer FLOW does not address. |
| 56 | |
| 57 | These additions implement the FLOW principles in production tooling; they do not modify the principles. |
| 58 | |
| 59 | ## 6. When to consult this doc vs. the synced FLOW source |
| 60 | |
| 61 | This doc (`flow-alignment.md`): the orchestrator and any sub-skill loads this when the user asks "what does claude-blog do for AI citations / evidence / surfaces", to give a claude-blog-specific answer with skill names and routing. |
| 62 | The synced FLOW source (`skills/blog-flow/references/flow-framework.md` plus 30 prompts): load when applying a specific FLOW prompt or quoting the framework verbatim. CC BY 4.0 attribution is required for any quote. |
| 63 | The bibliography (`skills/blog-flow/references/bibliography.md`): load when verifying sources for a statistic. |
| 64 | |
| 65 | Last updated 2026-07-08 for claude-blog v1.10.0. |
| 66 |
Discussion
Alternatives
⚙️ Phase 2 Playbook — Foundation & Scaffolding> Duration: 3-5 days | Agents: 6 | Gate Keepers: DevOps Automator + Evidence Collector🌐 NEXUS — Network of EXperts, Unified in Strategy> NEXUS transforms The Agency's independent AI specialists into a synchronized intelligence network. This is not a prompt collection — it…
Ansoff matrixGenerate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.
Career changer translatorTranslate skills from one industry to another, identify transferable skillsBrowse more free Claude skills or everything in Product.