<< All versions

Skill v1.0.1

currentAutomated scan100/100
tekkiiiii/the-agency/tech-stack

+2 new

──Details
PublishedNovember 17, 2026 at 01:16 PM
Content Hashsha256:b6515465c558ace4...
Git SHA36b8ed35080d
Bump Typepatch
Compare with v1.0.0
──Files
Files (1 file, 1.8 KB)
SKILL.md1.8 KBactive
SKILL.md · 49 lines · 1.8 KB

name: tech-stack description: "Use on \"what tech should I use\", \"which framework\", \"should I use X or Y\", \"help me pick a database\", \"recommend a stack\", or when starting a project or reviewing an existing stack. Clarifies team, scale, budget first; returns recommendation, alternatives, trade-offs and migration path." metadata: version: "1.0.1"


Tech Stack Advisor Skill

Process

  1. Clarify requirements first — before recommending, ask about:
  • Team size and existing expertise
  • Scale expectations (users, data volume)
  • Budget constraints (open source vs paid)
  • Deployment environment (cloud, on-prem, edge)
  • Timeline and MVP vs long-term
  1. Structure recommendations using this format:
  • Recommended Stack with brief rationale
  • Alternatives Considered and why not chosen
  • Trade-offs honestly stated
  • Migration path if they're switching from something existing

Common Stack Patterns

Web App (Full Stack)

  • Modern: Next.js + TypeScript + PostgreSQL + Prisma + Vercel
  • Enterprise: Java Spring Boot / .NET + React + Oracle/MSSQL
  • Rapid MVP: Supabase + Next.js or Firebase + React

Mobile

  • Cross-platform: React Native or Flutter
  • Native performance critical: Swift (iOS), Kotlin (Android)

Data / AI

  • Python stack: FastAPI + SQLAlchemy + Pandas/Polars + PostgreSQL
  • ML serving: FastAPI + PyTorch/TensorFlow + Redis cache

Microservices

  • Node.js or Go for high-throughput services
  • Kafka or RabbitMQ for event streaming
  • Docker + Kubernetes for orchestration

Principles

  • Prefer boring, proven technology for core infrastructure
  • Match stack to team's existing knowledge when possible
  • Avoid over-engineering for early-stage projects
  • Always consider operational complexity, not just development speed
← v1.0.0All versions