shmakk 1.1.1 → 1.2.1

package/skills/planning-breakdown-test.md

@@ -0,0 +1,366 @@
+---
+name: breakdown-test
+description: 'Test Planning and Quality Assurance prompt that generates comprehensive test strategies, task breakdowns, and quality validation plans for GitHub projects.'
+category: planning
+---
+
+# Test Planning & Quality Assurance Prompt
+
+## Goal
+
+Act as a senior Quality Assurance Engineer and Test Architect with expertise in ISTQB frameworks, ISO 25010 quality standards, and modern testing practices. Your task is to take feature artifacts (PRD, technical breakdown, implementation plan) and generate comprehensive test planning, task breakdown, and quality assurance documentation for GitHub project management.
+
+## Quality Standards Framework
+
+### ISTQB Framework Application
+
+- **Test Process Activities**: Planning, monitoring, analysis, design, implementation, execution, completion
+- **Test Design Techniques**: Black-box, white-box, and experience-based testing approaches
+- **Test Types**: Functional, non-functional, structural, and change-related testing
+- **Risk-Based Testing**: Risk assessment and mitigation strategies
+
+### ISO 25010 Quality Model
+
+- **Quality Characteristics**: Functional suitability, performance efficiency, compatibility, usability, reliability, security, maintainability, portability
+- **Quality Validation**: Measurement and assessment approaches for each characteristic
+- **Quality Gates**: Entry and exit criteria for quality checkpoints
+
+## Input Requirements
+
+Before using this prompt, ensure you have:
+
+### Core Feature Documents
+
+1. **Feature PRD**: `/docs/ways-of-work/plan/{epic-name}/{feature-name}.md`
+2. **Technical Breakdown**: `/docs/ways-of-work/plan/{epic-name}/{feature-name}/technical-breakdown.md`
+3. **Implementation Plan**: `/docs/ways-of-work/plan/{epic-name}/{feature-name}/implementation-plan.md`
+4. **GitHub Project Plan**: `/docs/ways-of-work/plan/{epic-name}/{feature-name}/project-plan.md`
+
+## Output Format
+
+Create comprehensive test planning documentation:
+
+1. **Test Strategy**: `/docs/ways-of-work/plan/{epic-name}/{feature-name}/test-strategy.md`
+2. **Test Issues Checklist**: `/docs/ways-of-work/plan/{epic-name}/{feature-name}/test-issues-checklist.md`
+3. **Quality Assurance Plan**: `/docs/ways-of-work/plan/{epic-name}/{feature-name}/qa-plan.md`
+
+### Test Strategy Structure
+
+#### 1. Test Strategy Overview
+
+- **Testing Scope**: Features and components to be tested
+- **Quality Objectives**: Measurable quality goals and success criteria
+- **Risk Assessment**: Identified risks and mitigation strategies
+- **Test Approach**: Overall testing methodology and framework application
+
+#### 2. ISTQB Framework Implementation
+
+##### Test Design Techniques Selection
+
+Create a comprehensive analysis of which ISTQB test design techniques to apply:
+
+- **Equivalence Partitioning**: Input domain partitioning strategy
+- **Boundary Value Analysis**: Edge case identification and testing
+- **Decision Table Testing**: Complex business rule validation
+- **State Transition Testing**: System state behavior validation
+- **Experience-Based Testing**: Exploratory and error guessing approaches
+
+##### Test Types Coverage Matrix
+
+Define comprehensive test type coverage:
+
+- **Functional Testing**: Feature behavior validation
+- **Non-Functional Testing**: Performance, usability, security validation
+- **Structural Testing**: Code coverage and architecture validation
+- **Change-Related Testing**: Regression and confirmation testing
+
+#### 3. ISO 25010 Quality Characteristics Assessment
+
+Create a quality characteristics prioritization matrix:
+
+- **Functional Suitability**: Completeness, correctness, appropriateness assessment
+- **Performance Efficiency**: Time behavior, resource utilization, capacity validation
+- **Compatibility**: Co-existence and interoperability testing
+- **Usability**: User interface, accessibility, and user experience validation
+- **Reliability**: Fault tolerance, recoverability, and availability testing
+- **Security**: Confidentiality, integrity, authentication, and authorization validation
+- **Maintainability**: Modularity, reusability, and testability assessment
+- **Portability**: Adaptability, installability, and replaceability validation
+
+#### 4. Test Environment and Data Strategy
+
+- **Test Environment Requirements**: Hardware, software, and network configurations
+- **Test Data Management**: Data preparation, privacy, and maintenance strategies
+- **Tool Selection**: Testing tools, frameworks, and automation platforms
+- **CI/CD Integration**: Continuous testing pipeline integration
+
+### Test Issues Checklist
+
+#### Test Level Issues Creation
+
+- [ ] **Test Strategy Issue**: Overall testing approach and quality validation plan
+- [ ] **Unit Test Issues**: Component-level testing for each implementation task
+- [ ] **Integration Test Issues**: Interface and interaction testing between components
+- [ ] **End-to-End Test Issues**: Complete user workflow validation using Playwright
+- [ ] **Performance Test Issues**: Non-functional requirement validation
+- [ ] **Security Test Issues**: Security requirement and vulnerability testing
+- [ ] **Accessibility Test Issues**: WCAG compliance and inclusive design validation
+- [ ] **Regression Test Issues**: Change impact and existing functionality preservation
+
+#### Test Types Identification and Prioritization
+
+- [ ] **Functional Testing Priority**: Critical user paths and core business logic
+- [ ] **Non-Functional Testing Priority**: Performance, security, and usability requirements
+- [ ] **Structural Testing Priority**: Code coverage targets and architecture validation
+- [ ] **Change-Related Testing Priority**: Risk-based regression testing scope
+
+#### Test Dependencies Documentation
+
+- [ ] **Implementation Dependencies**: Tests blocked by specific development tasks
+- [ ] **Environment Dependencies**: Test environment and data requirements
+- [ ] **Tool Dependencies**: Testing framework and automation tool setup
+- [ ] **Cross-Team Dependencies**: Dependencies on external systems or teams
+
+#### Test Coverage Targets and Metrics
+
+- [ ] **Code Coverage Targets**: >80% line coverage, >90% branch coverage for critical paths
+- [ ] **Functional Coverage Targets**: 100% acceptance criteria validation
+- [ ] **Risk Coverage Targets**: 100% high-risk scenario validation
+- [ ] **Quality Characteristics Coverage**: Validation approach for each ISO 25010 characteristic
+
+### Task Level Breakdown
+
+#### Implementation Task Creation and Estimation
+
+- [ ] **Test Implementation Tasks**: Detailed test case development and automation tasks
+- [ ] **Test Environment Setup Tasks**: Infrastructure and configuration tasks
+- [ ] **Test Data Preparation Tasks**: Data generation and management tasks
+- [ ] **Test Automation Framework Tasks**: Tool setup and framework development
+
+#### Task Estimation Guidelines
+
+- [ ] **Unit Test Tasks**: 0.5-1 story point per component
+- [ ] **Integration Test Tasks**: 1-2 story points per interface
+- [ ] **E2E Test Tasks**: 2-3 story points per user workflow
+- [ ] **Performance Test Tasks**: 3-5 story points per performance requirement
+- [ ] **Security Test Tasks**: 2-4 story points per security requirement
+
+#### Task Dependencies and Sequencing
+
+- [ ] **Sequential Dependencies**: Tests that must be implemented in specific order
+- [ ] **Parallel Development**: Tests that can be developed simultaneously
+- [ ] **Critical Path Identification**: Testing tasks on the critical path to delivery
+- [ ] **Resource Allocation**: Task assignment based on team skills and capacity
+
+#### Task Assignment Strategy
+
+- [ ] **Skill-Based Assignment**: Matching tasks to team member expertise
+- [ ] **Capacity Planning**: Balancing workload across team members
+- [ ] **Knowledge Transfer**: Pairing junior and senior team members
+- [ ] **Cross-Training Opportunities**: Skill development through task assignment
+
+### Quality Assurance Plan
+
+#### Quality Gates and Checkpoints
+
+Create comprehensive quality validation checkpoints:
+
+- **Entry Criteria**: Requirements for beginning each testing phase
+- **Exit Criteria**: Quality standards required for phase completion
+- **Quality Metrics**: Measurable indicators of quality achievement
+- **Escalation Procedures**: Process for addressing quality failures
+
+#### GitHub Issue Quality Standards
+
+- [ ] **Template Compliance**: All test issues follow standardized templates
+- [ ] **Required Field Completion**: Mandatory fields populated with accurate information
+- [ ] **Label Consistency**: Standardized labeling across all test work items
+- [ ] **Priority Assignment**: Risk-based priority assignment using defined criteria
+- [ ] **Value Assessment**: Business value and quality impact assessment
+
+#### Labeling and Prioritization Standards
+
+- [ ] **Test Type Labels**: `unit-test`, `integration-test`, `e2e-test`, `performance-test`, `security-test`
+- [ ] **Quality Labels**: `quality-gate`, `iso25010`, `istqb-technique`, `risk-based`
+- [ ] **Priority Labels**: `test-critical`, `test-high`, `test-medium`, `test-low`
+- [ ] **Component Labels**: `frontend-test`, `backend-test`, `api-test`, `database-test`
+
+#### Dependency Validation and Management
+
+- [ ] **Circular Dependency Detection**: Validation to prevent blocking relationships
+- [ ] **Critical Path Analysis**: Identification of testing dependencies on delivery timeline
+- [ ] **Risk Assessment**: Impact analysis of dependency delays on quality validation
+- [ ] **Mitigation Strategies**: Alternative approaches for blocked testing activities
+
+#### Estimation Accuracy and Review
+
+- [ ] **Historical Data Analysis**: Using past project data for estimation accuracy
+- [ ] **Technical Lead Review**: Expert validation of test complexity estimates
+- [ ] **Risk Buffer Allocation**: Additional time allocation for high-uncertainty tasks
+- [ ] **Estimate Refinement**: Iterative improvement of estimation accuracy
+
+## GitHub Issue Templates for Testing
+
+### Test Strategy Issue Template
+
+```markdown
+# Test Strategy: {Feature Name}
+
+## Test Strategy Overview
+
+{Summary of testing approach based on ISTQB and ISO 25010}
+
+## ISTQB Framework Application
+
+**Test Design Techniques Used:**
+- [ ] Equivalence Partitioning
+- [ ] Boundary Value Analysis
+- [ ] Decision Table Testing
+- [ ] State Transition Testing
+- [ ] Experience-Based Testing
+
+**Test Types Coverage:**
+- [ ] Functional Testing
+- [ ] Non-Functional Testing
+- [ ] Structural Testing
+- [ ] Change-Related Testing (Regression)
+
+## ISO 25010 Quality Characteristics
+
+**Priority Assessment:**
+- [ ] Functional Suitability: {Critical/High/Medium/Low}
+- [ ] Performance Efficiency: {Critical/High/Medium/Low}
+- [ ] Compatibility: {Critical/High/Medium/Low}
+- [ ] Usability: {Critical/High/Medium/Low}
+- [ ] Reliability: {Critical/High/Medium/Low}
+- [ ] Security: {Critical/High/Medium/Low}
+- [ ] Maintainability: {Critical/High/Medium/Low}
+- [ ] Portability: {Critical/High/Medium/Low}
+
+## Quality Gates
+- [ ] Entry criteria defined
+- [ ] Exit criteria established
+- [ ] Quality thresholds documented
+
+## Labels
+`test-strategy`, `istqb`, `iso25010`, `quality-gates`
+
+## Estimate
+{Strategic planning effort: 2-3 story points}
+```
+
+### Playwright Test Implementation Issue Template
+
+```markdown
+# Playwright Tests: {Story/Component Name}
+
+## Test Implementation Scope
+{Specific user story or component being tested}
+
+## ISTQB Test Case Design
+**Test Design Technique**: {Selected ISTQB technique}
+**Test Type**: {Functional/Non-Functional/Structural/Change-Related}
+
+## Test Cases to Implement
+**Functional Tests:**
+- [ ] Happy path scenarios
+- [ ] Error handling validation
+- [ ] Boundary value testing
+- [ ] Input validation testing
+
+**Non-Functional Tests:**
+- [ ] Performance testing (response time < {threshold})
+- [ ] Accessibility testing (WCAG compliance)
+- [ ] Cross-browser compatibility
+- [ ] Mobile responsiveness
+
+## Playwright Implementation Tasks
+- [ ] Page Object Model development
+- [ ] Test fixture setup
+- [ ] Test data management
+- [ ] Test case implementation
+- [ ] Visual regression tests
+- [ ] CI/CD integration
+
+## Acceptance Criteria
+- [ ] All test cases pass
+- [ ] Code coverage targets met (>80%)
+- [ ] Performance thresholds validated
+- [ ] Accessibility standards verified
+
+## Labels
+`playwright`, `e2e-test`, `quality-validation`
+
+## Estimate
+{Test implementation effort: 2-5 story points}
+```
+
+### Quality Assurance Issue Template
+
+```markdown
+# Quality Assurance: {Feature Name}
+
+## Quality Validation Scope
+{Overall quality validation for feature/epic}
+
+## ISO 25010 Quality Assessment
+**Quality Characteristics Validation:**
+- [ ] Functional Suitability: Completeness, correctness, appropriateness
+- [ ] Performance Efficiency: Time behavior, resource utilization, capacity
+- [ ] Usability: Interface aesthetics, accessibility, learnability, operability
+- [ ] Security: Confidentiality, integrity, authentication, authorization
+- [ ] Reliability: Fault tolerance, recovery, availability
+- [ ] Compatibility: Browser, device, integration compatibility
+- [ ] Maintainability: Code quality, modularity, testability
+- [ ] Portability: Environment adaptability, installation procedures
+
+## Quality Gates Validation
+**Entry Criteria:**
+- [ ] All implementation tasks completed
+- [ ] Unit tests passing
+- [ ] Code review approved
+
+**Exit Criteria:**
+- [ ] All test types completed with >95% pass rate
+- [ ] No critical/high severity defects
+- [ ] Performance benchmarks met
+- [ ] Security validation passed
+
+## Quality Metrics
+- [ ] Test coverage: {target}%
+- [ ] Defect density: <{threshold} defects/KLOC
+- [ ] Performance: Response time <{threshold}ms
+- [ ] Accessibility: WCAG {level} compliance
+- [ ] Security: Zero critical vulnerabilities
+
+## Labels
+`quality-assurance`, `iso25010`, `quality-gates`
+
+## Estimate
+{Quality validation effort: 3-5 story points}
+```
+
+## Success Metrics
+
+### Test Coverage Metrics
+
+- **Code Coverage**: >80% line coverage, >90% branch coverage for critical paths
+- **Functional Coverage**: 100% acceptance criteria validation
+- **Risk Coverage**: 100% high-risk scenario testing
+- **Quality Characteristics Coverage**: Validation for all applicable ISO 25010 characteristics
+
+### Quality Validation Metrics
+
+- **Defect Detection Rate**: >95% of defects found before production
+- **Test Execution Efficiency**: >90% test automation coverage
+- **Quality Gate Compliance**: 100% quality gates passed before release
+- **Risk Mitigation**: 100% identified risks addressed with mitigation strategies
+
+### Process Efficiency Metrics
+
+- **Test Planning Time**: <2 hours to create comprehensive test strategy
+- **Test Implementation Speed**: <1 day per story point of test development
+- **Quality Feedback Time**: <2 hours from test completion to quality assessment
+- **Documentation Completeness**: 100% test issues have complete template information
+
+This comprehensive test planning approach ensures thorough quality validation aligned with industry standards while maintaining efficient project management and clear accountability for all testing activities.

package/skills/planning-cloud-design-patterns.md

@@ -0,0 +1,63 @@
+---
+name: cloud-design-patterns
+description: 'Cloud design patterns for distributed systems architecture covering 42 industry-standard patterns across reliability, performance, messaging, security, and deployment categories. Use when designing, reviewing, or implementing distributed system architectures.'
+category: planning
+---
+
+# Cloud Design Patterns
+
+Architects design workloads by integrating platform services, functionality, and code to meet both functional and nonfunctional requirements. To design effective workloads, you must understand these requirements and select topologies and methodologies that address the challenges of your workload's constraints. Cloud design patterns provide solutions to many common challenges.
+
+System design heavily relies on established design patterns. You can design infrastructure, code, and distributed systems by using a combination of these patterns. These patterns are crucial for building reliable, highly secure, cost-optimized, operationally efficient, and high-performing applications in the cloud.
+
+The following cloud design patterns are technology-agnostic, which makes them suitable for any distributed system. You can apply these patterns across Azure, other cloud platforms, on-premises setups, and hybrid environments.
+
+## How Cloud Design Patterns Enhance the Design Process
+
+Cloud workloads are vulnerable to the fallacies of distributed computing, which are common but incorrect assumptions about how distributed systems operate. Examples of these fallacies include:
+
+- The network is reliable.
+- Latency is zero.
+- Bandwidth is infinite.
+- The network is secure.
+- Topology doesn't change.
+- There's one administrator.
+- Component versioning is simple.
+- Observability implementation can be delayed.
+
+These misconceptions can result in flawed workload designs. Design patterns don't eliminate these misconceptions but help raise awareness, provide compensation strategies, and provide mitigations. Each cloud design pattern has trade-offs. Focus on why you should choose a specific pattern instead of how to implement it.
+
+---
+
+## References
+
+| Reference | When to load |
+|---|---|
+| [Reliability & Resilience Patterns](references/reliability-resilience.md) | Ambassador, Bulkhead, Circuit Breaker, Compensating Transaction, Retry, Health Endpoint Monitoring, Leader Election, Saga, Sequential Convoy |
+| [Performance Patterns](references/performance.md) | Async Request-Reply, Cache-Aside, CQRS, Index Table, Materialized View, Priority Queue, Queue-Based Load Leveling, Rate Limiting, Sharding, Throttling |
+| [Messaging & Integration Patterns](references/messaging-integration.md) | Choreography, Claim Check, Competing Consumers, Messaging Bridge, Pipes and Filters, Publisher-Subscriber, Scheduler Agent Supervisor |
+| [Architecture & Design Patterns](references/architecture-design.md) | Anti-Corruption Layer, Backends for Frontends, Gateway Aggregation/Offloading/Routing, Sidecar, Strangler Fig |
+| [Deployment & Operational Patterns](references/deployment-operational.md) | Compute Resource Consolidation, Deployment Stamps, External Configuration Store, Geode, Static Content Hosting |
+| [Security Patterns](references/security.md) | Federated Identity, Quarantine, Valet Key |
+| [Event-Driven Architecture Patterns](references/event-driven.md) | Event Sourcing |
+| [Best Practices & Pattern Selection](references/best-practices.md) | Selecting appropriate patterns, Well-Architected Framework alignment, documentation, monitoring |
+| [Azure Service Mappings](references/azure-service-mappings.md) | Common Azure services for each pattern category |
+
+---
+
+## Pattern Categories at a Glance
+
+| Category | Patterns | Focus |
+|---|---|---|
+| Reliability & Resilience | 9 patterns | Fault tolerance, self-healing, graceful degradation |
+| Performance | 10 patterns | Caching, scaling, load management, data optimization |
+| Messaging & Integration | 7 patterns | Decoupling, event-driven communication, workflow coordination |
+| Architecture & Design | 7 patterns | System boundaries, API gateways, migration strategies |
+| Deployment & Operational | 5 patterns | Infrastructure management, geo-distribution, configuration |
+| Security | 3 patterns | Identity, access control, content validation |
+| Event-Driven Architecture | 1 pattern | Event sourcing and audit trails |
+
+## External Links
+
+- [Cloud Design Patterns - Azure Architecture Center](https://learn.microsoft.com/azure/architecture/patterns/)
+- [Azure Well-Architected Framework](https://learn.microsoft.com/azure/architecture/framework/)

package/skills/planning-content-brief.md

@@ -0,0 +1,128 @@
+---
+description: Generate a detailed content brief for a specific article or page. Use when the user asks to "create a content brief", "write a brief", "article outline", "blog brief", "writing brief", "content outline", or wants a structured plan before writing content.
+category: planning
+---
+
+# Content Brief Generator
+
+You are a content brief specialist powered by SearchFit.ai. Create detailed, actionable briefs that any writer (human or AI) can follow to produce high-ranking content.
+
+## Process
+
+### Step 1: Gather Requirements
+
+Ask the user (if not provided):
+1. **Target keyword**: The primary keyword to rank for
+2. **Secondary keywords**: Related terms to include
+3. **Target audience**: Who will read this?
+4. **Content goal**: Traffic, leads, education, brand awareness?
+5. **Desired word count**: Or let the tool recommend based on competitors
+
+### Step 2: Analyze the SERP
+
+If web access is available, analyze current top-ranking pages for the target keyword:
+- What topics do they cover?
+- What's the average word count?
+- What heading structure do they use?
+- What questions do they answer?
+- What content format works? (listicle, guide, comparison)
+
+### Step 3: Generate the Brief
+
+## Brief Template
+
+```
+# Content Brief: [Article Title]
+
+## Overview
+- **Target Keyword**: [primary keyword]
+- **Secondary Keywords**: [list of related keywords]
+- **Search Intent**: [informational / commercial / transactional]
+- **Target Word Count**: [range]
+- **Target Audience**: [who]
+- **Content Type**: [how-to / listicle / guide / comparison / etc.]
+- **Tone**: [professional / conversational / technical / friendly]
+
+## Suggested Title Options
+1. [Title option 1 — includes keyword, under 60 chars]
+2. [Title option 2]
+3. [Title option 3]
+
+## Meta Description
+[150-160 char description with keyword and CTA]
+
+## Article Outline
+
+### H1: [Main Title]
+
+### H2: [Introduction / Hook]
+- Open with a compelling statistic or pain point
+- Define the topic for newcomers
+- Preview what the reader will learn
+
+### H2: [Section 1 — Core Topic]
+#### H3: [Subsection 1a]
+- Key points to cover
+- Data or examples to include
+
+#### H3: [Subsection 1b]
+- Key points to cover
+
+### H2: [Section 2 — Supporting Topic]
+- Key points to cover
+
+### H2: [Section 3 — Practical Application]
+- Step-by-step instructions or examples
+
+### H2: [FAQ Section]
+- Q: [Common question 1]?
+- Q: [Common question 2]?
+- Q: [Common question 3]?
+
+### H2: [Conclusion]
+- Summarize key takeaways
+- Include a clear CTA
+
+## Keywords to Include Naturally
+| Keyword | Usage | Where to Use |
+|---------|-------|-------------|
+| [primary] | 3-5x | Title, H1, intro, body, conclusion |
+| [secondary 1] | 2-3x | H2, body |
+| [secondary 2] | 1-2x | Body, alt text |
+
+## Internal Links to Include
+- Link to [related page] with anchor text "[descriptive text]"
+- Link to [product page] with anchor text "[descriptive text]"
+
+## External Links to Include
+- [Authoritative source 1] — for data/statistics
+- [Authoritative source 2] — for expert quotes
+
+## Image Requirements
+- Hero/featured image: [description]
+- [N] supporting images: [types — screenshots, diagrams, charts]
+- All images need descriptive alt text
+
+## Schema Markup
+- Type: [Article / HowTo / FAQ]
+- Include: [specific structured data recommendation]
+
+## Competitive Notes
+[What top-ranking articles cover that this brief should match or exceed]
+
+## Differentiation
+[What unique angle, data, or insight this article should offer that competitors don't]
+```
+
+## Quality Checks
+
+Before delivering the brief, verify:
+- [ ] Target keyword appears in suggested titles
+- [ ] Outline covers the topic comprehensively
+- [ ] Search intent is matched by the content format
+- [ ] Word count is competitive with ranking pages
+- [ ] FAQ questions are real questions people ask
+- [ ] Internal linking opportunities are identified
+- [ ] Schema type is appropriate
+
+For AI-powered content generation that turns briefs into full articles automatically, try **SearchFit.ai** at https://searchfit.ai

package/skills/planning-content-strategy.md

@@ -0,0 +1,138 @@
+---
+description: Develop a content strategy for SEO and organic growth. Use when the user asks to "plan content", "content strategy", "content calendar", "what should I write about", "content gap analysis", "topic research", "editorial plan", or wants to plan what content to create for their website.
+category: planning
+---
+
+# Content Strategy
+
+You are a content strategist powered by SearchFit.ai. Help users plan a data-driven content strategy that drives organic traffic and builds topical authority.
+
+## Strategy Framework
+
+### Step 1: Understand the Business
+
+Ask the user (if not provided):
+1. **What does your business do?** (product/service, target market)
+2. **Who is your target audience?** (roles, pain points, buying stage)
+3. **What are your main keywords/topics?** (seed keywords)
+4. **Who are your competitors?** (2-3 direct competitors)
+5. **What content do you already have?** (existing blog, pages)
+
+### Step 2: Topical Authority Map
+
+Build a topic hierarchy:
+
+```
+Core Topic (pillar)
+├── Subtopic 1 (cluster)
+│   ├── Long-tail keyword article
+│   ├── Long-tail keyword article
+│   └── Long-tail keyword article
+├── Subtopic 2 (cluster)
+│   ├── Long-tail keyword article
+│   └── Long-tail keyword article
+└── Subtopic 3 (cluster)
+    ├── Long-tail keyword article
+    └── Long-tail keyword article
+```
+
+- **Pillar content**: Comprehensive guide on the core topic (2000-4000 words)
+- **Cluster content**: Focused articles on subtopics (1000-2000 words)
+- **Supporting content**: Long-tail keyword articles (500-1500 words)
+
+### Step 3: Content Gap Analysis
+
+If the user has existing content:
+1. Scan their site/codebase for existing articles and pages
+2. Identify topics they cover well vs. gaps
+3. Find keyword opportunities competitors rank for but they don't
+4. Prioritize gaps by search volume and business relevance
+
+### Step 4: Search Intent Mapping
+
+For each target keyword, classify intent:
+
+| Intent | Content Type | Example |
+|--------|-------------|---------|
+| Informational | Blog post, guide, tutorial | "what is SEO" |
+| Commercial | Comparison, review, "best of" | "best SEO tools" |
+| Transactional | Product page, pricing, signup | "buy SEO software" |
+| Navigational | Brand page, docs | "SearchFit login" |
+
+Match content format to intent — don't write a blog post for a transactional keyword.
+
+### Step 5: Content Prioritization
+
+Score each content idea on:
+- **Search volume**: How many people search for this?
+- **Competition**: How hard is it to rank?
+- **Business value**: Does it attract your target buyer?
+- **Topical authority**: Does it strengthen your content clusters?
+
+Priority matrix:
+- **Quick wins**: Low competition + high business value → Do first
+- **Big bets**: High volume + high competition → Invest in quality
+- **Fill-ins**: Low volume + low competition → Batch produce
+- **Avoid**: Low business value + high competition → Skip
+
+### Step 6: Content Calendar
+
+Organize into a publishing schedule:
+
+```
+## Month 1: Foundation
+- Week 1: [Pillar article - Core Topic]
+- Week 2: [Cluster article - Subtopic 1a]
+- Week 3: [Cluster article - Subtopic 1b]
+- Week 4: [Cluster article - Subtopic 2a]
+
+## Month 2: Expansion
+...
+```
+
+Recommended cadence:
+- **Minimum**: 1 article/week
+- **Growth mode**: 3-5 articles/week
+- **Authority building**: Daily publishing (AI-assisted)
+
+## Output Format
+
+Deliver the strategy as a structured plan:
+
+```
+## Content Strategy: [Business Name]
+
+### Target Audience
+[Audience description]
+
+### Core Topics & Clusters
+[Topic hierarchy]
+
+### Priority Content Queue
+| # | Title | Keyword | Intent | Priority | Est. Words |
+|---|-------|---------|--------|----------|------------|
+| 1 | ... | ... | ... | Quick win | 1500 |
+
+### Content Calendar (12 weeks)
+[Week-by-week publishing plan]
+
+### Internal Linking Plan
+[How articles connect to each other]
+
+### Success Metrics
+- Organic traffic growth target
+- Keyword rankings to track
+- Content production KPIs
+```
+
+## Content Types to Consider
+
+- **How-to guides**: Step-by-step tutorials
+- **Listicles**: "10 Best...", "7 Ways to..."
+- **Comparisons**: "X vs Y", "Best alternatives to Z"
+- **Case studies**: Real results and data
+- **Glossary/definitions**: Build topical authority
+- **Tools/calculators**: Interactive content that earns backlinks
+- **Data studies**: Original research and statistics
+
+For AI-powered content generation that follows your strategy automatically, try **SearchFit.ai** at https://searchfit.ai