skill-library-mcp 1.0.0

package/skills/framework-migration-legacy-modernize/SKILL.md

@@ -0,0 +1,132 @@
+---
+name: framework-migration-legacy-modernize
+description: "Orchestrate a comprehensive legacy system modernization using the strangler fig pattern, enabling gradual replacement of outdated components while maintaining continuous business operations through ex"
+---
+
+# Legacy Code Modernization Workflow
+
+Orchestrate a comprehensive legacy system modernization using the strangler fig pattern, enabling gradual replacement of outdated components while maintaining continuous business operations through expert agent coordination.
+
+[Extended thinking: The strangler fig pattern, named after the tropical fig tree that gradually envelops and replaces its host, represents the gold standard for risk-managed legacy modernization. This workflow implements a systematic approach where new functionality gradually replaces legacy components, allowing both systems to coexist during transition. By orchestrating specialized agents for assessment, testing, security, and implementation, we ensure each migration phase is validated before proceeding, minimizing disruption while maximizing modernization velocity.]
+
+## Use this skill when
+
+- Working on legacy code modernization workflow tasks or workflows
+- Needing guidance, best practices, or checklists for legacy code modernization workflow
+
+## Do not use this skill when
+
+- The task is unrelated to legacy code modernization workflow
+- You need a different domain or tool outside this scope
+
+## Instructions
+
+- Clarify goals, constraints, and required inputs.
+- Apply relevant best practices and validate outcomes.
+- Provide actionable steps and verification.
+- If detailed examples are required, open `resources/implementation-playbook.md`.
+
+## Phase 1: Legacy Assessment and Risk Analysis
+
+### 1. Comprehensive Legacy System Analysis
+- Use Task tool with subagent_type="legacy-modernizer"
+- Prompt: "Analyze the legacy codebase at $ARGUMENTS. Document technical debt inventory including: outdated dependencies, deprecated APIs, security vulnerabilities, performance bottlenecks, and architectural anti-patterns. Generate a modernization readiness report with component complexity scores (1-10), dependency mapping, and database coupling analysis. Identify quick wins vs complex refactoring targets."
+- Expected output: Detailed assessment report with risk matrix and modernization priorities
+
+### 2. Dependency and Integration Mapping
+- Use Task tool with subagent_type="architect-review"
+- Prompt: "Based on the legacy assessment report, create a comprehensive dependency graph showing: internal module dependencies, external service integrations, shared database schemas, and cross-system data flows. Identify integration points that will require facade patterns or adapter layers during migration. Highlight circular dependencies and tight coupling that need resolution."
+- Context from previous: Legacy assessment report, component complexity scores
+- Expected output: Visual dependency map and integration point catalog
+
+### 3. Business Impact and Risk Assessment
+- Use Task tool with subagent_type="business-analytics::business-analyst"
+- Prompt: "Evaluate business impact of modernizing each component identified. Create risk assessment matrix considering: business criticality (revenue impact), user traffic patterns, data sensitivity, regulatory requirements, and fallback complexity. Prioritize components using a weighted scoring system: (Business Value × 0.4) + (Technical Risk × 0.3) + (Quick Win Potential × 0.3). Define rollback strategies for each component."
+- Context from previous: Component inventory, dependency mapping
+- Expected output: Prioritized migration roadmap with risk mitigation strategies
+
+## Phase 2: Test Coverage Establishment
+
+### 1. Legacy Code Test Coverage Analysis
+- Use Task tool with subagent_type="unit-testing::test-automator"
+- Prompt: "Analyze existing test coverage for legacy components at $ARGUMENTS. Use coverage tools to identify untested code paths, missing integration tests, and absent end-to-end scenarios. For components with <40% coverage, generate characterization tests that capture current behavior without modifying functionality. Create test harness for safe refactoring."
+- Expected output: Test coverage report and characterization test suite
+
+### 2. Contract Testing Implementation
+- Use Task tool with subagent_type="unit-testing::test-automator"
+- Prompt: "Implement contract tests for all integration points identified in dependency mapping. Create consumer-driven contracts for APIs, message queue interactions, and database schemas. Set up contract verification in CI/CD pipeline. Generate performance baselines for response times and throughput to validate modernized components maintain SLAs."
+- Context from previous: Integration point catalog, existing test coverage
+- Expected output: Contract test suite with performance baselines
+
+### 3. Test Data Management Strategy
+- Use Task tool with subagent_type="data-engineering::data-engineer"
+- Prompt: "Design test data management strategy for parallel system operation. Create data generation scripts for edge cases, implement data masking for sensitive information, and establish test database refresh procedures. Set up monitoring for data consistency between legacy and modernized components during migration."
+- Context from previous: Database schemas, test requirements
+- Expected output: Test data pipeline and consistency monitoring
+
+## Phase 3: Incremental Migration Implementation
+
+### 1. Strangler Fig Infrastructure Setup
+- Use Task tool with subagent_type="backend-development::backend-architect"
+- Prompt: "Implement strangler fig infrastructure with API gateway for traffic routing. Configure feature flags for gradual rollout using environment variables or feature management service. Set up proxy layer with request routing rules based on: URL patterns, headers, or user segments. Implement circuit breakers and fallback mechanisms for resilience. Create observability dashboard for dual-system monitoring."
+- Expected output: API gateway configuration, feature flag system, monitoring dashboard
+
+### 2. Component Modernization - First Wave
+- Use Task tool with subagent_type="python-development::python-pro" or "golang-pro" (based on target stack)
+- Prompt: "Modernize first-wave components (quick wins identified in assessment). For each component: extract business logic from legacy code, implement using modern patterns (dependency injection, SOLID principles), ensure backward compatibility through adapter patterns, maintain data consistency with event sourcing or dual writes. Follow 12-factor app principles. Components to modernize: [list from prioritized roadmap]"
+- Context from previous: Characterization tests, contract tests, infrastructure setup
+- Expected output: Modernized components with adapters
+
+### 3. Security Hardening
+- Use Task tool with subagent_type="security-scanning::security-auditor"
+- Prompt: "Audit modernized components for security vulnerabilities. Implement security improvements including: OAuth 2.0/JWT authentication, role-based access control, input validation and sanitization, SQL injection prevention, XSS protection, and secrets management. Verify OWASP top 10 compliance. Configure security headers and implement rate limiting."
+- Context from previous: Modernized component code
+- Expected output: Security audit report and hardened components
+
+## Phase 4: Performance Validation and Optimization
+
+### 1. Performance Testing and Optimization
+- Use Task tool with subagent_type="application-performance::performance-engineer"
+- Prompt: "Conduct performance testing comparing legacy vs modernized components. Run load tests simulating production traffic patterns, measure response times, throughput, and resource utilization. Identify performance regressions and optimize: database queries with indexing, caching strategies (Redis/Memcached), connection pooling, and async processing where applicable. Validate against SLA requirements."
+- Context from previous: Performance baselines, modernized components
+- Expected output: Performance test results and optimization recommendations
+
+### 2. Progressive Rollout and Monitoring
+- Use Task tool with subagent_type="deployment-strategies::deployment-engineer"
+- Prompt: "Implement progressive rollout strategy using feature flags. Start with 5% traffic to modernized components, monitor error rates, latency, and business metrics. Define automatic rollback triggers: error rate >1%, latency >2x baseline, or business metric degradation. Create runbook for traffic shifting: 5% → 25% → 50% → 100% with 24-hour observation periods."
+- Context from previous: Feature flag configuration, monitoring dashboard
+- Expected output: Rollout plan with automated safeguards
+
+## Phase 5: Migration Completion and Documentation
+
+### 1. Legacy Component Decommissioning
+- Use Task tool with subagent_type="legacy-modernizer"
+- Prompt: "Plan safe decommissioning of replaced legacy components. Verify no remaining dependencies through traffic analysis (minimum 30 days at 0% traffic). Archive legacy code with documentation of original functionality. Update CI/CD pipelines to remove legacy builds. Clean up unused database tables and remove deprecated API endpoints. Document any retained legacy components with sunset timeline."
+- Context from previous: Traffic routing data, modernization status
+- Expected output: Decommissioning checklist and timeline
+
+### 2. Documentation and Knowledge Transfer
+- Use Task tool with subagent_type="documentation-generation::docs-architect"
+- Prompt: "Create comprehensive modernization documentation including: architectural diagrams (before/after), API documentation with migration guides, runbooks for dual-system operation, troubleshooting guides for common issues, and lessons learned report. Generate developer onboarding guide for modernized system. Document technical decisions and trade-offs made during migration."
+- Context from previous: All migration artifacts and decisions
+- Expected output: Complete modernization documentation package
+
+## Configuration Options
+
+- **--parallel-systems**: Keep both systems running indefinitely (for gradual migration)
+- **--big-bang**: Full cutover after validation (higher risk, faster completion)
+- **--by-feature**: Migrate complete features rather than technical components
+- **--database-first**: Prioritize database modernization before application layer
+- **--api-first**: Modernize API layer while maintaining legacy backend
+
+## Success Criteria
+
+- All high-priority components modernized with >80% test coverage
+- Zero unplanned downtime during migration
+- Performance metrics maintained or improved (P95 latency within 110% of baseline)
+- Security vulnerabilities reduced by >90%
+- Technical debt score improved by >60%
+- Successful operation for 30 days post-migration without rollbacks
+- Complete documentation enabling new developer onboarding in <1 week
+
+Target: $ARGUMENTS

package/skills/free-tool-strategy/SKILL.md

@@ -0,0 +1,576 @@
+---
+name: free-tool-strategy
+description: When the user wants to plan, evaluate, or build a free tool for marketing purposes — lead generation, SEO value, or brand awareness. Also use when the user mentions "engineering as marketing," "free tool," "marketing tool," "calculator," "generator," "interactive tool," "lead gen tool," "build a tool for leads," or "free resource." This skill bridges engineering and marketing — useful for founders and technical marketers.
+---
+
+# Free Tool Strategy (Engineering as Marketing)
+
+You are an expert in engineering-as-marketing strategy. Your goal is to help plan and evaluate free tools that generate leads, attract organic traffic, and build brand awareness.
+
+## Initial Assessment
+
+Before designing a tool strategy, understand:
+
+1. **Business Context**
+   - What's the core product/service?
+   - Who is the target audience?
+   - What problems do they have?
+
+2. **Goals**
+   - Lead generation primary goal?
+   - SEO/traffic acquisition?
+   - Brand awareness?
+   - Product education?
+
+3. **Resources**
+   - Technical capacity to build?
+   - Ongoing maintenance bandwidth?
+   - Budget for promotion?
+
+---
+
+## Core Principles
+
+### 1. Solve a Real Problem
+- Tool must provide genuine value
+- Solves a problem your audience actually has
+- Useful even without your main product
+
+### 2. Adjacent to Core Product
+- Related to what you sell
+- Natural path from tool to product
+- Educates on problem you solve
+
+### 3. Simple and Focused
+- Does one thing well
+- Low friction to use
+- Immediate value
+
+### 4. Worth the Investment
+- Lead value × expected leads > build cost + maintenance
+- Consider SEO value
+- Consider brand halo effect
+
+---
+
+## Tool Types
+
+### Calculators
+
+**Best for**: Decisions involving numbers, comparisons, estimates
+
+**Examples**:
+- ROI calculator
+- Savings calculator
+- Cost comparison tool
+- Salary calculator
+- Tax estimator
+
+**Why they work**:
+- Personalized output
+- High perceived value
+- Share-worthy results
+- Clear problem → solution
+
+### Generators
+
+**Best for**: Creating something useful quickly
+
+**Examples**:
+- Policy generator
+- Template generator
+- Name/tagline generator
+- Email subject line generator
+- Resume builder
+
+**Why they work**:
+- Tangible output
+- Saves time
+- Easily shared
+- Repeat usage
+
+### Analyzers/Auditors
+
+**Best for**: Evaluating existing work or assets
+
+**Examples**:
+- Website grader
+- SEO analyzer
+- Email subject tester
+- Headline analyzer
+- Security checker
+
+**Why they work**:
+- Curiosity-driven
+- Personalized insights
+- Creates awareness of problems
+- Natural lead to solution
+
+### Testers/Validators
+
+**Best for**: Checking if something works
+
+**Examples**:
+- Meta tag preview
+- Email rendering test
+- Accessibility checker
+- Mobile-friendly test
+- Speed test
+
+**Why they work**:
+- Immediate utility
+- Bookmark-worthy
+- Repeat usage
+- Professional necessity
+
+### Libraries/Resources
+
+**Best for**: Reference material
+
+**Examples**:
+- Icon library
+- Template library
+- Code snippet library
+- Example gallery
+- Directory
+
+**Why they work**:
+- High SEO value
+- Ongoing traffic
+- Establishes authority
+- Linkable asset
+
+### Interactive Educational
+
+**Best for**: Learning/understanding
+
+**Examples**:
+- Interactive tutorials
+- Code playgrounds
+- Visual explainers
+- Quizzes/assessments
+- Simulators
+
+**Why they work**:
+- Engages deeply
+- Demonstrates expertise
+- Shareable
+- Memory-creating
+
+---
+
+## Ideation Framework
+
+### Start with Pain Points
+
+1. **What problems does your audience Google?**
+   - Search query research
+   - Common questions
+   - "How to" searches
+
+2. **What manual processes are tedious?**
+   - Tasks done in spreadsheets
+   - Repetitive calculations
+   - Copy-paste workflows
+
+3. **What do they need before buying your product?**
+   - Assessments of current state
+   - Planning/scoping
+   - Comparisons
+
+4. **What information do they wish they had?**
+   - Data they can't easily access
+   - Personalized insights
+   - Industry benchmarks
+
+### Validate the Idea
+
+**Search demand:**
+- Is there search volume for this problem?
+- What keywords would rank?
+- How competitive?
+
+**Uniqueness:**
+- What exists already?
+- How can you be 10x better or different?
+- What's your unique angle?
+
+**Lead quality:**
+- Does this problem-audience match buyers?
+- Will users be your target customers?
+- Is there a natural path to your product?
+
+**Build feasibility:**
+- How complex to build?
+- Can you scope an MVP?
+- Ongoing maintenance burden?
+
+---
+
+## SEO Considerations
+
+### Keyword Strategy
+
+**Tool landing page:**
+- "[thing] calculator"
+- "[thing] generator"
+- "free [tool type]"
+- "[industry] [tool type]"
+
+**Supporting content:**
+- "How to [use case]"
+- "What is [concept tool helps with]"
+- Blog posts that link to tool
+
+### Link Building
+
+Free tools attract links because:
+- Genuinely useful (people reference them)
+- Unique (can't link to just any page)
+- Shareable (social amplification)
+
+**Outreach opportunities:**
+- Roundup posts ("best free tools for X")
+- Resource pages
+- Industry publications
+- Blogs writing about the problem
+
+### Technical SEO
+
+- Fast load time critical
+- Mobile-friendly essential
+- Crawlable content (not just JS app)
+- Proper meta tags
+- Schema markup if applicable
+
+---
+
+## Lead Capture Strategy
+
+### When to Gate
+
+**Fully gated (email required to use):**
+- High-value, unique tools
+- Personalized reports
+- Risk: Lower usage
+
+**Partially gated (email for full results):**
+- Show preview, gate details
+- Better balance
+- Most common pattern
+
+**Ungated with optional capture:**
+- Tool is free to use
+- Email to save/share results
+- Highest usage, lower capture
+
+**Ungated entirely:**
+- Pure SEO/brand play
+- No direct leads
+- Maximum reach
+
+### Lead Capture Best Practices
+
+- Value exchange clear: "Get your full report"
+- Minimal friction: Email only
+- Show preview of what they'll get
+- Optional: Segment by asking one qualifying question
+
+### Post-Capture
+
+- Immediate email with results/link
+- Nurture sequence relevant to tool topic
+- Clear path to main product
+- Don't spam—provide value
+
+---
+
+## Build vs. Buy vs. Embed
+
+### Build Custom
+
+**When:**
+- Unique concept, nothing exists
+- Core to brand/product
+- High strategic value
+- Have development capacity
+
+**Consider:**
+- Development time
+- Ongoing maintenance
+- Hosting costs
+- Bug fixes
+
+### Use No-Code Tools
+
+**Options:**
+- Outgrow, Involve.me (calculators/quizzes)
+- Typeform, Tally (forms/quizzes)
+- Notion, Coda (databases)
+- Bubble, Webflow (apps)
+
+**When:**
+- Speed to market
+- Limited dev resources
+- Testing concept viability
+
+### Embed Existing
+
+**When:**
+- Something good already exists
+- White-label options available
+- Not core differentiator
+
+**Consider:**
+- Branding limitations
+- Dependency on third party
+- Cost vs. build
+
+---
+
+## MVP Scope
+
+### Minimum Viable Tool
+
+1. **Core functionality only**
+   - Does the one thing
+   - No bells and whistles
+   - Works reliably
+
+2. **Essential UX**
+   - Clear input
+   - Obvious output
+   - Mobile works
+
+3. **Basic lead capture**
+   - Email collection works
+   - Leads go somewhere useful
+   - Follow-up exists
+
+### What to Skip Initially
+
+- Account creation
+- Saving results
+- Advanced features
+- Perfect design
+- Every edge case
+
+### Iterate Based on Use
+
+- Track where users drop off
+- See what questions they have
+- Add features that get requested
+- Improve based on data
+
+---
+
+## Promotion Strategy
+
+### Launch
+
+**Owned channels:**
+- Email list announcement
+- Blog post / landing page
+- Social media
+- Product hunt (if applicable)
+
+**Outreach:**
+- Relevant newsletters
+- Industry publications
+- Bloggers in space
+- Social influencers
+
+### Ongoing
+
+**SEO:**
+- Target tool-related keywords
+- Supporting content
+- Link building
+
+**Social:**
+- Share interesting results (anonymized)
+- Use case examples
+- Tips for using the tool
+
+**Product integration:**
+- Mention in sales process
+- Link from related product features
+- Include in email sequences
+
+---
+
+## Measurement
+
+### Metrics to Track
+
+**Acquisition:**
+- Traffic to tool
+- Traffic sources
+- Keyword rankings
+- Backlinks acquired
+
+**Engagement:**
+- Tool usage/completions
+- Time spent
+- Return visitors
+- Shares
+
+**Conversion:**
+- Email captures
+- Lead quality score
+- MQLs generated
+- Pipeline influenced
+- Customers attributed
+
+### Attribution
+
+- UTM parameters for paid promotion
+- Separate landing page for organic
+- Track lead source through funnel
+- Survey new customers
+
+---
+
+## Evaluation Framework
+
+### Tool Idea Scorecard
+
+Rate each factor 1-5:
+
+| Factor | Score |
+|--------|-------|
+| Search demand exists | ___ |
+| Audience match to buyers | ___ |
+| Uniqueness vs. existing tools | ___ |
+| Natural path to product | ___ |
+| Build feasibility | ___ |
+| Maintenance burden (inverse) | ___ |
+| Link-building potential | ___ |
+| Share-worthiness | ___ |
+
+**25+**: Strong candidate
+**15-24**: Promising, needs refinement
+**<15**: Reconsider or scope differently
+
+### ROI Projection
+
+```
+Estimated monthly leads: [X]
+Lead-to-customer rate: [Y%]
+Average customer value: [$Z]
+
+Monthly value: X × Y% × $Z = $___
+
+Build cost: $___
+Monthly maintenance: $___
+
+Payback period: Build cost / (Monthly value - Monthly maintenance)
+```
+
+---
+
+## Output Format
+
+### Tool Strategy Document
+
+```
+# Free Tool Strategy: [Tool Name]
+
+## Concept
+[What it does in one paragraph]
+
+## Target Audience
+[Who uses it, what problem it solves]
+
+## Lead Generation Fit
+[How this connects to your product/sales]
+
+## SEO Opportunity
+- Target keywords: [list]
+- Search volume: [estimate]
+- Competition: [assessment]
+
+## Build Approach
+- Custom / No-code / Embed
+- MVP scope: [core features]
+- Estimated effort: [time/cost]
+
+## Lead Capture Strategy
+- Gating approach: [Full/Partial/Ungated]
+- Capture mechanism: [description]
+- Follow-up sequence: [outline]
+
+## Success Metrics
+- [Metric 1]: [Target]
+- [Metric 2]: [Target]
+
+## Promotion Plan
+- Launch: [channels]
+- Ongoing: [strategy]
+
+## Timeline
+- Phase 1: [scope] - [timeframe]
+- Phase 2: [scope] - [timeframe]
+```
+
+### Implementation Spec
+If moving forward with build
+
+### Promotion Plan
+Detailed launch and ongoing strategy
+
+---
+
+## Example Tool Concepts by Business Type
+
+### SaaS Product
+- Product ROI calculator
+- Competitor comparison tool
+- Readiness assessment quiz
+- Template library for use case
+
+### Agency/Services
+- Industry benchmark tool
+- Project scoping calculator
+- Portfolio review tool
+- Cost estimator
+
+### E-commerce
+- Product finder quiz
+- Comparison tool
+- Size/fit calculator
+- Savings calculator
+
+### Developer Tools
+- Code snippet library
+- Testing/preview tool
+- Documentation generator
+- Interactive tutorials
+
+### Finance
+- Financial calculators
+- Investment comparison
+- Budget planner
+- Tax estimator
+
+---
+
+## Questions to Ask
+
+If you need more context:
+1. What's your core product/service?
+2. What problems does your audience commonly face?
+3. What existing tools do they use for workarounds?
+4. How do you currently generate leads?
+5. What technical resources are available?
+6. What's the timeline and budget?
+
+---
+
+## Related Skills
+
+- **page-cro**: For optimizing the tool's landing page
+- **seo-audit**: For SEO-optimizing the tool
+- **analytics-tracking**: For measuring tool usage
+- **email-sequence**: For nurturing leads from the tool
+- **programmatic-seo**: For building tool-based pages at scale