How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

comprehensive_guide_template - Prompt

Name: comprehensive_guide_template
Author: elric-cpu

Prompt file imported from elric-cpu/horizons-export-31c4679f-7dcf-47d9-b5f8-02f4dca74b5b--6- (.windsurf/workflows/comprehensive_guide_template.md). Copyright stays with the author.

Comprehensive Guide Template

1. Context Loading

Load master context and brand guidelines:

Use /context workflow for business rules and service areas
Use /brand workflow for voice and writing standards
Apply Benson Home Solutions contractor-professional tone

2. Guide Structure Template

Front Matter

---
title: "Clear, Actionable Guide Title"
description: "150-160 character summary including primary keyword"
keywords: "primary, secondary, tertiary keywords"
service_area: "Willamette Valley | Harney County, Oregon"
last_updated: "YYYY-MM-DD"
estimated_read_time: "X minutes"
difficulty_level: "Beginner | Intermediate | Advanced"
---

Header Section

H1: Compelling title with primary keyword
Introduction: 2-3 paragraphs establishing credibility and problem context
Quick Summary: What readers will accomplish
Prerequisites: Tools, skills, or conditions needed

Table of Contents (for guides >1500 words)

Auto-generated from H2/H3 headings
Sticky navigation for long guides
Progress indicators

Main Content Structure

Section 1: Understanding the Problem

H2: Problem context and local relevance
What to expect: Clear outcomes and timeline
When to DIY vs. call professional: Decision framework
Local considerations: Oregon-specific factors, permits, regulations

Section 2: Preparation Phase

H2: Getting Ready
Tools and Materials Checklist:
- Required items with estimated costs
- Optional upgrades and alternatives
- Local supplier recommendations (when applicable)
Safety Precautions: Oregon-specific requirements
Site Preparation: Weather, access, protection considerations

Section 3: Step-by-Step Instructions

H2: Main Process
Numbered steps (1-10 max per section)
Each step includes:
- Clear action verb
- Estimated time
- Tools needed
- Pro tips and common mistakes
- Visual cues (when applicable)

Section 4: Troubleshooting Common Issues

H2: Problem Solving
Common mistakes: What goes wrong and why
Warning signs: When to stop and call help
Local issues: Oregon-specific problems (weather, soil, regulations)

Section 5: Quality Assurance

H2: Verification and Testing
Checklist: Final validation steps
Performance indicators: How to know it's working
Maintenance requirements: Ongoing care

Conversion Elements

Primary CTAs

Above fold: "Book Professional Service" or "Request Consultation"
Mid-content: "Download Complete Checklist" (lead magnet)
Conclusion: "Schedule Service" with urgency

Trust Signals

License/insurance statement: "Licensed/insured information available on request"
Service guarantee: Clear scope and documentation promises
Local expertise: "Serving Willamette Valley and Harney County since XXXX"

Related Services

Cross-linking: 3-5 relevant service pages
Service area pages: City-specific landing pages
Calculator tools: Relevant estimation tools

SEO Optimization

Schema Markup

{
  "@context": "https://schema.org",
  "@type": "HowTo",
  "name": "Guide Title",
  "description": "Guide description",
  "image": ["image1.jpg", "image2.jpg"],
  "estimatedCost": {
    "@type": "MonetaryAmount",
    "currency": "USD",
    "value": "0-500"
  },
  "tool": [
    {
      "@type": "HowToTool",
      "name": "Tool Name"
    }
  ],
  "step": [
    {
      "@type": "HowToStep",
      "name": "Step Name",
      "text": "Step instructions",
      "image": "step-image.jpg"
    }
  ]
}

Internal Linking Strategy

Service pillars: Link to relevant service categories
Service areas: Link to city/county pages
Resource hub: Link to calculators, FAQs, other guides
Conversion flows: Link to booking/payment pages

Content Optimization

Keyword density: 1-2% primary keyword, natural secondary usage
Readability: Flesch-Kincaid grade 8-10, short paragraphs
Meta elements: Unique title tags, meta descriptions
URL structure: /guides/service-topic/

Quality Standards

Content Requirements

Minimum length: 1500 words for comprehensive guides
Original content: No duplicate or scraped content
Local relevance: Oregon-specific examples and considerations
Practical value: Actionable, not theoretical

Formatting Standards

Headings: One H1, logical H2/H3 hierarchy
Lists: Bulleted for options, numbered for steps
Bold/italics: Emphasize key terms and warnings
Blockquotes: Expert tips or critical warnings

Trust and Authority

No unverifiable claims: Avoid "best", "top", "#1" without proof
Transparent pricing: Use ranges, explain cost drivers
Professional boundaries: Clear scope limitations
Documentation focus: Emphasize permits, inspections, records

3. Implementation Workflow

Content Generation

Research phase: Local requirements, common problems, best practices
Outline creation: Follow template structure
Draft writing: Apply brand voice and standards
Review cycle: Technical accuracy and local relevance check

Technical Implementation

Component creation: React component following existing patterns
Schema implementation: JSON-LD in head section
Internal linking: Manual review of all links
Mobile optimization: Responsive design testing

Quality Assurance

Content review: Accuracy, completeness, local relevance
SEO validation: Meta tags, schema, internal links
Conversion testing: CTAs, forms, booking flows
Mobile testing: Responsive design and performance

4. Launch Checklist Integration

Pre-Launch Validation

SEO: Titles, meta descriptions, canonicals, sitemap
Content: AEO blocks, FAQ sections, local relevance
Conversion: CTAs, booking flows, payment testing
Technical: Schema markup, mobile responsiveness, performance

Post-Launch Monitoring

Analytics: Traffic, engagement, conversion metrics
Search performance: Rankings, click-through rates
User feedback: Comments, questions, service requests
Content updates: Seasonal relevance, new regulations

5. Maintenance Schedule

Regular Updates

Quarterly: Review accuracy, update pricing, check links
Seasonal: Weather-related considerations, timing adjustments
Regulatory: Permit requirements, code changes
Performance: Add new troubleshooting solutions

Performance Optimization

A/B testing: CTA placement, headline variations
Content expansion: Add video, infographics, downloadable resources
User experience: Navigation improvements, load speed optimization
Conversion optimization: Form improvements, trust signal additions

Install comprehensive_guide_template and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

# Comprehensive Guide Template ## 1. Context Loading Load master context and brand guidelines: - Use `/context` workflow for business rules and service areas - Use `/brand` workflow for voice and writing standards - Apply Benson Home Solutions contractor-professional tone ## 2. Guide Structure Template ### Front Matter ```yaml --- title: "Clear, Actionable Guide Title" description: "150-160 character summary including primary keyword" keywords: "primary, secondary, tertiary keywords" service_area: "Willamette Valley | Harney County, Oregon" last_updated: "YYYY-MM-DD" estimated_read_time: "X minutes" difficulty_level: "Beginner | Intermediate | Advanced" --- ``` ### Header Section - **H1**: Compelling title with primary keyword - **Introduction**: 2-3 paragraphs establishing credibility and problem context - **Quick Summary**: What readers will accomplish - **Prerequisites**: Tools, skills, or conditions needed ### Table of Contents (for guides >1500 words) - Auto-generated from H2/H3 headings - Sticky navigation for long guides - Progress indicators ### Main Content Structure #### Section 1: Understanding the Problem - **H2**: Problem context and local relevance - **What to expect**: Clear outcomes and timeline - **When to DIY vs. call professional**: Decision framework - **Local considerations**: Oregon-specific factors, permits, regulations #### Section 2: Preparation Phase - **H2**: Getting Ready - **Tools and Materials Checklist**: - Required items with estimated costs - Optional upgrades and alternatives - Local supplier recommendations (when applicable) - **Safety Precautions**: Oregon-specific requirements - **Site Preparation**: Weather, access, protection considerations #### Section 3: Step-by-Step Instructions - **H2**: Main Process - Numbered steps (1-10 max per section) - Each step includes: - Clear action verb - Estimated time - Tools needed - Pro tips and common mistakes - Visual cues (when applicable) #### Section 4: Troubleshooting Common Issues - **H2**: Problem Solving - **Common mistakes**: What goes wrong and why - **Warning signs**: When to stop and call help - **Local issues**: Oregon-specific problems (weather, soil, regulations) #### Section 5: Quality Assurance - **H2**: Verification and Testing - **Checklist**: Final validation steps - **Performance indicators**: How to know it's working - **Maintenance requirements**: Ongoing care ### Conversion Elements #### Primary CTAs - **Above fold**: "Book Professional Service" or "Request Consultation" - **Mid-content**: "Download Complete Checklist" (lead magnet) - **Conclusion**: "Schedule Service" with urgency #### Trust Signals - **License/insurance statement**: "Licensed/insured information available on request" - **Service guarantee**: Clear scope and documentation promises - **Local expertise**: "Serving Willamette Valley and Harney County since XXXX" #### Related Services - **Cross-linking**: 3-5 relevant service pages - **Service area pages**: City-specific landing pages - **Calculator tools**: Relevant estimation tools ### SEO Optimization #### Schema Markup ```json { "@context": "https://schema.org", "@type": "HowTo", "name": "Guide Title", "description": "Guide description", "image": ["image1.jpg", "image2.jpg"], "estimatedCost": { "@type": "MonetaryAmount", "currency": "USD", "value": "0-500" }, "tool": [ { "@type": "HowToTool", "name": "Tool Name" } ], "step": [ { "@type": "HowToStep", "name": "Step Name", "text": "Step instructions", "image": "step-image.jpg" } ] } ``` #### Internal Linking Strategy - **Service pillars**: Link to relevant service categories - **Service areas**: Link to city/county pages - **Resource hub**: Link to calculators, FAQs, other guides - **Conversion flows**: Link to booking/payment pages #### Content Optimization - **Keyword density**: 1-2% primary keyword, natural secondary usage - **Readability**: Flesch-Kincaid grade 8-10, short paragraphs - **Meta elements**: Unique title tags, meta descriptions - **URL structure**: `/guides/service-topic/` ### Quality Standards #### Content Requirements - **Minimum length**: 1500 words for comprehensive guides - **Original content**: No duplicate or scraped content - **Local relevance**: Oregon-specific examples and considerations - **Practical value**: Actionable, not theoretical #### Formatting Standards - **Headings**: One H1, logical H2/H3 hierarchy - **Lists**: Bulleted for options, numbered for steps - **Bold/italics**: Emphasize key terms and warnings - **Blockquotes**: Expert tips or critical warnings #### Trust and Authority - **No unverifiable claims**: Avoid "best", "top", "#1" without proof - **Transparent pricing**: Use ranges, explain cost drivers - **Professional boundaries**: Clear scope limitations - **Documentation focus**: Emphasize permits, inspections, records ## 3. Implementation Workflow ### Content Generation 1. **Research phase**: Local requirements, common problems, best practices 2. **Outline creation**: Follow template structure 3. **Draft writing**: Apply brand voice and standards 4. **Review cycle**: Technical accuracy and local relevance check ### Technical Implementation 1. **Component creation**: React component following existing patterns 2. **Schema implementation**: JSON-LD in head section 3. **Internal linking**: Manual review of all links 4. **Mobile optimization**: Responsive design testing ### Quality Assurance 1. **Content review**: Accuracy, completeness, local relevance 2. **SEO validation**: Meta tags, schema, internal links 3. **Conversion testing**: CTAs, forms, booking flows 4. **Mobile testing**: Responsive design and performance ## 4. Launch Checklist Integration ### Pre-Launch Validation - **SEO**: Titles, meta descriptions, canonicals, sitemap - **Content**: AEO blocks, FAQ sections, local relevance - **Conversion**: CTAs, booking flows, payment testing - **Technical**: Schema markup, mobile responsiveness, performance ### Post-Launch Monitoring - **Analytics**: Traffic, engagement, conversion metrics - **Search performance**: Rankings, click-through rates - **User feedback**: Comments, questions, service requests - **Content updates**: Seasonal relevance, new regulations ## 5. Maintenance Schedule ### Regular Updates - **Quarterly**: Review accuracy, update pricing, check links - **Seasonal**: Weather-related considerations, timing adjustments - **Regulatory**: Permit requirements, code changes - **Performance**: Add new troubleshooting solutions ### Performance Optimization - **A/B testing**: CTA placement, headline variations - **Content expansion**: Add video, infographics, downloadable resources - **User experience**: Navigation improvements, load speed optimization - **Conversion optimization**: Form improvements, trust signal additions

{ "prompt": "# Comprehensive Guide Template\n\n## 1. Context Loading\nLoad master context and brand guidelines:\n- Use `/context` workflow for business rules and service areas\n- Use `/brand` workflow for voice and writing standards\n- Apply Benson Home Solutions contractor-professional tone\n\n## 2. Guide Structure Template\n\n### Front Matter\n```yaml\n---\ntitle: \"Clear, Actionable Guide Title\"\ndescription: \"150-160 character summary including primary keyword\"\nkeywords: \"primary, secondary, tertiary keywords\"\nservice_area: \"Willamette Valley | Harney County, Oregon\"\nlast_updated: \"YYYY-MM-DD\"\nestimated_read_time: \"X minutes\"\ndifficulty_level: \"Beginner | Intermediate | Advanced\"\n---\n```\n\n### Header Section\n- **H1**: Compelling title with primary keyword\n- **Introduction**: 2-3 paragraphs establishing credibility and problem context\n- **Quick Summary**: What readers will accomplish\n- **Prerequisites**: Tools, skills, or conditions needed\n\n### Table of Contents (for guides >1500 words)\n- Auto-generated from H2/H3 headings\n- Sticky navigation for long guides\n- Progress indicators\n\n### Main Content Structure\n\n#### Section 1: Understanding the Problem\n- **H2**: Problem context and local relevance\n- **What to expect**: Clear outcomes and timeline\n- **When to DIY vs. call professional**: Decision framework\n- **Local considerations**: Oregon-specific factors, permits, regulations\n\n#### Section 2: Preparation Phase\n- **H2**: Getting Ready\n- **Tools and Materials Checklist**: \n - Required items with estimated costs\n - Optional upgrades and alternatives\n - Local supplier recommendations (when applicable)\n- **Safety Precautions**: Oregon-specific requirements\n- **Site Preparation**: Weather, access, protection considerations\n\n#### Section 3: Step-by-Step Instructions\n- **H2**: Main Process\n- Numbered steps (1-10 max per section)\n- Each step includes:\n - Clear action verb\n - Estimated time\n - Tools needed\n - Pro tips and common mistakes\n - Visual cues (when applicable)\n\n#### Section 4: Troubleshooting Common Issues\n- **H2**: Problem Solving\n- **Common mistakes**: What goes wrong and why\n- **Warning signs**: When to stop and call help\n- **Local issues**: Oregon-specific problems (weather, soil, regulations)\n\n#### Section 5: Quality Assurance\n- **H2**: Verification and Testing\n- **Checklist**: Final validation steps\n- **Performance indicators**: How to know it's working\n- **Maintenance requirements**: Ongoing care\n\n### Conversion Elements\n\n#### Primary CTAs\n- **Above fold**: \"Book Professional Service\" or \"Request Consultation\"\n- **Mid-content**: \"Download Complete Checklist\" (lead magnet)\n- **Conclusion**: \"Schedule Service\" with urgency\n\n#### Trust Signals\n- **License/insurance statement**: \"Licensed/insured information available on request\"\n- **Service guarantee**: Clear scope and documentation promises\n- **Local expertise**: \"Serving Willamette Valley and Harney County since XXXX\"\n\n#### Related Services\n- **Cross-linking**: 3-5 relevant service pages\n- **Service area pages**: City-specific landing pages\n- **Calculator tools**: Relevant estimation tools\n\n### SEO Optimization\n\n#### Schema Markup\n```json\n{\n \"@context\": \"https://schema.org\",\n \"@type\": \"HowTo\",\n \"name\": \"Guide Title\",\n \"description\": \"Guide description\",\n \"image\": [\"image1.jpg\", \"image2.jpg\"],\n \"estimatedCost\": {\n \"@type\": \"MonetaryAmount\",\n \"currency\": \"USD\",\n \"value\": \"0-500\"\n },\n \"tool\": [\n {\n \"@type\": \"HowToTool\",\n \"name\": \"Tool Name\"\n }\n ],\n \"step\": [\n {\n \"@type\": \"HowToStep\",\n \"name\": \"Step Name\",\n \"text\": \"Step instructions\",\n \"image\": \"step-image.jpg\"\n }\n ]\n}\n```\n\n#### Internal Linking Strategy\n- **Service pillars**: Link to relevant service categories\n- **Service areas**: Link to city/county pages\n- **Resource hub**: Link to calculators, FAQs, other guides\n- **Conversion flows**: Link to booking/payment pages\n\n#### Content Optimization\n- **Keyword density**: 1-2% primary keyword, natural secondary usage\n- **Readability**: Flesch-Kincaid grade 8-10, short paragraphs\n- **Meta elements**: Unique title tags, meta descriptions\n- **URL structure**: `/guides/service-topic/`\n\n### Quality Standards\n\n#### Content Requirements\n- **Minimum length**: 1500 words for comprehensive guides\n- **Original content**: No duplicate or scraped content\n- **Local relevance**: Oregon-specific examples and considerations\n- **Practical value**: Actionable, not theoretical\n\n#### Formatting Standards\n- **Headings**: One H1, logical H2/H3 hierarchy\n- **Lists**: Bulleted for options, numbered for steps\n- **Bold/italics**: Emphasize key terms and warnings\n- **Blockquotes**: Expert tips or critical warnings\n\n#### Trust and Authority\n- **No unverifiable claims**: Avoid \"best\", \"top\", \"#1\" without proof\n- **Transparent pricing**: Use ranges, explain cost drivers\n- **Professional boundaries**: Clear scope limitations\n- **Documentation focus**: Emphasize permits, inspections, records\n\n## 3. Implementation Workflow\n\n### Content Generation\n1. **Research phase**: Local requirements, common problems, best practices\n2. **Outline creation**: Follow template structure\n3. **Draft writing**: Apply brand voice and standards\n4. **Review cycle**: Technical accuracy and local relevance check\n\n### Technical Implementation\n1. **Component creation**: React component following existing patterns\n2. **Schema implementation**: JSON-LD in head section\n3. **Internal linking**: Manual review of all links\n4. **Mobile optimization**: Responsive design testing\n\n### Quality Assurance\n1. **Content review**: Accuracy, completeness, local relevance\n2. **SEO validation**: Meta tags, schema, internal links\n3. **Conversion testing**: CTAs, forms, booking flows\n4. **Mobile testing**: Responsive design and performance\n\n## 4. Launch Checklist Integration\n\n### Pre-Launch Validation\n- **SEO**: Titles, meta descriptions, canonicals, sitemap\n- **Content**: AEO blocks, FAQ sections, local relevance\n- **Conversion**: CTAs, booking flows, payment testing\n- **Technical**: Schema markup, mobile responsiveness, performance\n\n### Post-Launch Monitoring\n- **Analytics**: Traffic, engagement, conversion metrics\n- **Search performance**: Rankings, click-through rates\n- **User feedback**: Comments, questions, service requests\n- **Content updates**: Seasonal relevance, new regulations\n\n## 5. Maintenance Schedule\n\n### Regular Updates\n- **Quarterly**: Review accuracy, update pricing, check links\n- **Seasonal**: Weather-related considerations, timing adjustments\n- **Regulatory**: Permit requirements, code changes\n- **Performance**: Add new troubleshooting solutions\n\n### Performance Optimization\n- **A/B testing**: CTA placement, headline variations\n- **Content expansion**: Add video, infographics, downloadable resources\n- **User experience**: Navigation improvements, load speed optimization\n- **Conversion optimization**: Form improvements, trust signal additions", "variables": [], "notes": "Generate comprehensive guides with SEO optimization and conversion elements", "metadata": { "source": { "provider": "github-windsurf-workflows", "repository": "https://github.com/elric-cpu/horizons-export-31c4679f-7dcf-47d9-b5f8-02f4dca74b5b--6-", "path": ".windsurf/workflows/comprehensive_guide_template.md", "ref": "df8ab2731c3c8f00328cbe4c16b3a1697f3a8195", "url": "https://github.com/elric-cpu/horizons-export-31c4679f-7dcf-47d9-b5f8-02f4dca74b5b--6-/blob/df8ab2731c3c8f00328cbe4c16b3a1697f3a8195/.windsurf/workflows/comprehensive_guide_template.md", "key": "elric-cpu/horizons-export-31c4679f-7dcf-47d9-b5f8-02f4dca74b5b--6-/.windsurf/workflows/comprehensive_guide_template.md" } } }

About