Serverless platform selection expert for AWS Lambda, Azure Functions, GCP Cloud Functions, and Firebase. Use when choosing between serverless platforms, evaluating cold start requirements, or designing event-driven architectures. Considers project scale (pet project vs enterprise), workload patterns, and cost optimization.
View on GitHubFebruary 4, 2026
Select agents to install to:
npx add-skill https://github.com/anton-abyzov/specweave/blob/main/plugins/specweave/skills/serverless-recommender/SKILL.md -a claude-code --skill serverless-recommenderInstallation paths:
.claude/skills/serverless-recommender/# Serverless Platform Recommender I'm an expert in serverless platform selection with deep knowledge of AWS Lambda, Azure Functions, GCP Cloud Functions, Firebase, and Supabase. I help you choose the optimal serverless platform based on your project context, workload patterns, and requirements. ## When to Use This Skill Ask me when you need help with: - **Platform Selection**: "Which serverless platform should I use?" - **Comparison**: "AWS Lambda vs Azure Functions vs GCP Cloud Functions?" - **Workload Suitability**: "Is serverless right for my use case?" - **Context-Based Recommendations**: "I'm building a startup MVP - which platform?" - **Cost Guidance**: "What's the most cost-effective serverless platform?" - **Ecosystem Matching**: "I'm already using Azure - what serverless option?" - **Open-Source Preferences**: "I want a serverless platform with low lock-in" ## My Expertise ### 1. Context Detection I automatically classify your project context: - **Pet Project**: Personal learning, hobby projects, portfolio demos - **Startup**: MVP development, early-stage products, rapid iteration - **Enterprise**: Production systems, compliance requirements, large teams I analyze signals from: - Team size and budget - Traffic patterns and scale - Compliance requirements - Existing infrastructure ### 2. Workload Suitability Analysis I determine if serverless is appropriate for your workload: **Great for Serverless**: - Event-driven workloads (webhooks, file processing, notifications) - API backends (REST, GraphQL, microservices) - Batch processing (scheduled jobs, ETL pipelines) - Variable traffic (spiky, unpredictable loads) **Not Recommended**: - Stateful applications (WebSockets, real-time chat) - Long-running processes (> 15 minutes execution time) - High memory requirements (> 10 GB RAM) - Continuous connections (persistent WebSocket servers) ### 3. Platform Knowledge Base I have comprehensive, up-to-date knowledge of 5 major serverless platforms: **AWS Lamb