codehava-agent-kit 1.0.1 → 2.0.0

package/templates/.agent/skills/seo-geo/SKILL.md

@@ -0,0 +1,254 @@
+---
+name: seo-geo
+description: "Optimize content for AI Overviews, ChatGPT, Perplexity, and other AI search systems. Use when improving GEO, AI citations, llms.txt readiness, crawler accessibility, and passage-level citability."
+risk: unknown
+source: "https://github.com/AgriciDaniel/claude-seo"
+date_added: "2026-03-21"
+user-invokable: true
+argument-hint: "[url]"
+allowed-tools:
+  - Read
+  - Grep
+  - Glob
+  - Bash
+  - WebFetch
+---
+
+# AI Search / GEO Optimization (February 2026)
+
+## When to Use
+
+- Use when improving visibility in AI Overviews, ChatGPT, Perplexity, or similar AI search systems.
+- Use when evaluating llms.txt readiness, AI crawler access, or citation-oriented content structure.
+- Use when the user asks about GEO, AI SEO, LLM visibility, or AI citations.
+
+## Key Statistics
+
+| Metric | Value | Source |
+|--------|-------|--------|
+| AI Overviews reach | 1.5 billion users/month across 200+ countries | Google |
+| AI Overviews query coverage | 50%+ of all queries | Industry data |
+| AI-referred sessions growth | 527% (Jan-May 2025) | SparkToro |
+| ChatGPT weekly active users | 900 million | OpenAI |
+| Perplexity monthly queries | 500+ million | Perplexity |
+
+## Critical Insight: Brand Mentions > Backlinks
+
+**Brand mentions correlate 3x more strongly with AI visibility than backlinks.**
+(Ahrefs December 2025 study of 75,000 brands)
+
+| Signal | Correlation with AI Citations |
+|--------|------------------------------|
+| YouTube mentions | ~0.737 (strongest) |
+| Reddit mentions | High |
+| Wikipedia presence | High |
+| LinkedIn presence | Moderate |
+| Domain Rating (backlinks) | ~0.266 (weak) |
+
+**Only 11% of domains** are cited by both ChatGPT and Google AI Overviews for the same query, so platform-specific optimization is essential.
+
+---
+
+## GEO Analysis Criteria (Updated)
+
+### 1. Citability Score (25%)
+
+**Optimal passage length: 134-167 words** for AI citation.
+
+**Strong signals:**
+- Clear, quotable sentences with specific facts/statistics
+- Self-contained answer blocks (can be extracted without context)
+- Direct answer in first 40-60 words of section
+- Claims attributed with specific sources
+- Definitions following "X is..." or "X refers to..." patterns
+- Unique data points not found elsewhere
+
+**Weak signals:**
+- Vague, general statements
+- Opinion without evidence
+- Buried conclusions
+- No specific data points
+
+### 2. Structural Readability (20%)
+
+**92% of AI Overview citations come from top-10 ranking pages**, but 47% come from pages ranking below position 5, demonstrating different selection logic.
+
+**Strong signals:**
+- Clean H1->H2->H3 heading hierarchy
+- Question-based headings (matches query patterns)
+- Short paragraphs (2-4 sentences)
+- Tables for comparative data
+- Ordered/unordered lists for step-by-step or multi-item content
+- FAQ sections with clear Q&A format
+
+**Weak signals:**
+- Wall of text with no structure
+- Inconsistent heading hierarchy
+- No lists or tables
+- Information buried in paragraphs
+
+### 3. Multi-Modal Content (15%)
+
+Content with multi-modal elements sees **156% higher selection rates**.
+
+**Check for:**
+- Text + relevant images
+- Video content (embedded or linked)
+- Infographics and charts
+- Interactive elements (calculators, tools)
+- Structured data supporting media
+
+### 4. Authority & Brand Signals (20%)
+
+**Strong signals:**
+- Author byline with credentials
+- Publication date and last-updated date
+- Citations to primary sources (studies, official docs, data)
+- Organization credentials and affiliations
+- Expert quotes with attribution
+- Entity presence in Wikipedia, Wikidata
+- Mentions on Reddit, YouTube, LinkedIn
+
+**Weak signals:**
+- Anonymous authorship
+- No dates
+- No sources cited
+- No brand presence across platforms
+
+### 5. Technical Accessibility (20%)
+
+**AI crawlers do NOT execute JavaScript.** Server-side rendering is critical.
+
+**Check for:**
+- Server-side rendering (SSR) vs client-only content
+- AI crawler access in robots.txt
+- llms.txt file presence and configuration
+- RSL 1.0 licensing terms
+
+---
+
+## AI Crawler Detection
+
+Check `robots.txt` for these AI crawlers:
+
+| Crawler | Owner | Purpose |
+|---------|-------|---------|
+| GPTBot | OpenAI | ChatGPT web search |
+| OAI-SearchBot | OpenAI | OpenAI search features |
+| ChatGPT-User | OpenAI | ChatGPT browsing |
+| ClaudeBot | Anthropic | Claude web features |
+| PerplexityBot | Perplexity | Perplexity AI search |
+| CCBot | Common Crawl | Training data (often blocked) |
+| anthropic-ai | Anthropic | Claude training |
+| Bytespider | ByteDance | TikTok/Douyin AI |
+| cohere-ai | Cohere | Cohere models |
+
+**Recommendation:** Allow GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot for AI search visibility. Block CCBot and training crawlers if desired.
+
+---
+
+## llms.txt Standard
+
+The emerging **llms.txt** standard provides AI crawlers with structured content guidance.
+
+**Location:** `/llms.txt` (root of domain)
+
+**Format:**
+```
+# Title of site
+> Brief description
+
+## Main sections
+- `Page title -> https://example.com/page`: Description
+- `Another page -> https://example.com/another-page`: Description
+
+## Optional: Key facts
+- Fact 1
+- Fact 2
+```
+
+**Check for:**
+- Presence of `/llms.txt`
+- Structured content guidance
+- Key page highlights
+- Contact/authority information
+
+---
+
+## RSL 1.0 (Really Simple Licensing)
+
+New standard (December 2025) for machine-readable AI licensing terms.
+
+**Backed by:** Reddit, Yahoo, Medium, Quora, Cloudflare, Akamai, Creative Commons
+
+**Check for:** RSL implementation and appropriate licensing terms.
+
+---
+
+## Platform-Specific Optimization
+
+| Platform | Key Citation Sources | Optimization Focus |
+|----------|---------------------|-------------------|
+| **Google AI Overviews** | Top-10 ranking pages (92%) | Traditional SEO + passage optimization |
+| **ChatGPT** | Wikipedia (47.9%), Reddit (11.3%) | Entity presence, authoritative sources |
+| **Perplexity** | Reddit (46.7%), Wikipedia | Community validation, discussions |
+| **Bing Copilot** | Bing index, authoritative sites | Bing SEO, IndexNow |
+
+---
+
+## Output
+
+Generate `GEO-ANALYSIS.md` with:
+
+1. **GEO Readiness Score: XX/100**
+2. **Platform breakdown** (Google AIO, ChatGPT, Perplexity scores)
+3. **AI Crawler Access Status** (which crawlers allowed/blocked)
+4. **llms.txt Status** (present, missing, recommendations)
+5. **Brand Mention Analysis** (presence on Wikipedia, Reddit, YouTube, LinkedIn)
+6. **Passage-Level Citability** (optimal 134-167 word blocks identified)
+7. **Server-Side Rendering Check** (JavaScript dependency analysis)
+8. **Top 5 Highest-Impact Changes**
+9. **Schema Recommendations** (for AI discoverability)
+10. **Content Reformatting Suggestions** (specific passages to rewrite)
+
+---
+
+## Quick Wins
+
+1. Add "What is [topic]?" definition in first 60 words
+2. Create 134-167 word self-contained answer blocks
+3. Add question-based H2/H3 headings
+4. Include specific statistics with sources
+5. Add publication/update dates
+6. Implement Person schema for authors
+7. Allow key AI crawlers in robots.txt
+
+## Medium Effort
+
+1. Create `/llms.txt` file
+2. Add author bio with credentials + Wikipedia/LinkedIn links
+3. Ensure server-side rendering for key content
+4. Build entity presence on Reddit, YouTube
+5. Add comparison tables with data
+6. Implement FAQ sections (structured, not schema for commercial sites)
+
+## High Impact
+
+1. Create original research/surveys (unique citability)
+2. Build Wikipedia presence for brand/key people
+3. Establish YouTube channel with content mentions
+4. Implement comprehensive entity linking (sameAs across platforms)
+5. Develop unique tools or calculators
+
+## DataForSEO Integration (Optional)
+
+If DataForSEO MCP tools are available, use `ai_optimization_chat_gpt_scraper` to check what ChatGPT web search returns for target queries (real GEO visibility check) and `ai_opt_llm_ment_search` with `ai_opt_llm_ment_top_domains` for LLM mention tracking across AI platforms.
+
+## Error Handling
+
+| Scenario | Action |
+|----------|--------|
+| URL unreachable (DNS failure, connection refused) | Report the error clearly. Do not guess site content. Suggest the user verify the URL and try again. |
+| AI crawlers blocked by robots.txt | Report exactly which crawlers are blocked and which are allowed. Provide specific robots.txt directives to add for enabling AI search visibility. |
+| No llms.txt found | Note the absence and provide a ready-to-use llms.txt template based on the site's content structure. |
+| No structured data detected | Report the gap and provide specific schema recommendations (Article, Organization, Person) for improving AI discoverability. |

package/templates/.agent/skills/seo-hreflang/SKILL.md

@@ -0,0 +1,209 @@
+---
+name: seo-hreflang
+description: >
+  Hreflang and international SEO audit, validation, and generation. Detects
+  common mistakes, validates language/region codes, and generates correct
+  hreflang implementations. Use when user says "hreflang", "i18n SEO",
+  "international SEO", "multi-language", "multi-region", or "language tags".
+risk: unknown
+source: "https://github.com/AgriciDaniel/claude-seo"
+date_added: "2026-03-21"
+user-invokable: true
+argument-hint: "[url]"
+allowed-tools:
+  - Read
+  - Grep
+  - Glob
+  - Bash
+  - WebFetch
+---
+
+# Hreflang & International SEO
+
+## When to Use
+
+- Use when validating or generating hreflang for multilingual or multiregional sites.
+- Use when the user mentions international SEO, language tags, x-default, or hreflang issues.
+- Use when auditing locale alternates across HTML, headers, or sitemap implementations.
+
+Validate existing hreflang implementations or generate correct hreflang tags
+for multi-language and multi-region sites. Supports HTML, HTTP header, and
+XML sitemap implementations.
+
+## Validation Checks
+
+### 1. Self-Referencing Tags
+- Every page must include an hreflang tag pointing to itself
+- The self-referencing URL must exactly match the page's canonical URL
+- Missing self-referencing tags cause Google to ignore the entire hreflang set
+
+### 2. Return Tags
+- If page A links to page B with hreflang, page B must link back to page A
+- Every hreflang relationship must be bidirectional (A→B and B→A)
+- Missing return tags invalidate the hreflang signal for both pages
+- Check all language versions reference each other (full mesh)
+
+### 3. x-default Tag
+- Required: designates the fallback page for unmatched languages/regions
+- Typically points to the language selector page or English version
+- Only one x-default per set of alternates
+- Must also have return tags from all other language versions
+
+### 4. Language Code Validation
+- Must use ISO 639-1 two-letter codes (e.g., `en`, `fr`, `de`, `ja`)
+- Common errors:
+  - `eng` instead of `en` (ISO 639-2, not valid for hreflang)
+  - `jp` instead of `ja` (incorrect code for Japanese)
+  - `zh` without region qualifier (ambiguous; use `zh-Hans` or `zh-Hant`)
+
+### 5. Region Code Validation
+- Optional region qualifier uses ISO 3166-1 Alpha-2 (e.g., `en-US`, `en-GB`, `pt-BR`)
+- Format: `language-REGION` (lowercase language, uppercase region)
+- Common errors:
+  - `en-uk` instead of `en-GB` (UK is not a valid ISO 3166-1 code)
+  - `es-LA` (Latin America is not a country; use specific countries)
+  - Region without language prefix
+
+### 6. Canonical URL Alignment
+- Hreflang tags must only appear on canonical URLs
+- If a page has `rel=canonical` pointing elsewhere, hreflang on that page is ignored
+- The canonical URL and hreflang URL must match exactly (including trailing slashes)
+- Non-canonical pages should not be in any hreflang set
+
+### 7. Protocol Consistency
+- All URLs in an hreflang set must use the same protocol (HTTPS or HTTP)
+- Mixed HTTP/HTTPS in hreflang sets causes validation failures
+- After HTTPS migration, update all hreflang tags to HTTPS
+
+### 8. Cross-Domain Support
+- Hreflang works across different domains (e.g., example.com and example.de)
+- Cross-domain hreflang requires return tags on both domains
+- Verify both domains are verified in Google Search Console
+- Sitemap-based implementation recommended for cross-domain setups
+
+## Common Mistakes
+
+| Issue | Severity | Fix |
+|-------|----------|-----|
+| Missing self-referencing tag | Critical | Add hreflang pointing to same page URL |
+| Missing return tags (A→B but no B→A) | Critical | Add matching return tags on all alternates |
+| Missing x-default | High | Add x-default pointing to fallback/selector page |
+| Invalid language code (e.g., `eng`) | High | Use ISO 639-1 two-letter codes |
+| Invalid region code (e.g., `en-uk`) | High | Use ISO 3166-1 Alpha-2 codes |
+| Hreflang on non-canonical URL | High | Move hreflang to canonical URL only |
+| HTTP/HTTPS mismatch in URLs | Medium | Standardize all URLs to HTTPS |
+| Trailing slash inconsistency | Medium | Match canonical URL format exactly |
+| Hreflang in both HTML and sitemap | Low | Choose one method (sitemap preferred for large sites) |
+| Language without region when needed | Low | Add region qualifier for geo-targeted content |
+
+## Implementation Methods
+
+### Method 1: HTML Link Tags
+Best for: Sites with <50 language/region variants per page.
+
+```html
+<link rel="alternate" hreflang="en-US" href="https://example.com/page" />
+<link rel="alternate" hreflang="en-GB" href="https://example.co.uk/page" />
+<link rel="alternate" hreflang="fr" href="https://example.com/fr/page" />
+<link rel="alternate" hreflang="x-default" href="https://example.com/page" />
+```
+
+Place in `<head>` section. Every page must include all alternates including itself.
+
+### Method 2: HTTP Headers
+Best for: Non-HTML files (PDFs, documents).
+
+```
+Link: <https://example.com/page>; rel="alternate"; hreflang="en-US",
+      <https://example.com/fr/page>; rel="alternate"; hreflang="fr",
+      <https://example.com/page>; rel="alternate"; hreflang="x-default"
+```
+
+Set via server configuration or CDN rules.
+
+### Method 3: XML Sitemap (Recommended for large sites)
+Best for: Sites with many language variants, cross-domain setups, or 50+ pages.
+
+See Hreflang Sitemap Generation section below.
+
+### Method Comparison
+| Method | Best For | Pros | Cons |
+|--------|----------|------|------|
+| HTML link tags | Small sites (<50 variants) | Easy to implement, visible in source | Bloats `<head>`, hard to maintain at scale |
+| HTTP headers | Non-HTML files | Works for PDFs, images | Complex server config, not visible in HTML |
+| XML sitemap | Large sites, cross-domain | Scalable, centralized management | Not visible on page, requires sitemap maintenance |
+
+## Hreflang Generation
+
+### Process
+1. **Detect languages**: Scan site for language indicators (URL path, subdomain, TLD, HTML lang attribute)
+2. **Map page equivalents**: Match corresponding pages across languages/regions
+3. **Validate language codes**: Verify all codes against ISO 639-1 and ISO 3166-1
+4. **Generate tags**: Create hreflang tags for each page including self-referencing
+5. **Verify return tags**: Confirm all relationships are bidirectional
+6. **Add x-default**: Set fallback for each page set
+7. **Output**: Generate implementation code (HTML, HTTP headers, or sitemap XML)
+
+## Hreflang Sitemap Generation
+
+### Sitemap with Hreflang
+```xml
+<?xml version="1.0" encoding="UTF-8"?>
+<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
+        xmlns:xhtml="http://www.w3.org/1999/xhtml">
+  <url>
+    <loc>https://example.com/page</loc>
+    <xhtml:link rel="alternate" hreflang="en-US" href="https://example.com/page" />
+    <xhtml:link rel="alternate" hreflang="fr" href="https://example.com/fr/page" />
+    <xhtml:link rel="alternate" hreflang="de" href="https://example.de/page" />
+    <xhtml:link rel="alternate" hreflang="x-default" href="https://example.com/page" />
+  </url>
+  <url>
+    <loc>https://example.com/fr/page</loc>
+    <xhtml:link rel="alternate" hreflang="en-US" href="https://example.com/page" />
+    <xhtml:link rel="alternate" hreflang="fr" href="https://example.com/fr/page" />
+    <xhtml:link rel="alternate" hreflang="de" href="https://example.de/page" />
+    <xhtml:link rel="alternate" hreflang="x-default" href="https://example.com/page" />
+  </url>
+</urlset>
+```
+
+Key rules:
+- Include the `xmlns:xhtml` namespace declaration
+- Every `<url>` entry must include ALL language alternates (including itself)
+- Each alternate must appear as a separate `<url>` entry with its own full set
+- Split at 50,000 URLs per sitemap file
+
+## Output
+
+### Hreflang Validation Report
+
+#### Summary
+- Total pages scanned: XX
+- Language variants detected: XX
+- Issues found: XX (Critical: X, High: X, Medium: X, Low: X)
+
+#### Validation Results
+| Language | URL | Self-Ref | Return Tags | x-default | Status |
+|----------|-----|----------|-------------|-----------|--------|
+| en-US | https://... | ✅ | ✅ | ✅ | ✅ |
+| fr | https://... | ❌ | ⚠️ | ✅ | ❌ |
+| de | https://... | ✅ | ❌ | ✅ | ❌ |
+
+### Generated Hreflang Tags
+- HTML `<link>` tags (if HTML method chosen)
+- HTTP header values (if header method chosen)
+- `hreflang-sitemap.xml` (if sitemap method chosen)
+
+### Recommendations
+- Missing implementations to add
+- Incorrect codes to fix
+- Method migration suggestions (e.g., HTML to sitemap for scale)
+
+## Error Handling
+
+| Scenario | Action |
+|----------|--------|
+| URL unreachable (DNS failure, connection refused) | Report the error clearly. Do not guess site structure. Suggest the user verify the URL and try again. |
+| No hreflang tags found | Report the absence. Check for other internationalization signals (subdirectories, subdomains, ccTLDs) and recommend the appropriate hreflang implementation method. |
+| Invalid language/region codes detected | List each invalid code with the correct replacement. Provide a corrected hreflang tag set ready to implement. |

package/templates/.agent/skills/seo-image-gen/SKILL.md

@@ -0,0 +1,183 @@
+---
+name: seo-image-gen
+description: "Generate SEO-focused images such as OG cards, hero images, schema assets, product visuals, and infographics. Use when image generation is part of an SEO workflow or content publishing task."
+risk: unknown
+source: "https://github.com/AgriciDaniel/claude-seo"
+date_added: "2026-03-21"
+argument-hint: "[og|hero|product|infographic|custom|batch] <description>"
+user-invokable: true
+allowed-tools:
+  - Read
+  - Grep
+  - Glob
+  - Bash
+  - WebFetch
+  - Write
+---
+
+# SEO Image Gen: AI Image Generation for SEO Assets (Extension)
+
+Generate production-ready images for SEO use cases using Gemini's image generation
+via the banana Creative Director pipeline. Maps SEO needs to optimized domain modes,
+aspect ratios, and resolution defaults.
+
+## When to Use
+
+- Use when generating OG images, hero images, schema visuals, infographics, or similar SEO assets.
+- Use when image generation is part of a broader SEO or publishing workflow.
+- Use only when the required image-generation extension is available.
+
+## Architecture Note
+
+This skill has two components with distinct roles:
+- **SKILL.md** (this file): Handles interactive `/seo image-gen` commands for generating images
+- **Agent** (`agents/seo-image-gen.md`): Audit-only analyst spawned during `/seo audit` to assess existing OG/social images and produce a generation plan (never auto-generates)
+
+## Prerequisites
+
+This skill requires the banana extension to be installed:
+```bash
+./extensions/banana/install.sh
+```
+
+**Check availability:** Before using any image generation tool, verify the MCP server
+is connected by checking if `gemini_generate_image` or `set_aspect_ratio` tools are
+available. If tools are not available, inform the user the extension is not installed
+and provide install instructions.
+
+## Quick Reference
+
+| Command | What it does |
+|---------|-------------|
+| `/seo image-gen og <description>` | Generate OG/social preview image (1200x630 feel) |
+| `/seo image-gen hero <description>` | Blog hero image (widescreen, dramatic) |
+| `/seo image-gen product <description>` | Product photography (clean, white BG) |
+| `/seo image-gen infographic <description>` | Infographic visual (vertical, data-heavy) |
+| `/seo image-gen custom <description>` | Custom image with full Creative Director pipeline |
+| `/seo image-gen batch <description> [N]` | Generate N variations (default: 3) |
+
+## SEO Image Use Cases
+
+Each use case maps to pre-configured banana parameters:
+
+| Use Case | Aspect Ratio | Resolution | Domain Mode | Notes |
+|----------|-------------|------------|-------------|-------|
+| **OG/Social Preview** | `16:9` | `1K` | Product or UI/Web | Clean, professional, text-friendly |
+| **Blog Hero** | `16:9` | `2K` | Cinema or Editorial | Dramatic, atmospheric, editorial quality |
+| **Schema Image** | `4:3` | `1K` | Product | Clean, descriptive, schema ImageObject |
+| **Social Square** | `1:1` | `1K` | UI/Web | Platform-optimized square |
+| **Product Photo** | `4:3` | `2K` | Product | White background, studio lighting |
+| **Infographic** | `2:3` | `4K` | Infographic | Data-heavy, vertical layout |
+| **Favicon/Icon** | `1:1` | `512` | Logo | Minimal, scalable, recognizable |
+| **Pinterest Pin** | `2:3` | `2K` | Editorial | Tall vertical card |
+
+## Generation Pipeline
+
+For every generation request:
+
+1. **Identify use case** from command or context (og, hero, product, etc.)
+2. **Apply SEO defaults** from the use cases table above
+3. **Set aspect ratio** via `set_aspect_ratio` MCP tool
+4. **Construct Reasoning Brief** using the banana Creative Director pipeline:
+   - Load `references/prompt-engineering.md` for the 6-component system
+   - Apply domain mode emphasis (Subject 30%, Style 25%, Context 15%, etc.)
+   - Be SPECIFIC and VISCERAL: describe what the camera sees
+5. **Generate** via `gemini_generate_image` MCP tool
+6. **Post-generation SEO checklist** (see below)
+
+### Check for Presets
+
+If the user mentions a brand or has SEO presets configured:
+```bash
+python3 ~/.claude/skills/seo-image-gen/scripts/presets.py list
+```
+Load matching preset and apply as defaults. Also check `references/seo-image-presets.md`
+for SEO-specific preset templates.
+
+## Post-Generation SEO Checklist
+
+After every successful generation, guide the user on:
+
+1. **Alt text**:Write descriptive, keyword-rich alt text for the generated image
+2. **File naming**:Rename to SEO-friendly format: `keyword-description-widthxheight.webp`
+3. **WebP conversion**:Convert to WebP for optimal page speed:
+   ```bash
+   magick output.png -quality 85 output.webp
+   ```
+4. **File size**:Target under 200KB for hero images, under 100KB for thumbnails
+5. **Schema markup**:Suggest `ImageObject` schema for the generated image:
+   ```json
+   {
+     "@type": "ImageObject",
+     "url": "https://example.com/images/keyword-description.webp",
+     "width": 1200,
+     "height": 630,
+     "caption": "Descriptive caption with target keyword"
+   }
+   ```
+6. **OG meta tags**:For social preview images, remind about:
+   ```html
+   <meta property="og:image" content="https://example.com/images/og-image.webp" />
+   <meta property="og:image:width" content="1200" />
+   <meta property="og:image:height" content="630" />
+   <meta property="og:image:alt" content="Descriptive alt text" />
+   ```
+
+## Cost Awareness
+
+Image generation costs money. Be transparent:
+- Show estimated cost before generating (especially for batch)
+- Log every generation: `python3 ~/.claude/skills/seo-image-gen/scripts/cost_tracker.py log --model MODEL --resolution RES --prompt "brief"`
+- Run `cost_tracker.py summary` if user asks about usage
+
+Approximate costs (gemini-3.1-flash):
+- 512: ~$0.02/image
+- 1K resolution: ~$0.04/image
+- 2K resolution: ~$0.08/image
+- 4K resolution: ~$0.16/image
+
+## Model Routing
+
+| Scenario | Model | Why |
+|----------|-------|-----|
+| OG images, social previews | `gemini-3.1-flash-image-preview` @ 1K | Fast, cost-effective |
+| Hero images, product photos | `gemini-3.1-flash-image-preview` @ 2K | Quality + detail |
+| Infographics with text | `gemini-3.1-flash-image-preview` @ 2K, thinking: high | Better text rendering |
+| Quick drafts | `gemini-2.5-flash-image` @ 512 | Rapid iteration |
+
+## Error Handling
+
+| Error | Resolution |
+|-------|-----------|
+| MCP not configured | Run `./extensions/banana/install.sh` |
+| API key invalid | New key at https://aistudio.google.com/apikey |
+| Rate limited (429) | Wait 60s, retry. Free tier: ~10 RPM / ~500 RPD |
+| `IMAGE_SAFETY` | Rephrase prompt - see `references/prompt-engineering.md` Safety section |
+| MCP unavailable | Fall back: `python3 ~/.claude/skills/seo-image-gen/scripts/generate.py --prompt "..." --aspect-ratio "16:9"` |
+| Extension not installed | Show install instructions: `./extensions/banana/install.sh` |
+
+## Cross-Skill Integration
+
+- **seo-images** (analysis) feeds into **seo-image-gen** (generation): audit results from `/seo images` identify missing or low-quality images; use those findings to drive `/seo image-gen` commands
+- **seo-audit** spawns the seo-image-gen **agent** (not this skill) to analyze OG/social images across the site and produce a prioritized generation plan
+- **seo-schema** can consume generated images: after generation, suggest `ImageObject` schema markup pointing to the new assets
+
+## Reference Documentation
+
+Load on-demand. Do NOT load all at startup:
+- `references/prompt-engineering.md`:6-component system, domain modes, templates
+- `references/gemini-models.md`:Model specs, rate limits, capabilities
+- `references/mcp-tools.md`:MCP tool parameters and responses
+- `references/post-processing.md`:ImageMagick/FFmpeg pipeline recipes
+- `references/cost-tracking.md`:Pricing, usage tracking
+- `references/presets.md`:Brand preset management
+- `references/seo-image-presets.md`:SEO-specific preset templates
+
+## Response Format
+
+After generating, always provide:
+1. **Image path**:where it was saved
+2. **Crafted prompt**:show what was sent to the API (educational)
+3. **Settings**:model, aspect ratio, resolution
+4. **SEO checklist**:alt text suggestion, file naming, WebP conversion
+5. **Schema snippet**:ImageObject or og:image markup if applicable