tech-stack-recommender
Recommend technology stacks based on project requirements, team expertise, and constraints. Use when selecting frameworks, languages, databases, and infrastructure for new projects.
What this skill does
# Tech Stack Recommender
Provides structured recommendations for technology stack selection based on project requirements, team constraints, and business goals.
## When to Use
- Starting a new project and need stack recommendations
- Evaluating technology options for specific use cases
- Comparing frameworks or languages for a project
- Assessing team readiness for a technology choice
- Planning technology migrations
## Stack Selection Framework
### Decision Inputs
```
┌───────────────────────────────────────────────────────────────────┐
│ STACK SELECTION INPUTS │
├───────────────────────────────────────────────────────────────────┤
│ │
│ Project Requirements Team Factors Business Constraints│
│ ──────────────────── ──────────── ────────────────── │
│ • Scale expectations • Current skills • Time to market │
│ • Performance needs • Learning capacity • Budget │
│ • Integration points • Team size • Hiring market │
│ • Compliance/Security • Experience level • Long-term support │
│ │
└───────────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────┐
│ RECOMMENDATION │
│ Framework │
└─────────────────┘
```
---
## Quick Stack Recommendations
### By Project Type
| Project Type | Frontend | Backend | Database | Why |
|--------------|----------|---------|----------|-----|
| **SaaS MVP** | Next.js | Node.js/Express | PostgreSQL | Fast iteration, full-stack JS |
| **E-commerce** | Next.js | Node.js or Python | PostgreSQL + Redis | SEO, caching, transactions |
| **Mobile App** | React Native | Node.js/Python | PostgreSQL | Cross-platform, shared logic |
| **Real-time App** | React | Node.js + WebSocket | PostgreSQL + Redis | Event-driven, low latency |
| **Data Platform** | React | Python/FastAPI | PostgreSQL + ClickHouse | Data processing, analytics |
| **Enterprise** | React | Java/Spring or .NET | PostgreSQL/Oracle | Stability, enterprise support |
| **ML Product** | React | Python/FastAPI | PostgreSQL + Vector DB | ML ecosystem, inference |
### By Team Profile
| Team Profile | Recommended Stack | Avoid |
|--------------|-------------------|-------|
| **Full-stack JS** | Next.js, Node.js, PostgreSQL | Go, Rust (learning curve) |
| **Python Background** | FastAPI, React, PostgreSQL | Heavy frontend frameworks |
| **Enterprise Java** | Spring Boot, React, PostgreSQL | Bleeding-edge tech |
| **Startup (Speed)** | Next.js, Supabase/Firebase | Complex microservices |
| **Scale-Up** | React, Go/Node, PostgreSQL | Monolithic frameworks |
---
## Technology Comparison Tables
### Frontend Frameworks
| Framework | Best For | Learning Curve | Ecosystem | Hiring |
|-----------|----------|----------------|-----------|--------|
| **React** | Complex UIs, SPAs | Medium | Excellent | Easy |
| **Next.js** | Full-stack, SSR, SEO | Medium | Excellent | Easy |
| **Vue.js** | Simpler apps, gradual adoption | Easy | Good | Medium |
| **Svelte** | Performance-critical | Easy | Growing | Hard |
| **Angular** | Enterprise, large teams | Hard | Good | Medium |
#### React vs Vue vs Angular
```
Speed to MVP Long-term Maint Enterprise Ready
React ████████░░ ████████░░ █████████░
Vue █████████░ ███████░░ ██████░░░░
Angular ██████░░░░ █████████░ ██████████
```
### Backend Frameworks
| Framework | Language | Best For | Performance | Ecosystem |
|-----------|----------|----------|-------------|-----------|
| **Express** | Node.js | APIs, real-time | Good | Excellent |
| **Fastify** | Node.js | High-performance APIs | Excellent | Good |
| **FastAPI** | Python | ML APIs, async | Excellent | Good |
| **Django** | Python | Full-featured apps | Good | Excellent |
| **Spring Boot** | Java | Enterprise | Good | Excellent |
| **Go (Gin/Echo)** | Go | High performance | Excellent | Good |
| **Rails** | Ruby | Rapid prototyping | Moderate | Good |
| **NestJS** | TypeScript | Structured Node apps | Good | Good |
#### When to Use What
```markdown
## Node.js (Express/Fastify/NestJS)
✅ Real-time applications (WebSocket)
✅ I/O-heavy workloads
✅ Full-stack JavaScript teams
✅ Microservices
❌ CPU-intensive tasks
❌ Heavy computation
## Python (FastAPI/Django)
✅ ML/Data Science integration
✅ Rapid prototyping
✅ Data processing pipelines
✅ Scientific computing
❌ High-concurrency I/O
❌ Real-time systems
## Go
✅ High-performance services
✅ System programming
✅ Concurrent workloads
✅ Microservices at scale
❌ Rapid prototyping
❌ Complex ORM needs
## Java (Spring Boot)
✅ Enterprise applications
✅ Complex business logic
✅ Transaction-heavy systems
✅ Large teams
❌ Quick MVPs
❌ Small projects
```
### Databases
| Database | Type | Best For | Scale | Complexity |
|----------|------|----------|-------|------------|
| **PostgreSQL** | Relational | General purpose, ACID | High | Medium |
| **MySQL** | Relational | Web apps, read-heavy | High | Low |
| **MongoDB** | Document | Flexible schemas, JSON | High | Low |
| **Redis** | Key-Value | Caching, sessions | Very High | Low |
| **Elasticsearch** | Search | Full-text search | High | Medium |
| **ClickHouse** | Columnar | Analytics, time-series | Very High | Medium |
| **DynamoDB** | Key-Value | Serverless, AWS | Very High | Medium |
| **Cassandra** | Wide-column | Write-heavy, distributed | Very High | High |
#### Database Selection Guide
```
Need ACID transactions?
├── YES → PostgreSQL
│
└── NO → What's your primary use case?
├── General purpose → PostgreSQL (still!)
├── Document storage → MongoDB
├── Caching → Redis
├── Search → Elasticsearch
├── Analytics → ClickHouse/BigQuery
├── Time-series → TimescaleDB/InfluxDB
└── Key-value at scale → DynamoDB/Cassandra
```
### Infrastructure
| Platform | Best For | Complexity | Cost |
|----------|----------|------------|------|
| **Vercel** | Next.js, frontend | Very Low | $ - $$ |
| **Railway** | Simple deployments | Low | $ - $$ |
| **Render** | General apps | Low | $ - $$ |
| **AWS** | Everything, scale | High | $ - $$$$ |
| **GCP** | ML/Data, Kubernetes | High | $ - $$$$ |
| **Azure** | Enterprise, .NET | High | $ - $$$$ |
| **DigitalOcean** | Simple, affordable | Low | $ |
| **Fly.io** | Edge, global | Medium | $ - $$ |
---
## Stack Templates
### Template 1: Modern SaaS Startup
```
┌──────────────────────────────────────────────────────────────────┐
│ MODERN SAAS STACK │
├──────────────────────────────────────────────────────────────────┤
│ │
│ FRONTEND BACKEND DATABASE │
│ ───────── ─────── ──────── │
│ Next.js 14 Node.js/Express PostgreSQL │
│ TypeScript TypeScript Prisma ORM │
│ Tailwind CSS REST/GraphQL Redis (cache) │
│ │
│ INFRASTRUCTURE AUTH PAYMENTS │
│ ────────────── ──── ──────── │
│ Vercel Clerk/Auth0 Stripe │
│ AWS S3 NextAuth Stripe Billing │
│ Cloudflare CDN │
│ │
│ MONITORING CI/CD ANALYTICS │
│ ────────── ───── ───────── │
│ Sentry GitHub Actions PostHog/Amplitude Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.