tech-stack-advisor

Recommend a startup MVP technology stack and generate a STACK.md file.

1|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/ComputerConnection/z-combinator --skill tech-stack-advisor-computerconnection
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-stack-advisor
Source: https://github.com/ComputerConnection/z-combinator/tree/main/skills/tech-stack-advisor
Command: npx skills add https://github.com/ComputerConnection/z-combinator --skill tech-stack-advisor-computerconnection

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Recommends pragmatic technology stack by evaluating team expertise, time to market, hosting costs at different scales, hiring pool, and vendor lock-in, with brutal honesty about over-engineering and a phase-based guided interaction.

Core Features & Use Cases

  • Phase-based guidance that reads founder profile, MVP spec, and runway information to recommend a complete stack (frontend, backend, database, hosting, and third-party services).
  • Generates a STACK.md with clear trade-offs, cost projections, and a phased plan to avoid premature optimization.
  • Use case: A new startup seeking a boring, proven stack to hit a fast MVP timeline and minimize operational burden.

Quick Start

Ask the founder for team expertise and timeline, then select boring, proven technologies and lock them into STACK.md.

Frequently Asked Questions about tech-stack-advisor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the best way to choose a tech stack for an MVP?

A pragmatic tech stack for an MVP prioritizes team expertise, timeline, and hosting costs to select proven technologies. This approach minimizes operational burden and avoids premature optimization by locking in a simple, robust, and scalable stack.

How do I estimate hosting costs for different MVP scales?

Estimating hosting costs for an MVP requires projecting expenses at different scales across cloud hosting and third-party services. You evaluate these cost projections alongside team expertise and runway to ensure the selected stack remains affordable.

How do I avoid vendor lock-in when selecting MVP technologies?

Avoiding vendor lock-in when selecting MVP technologies requires evaluating your dependency on specific cloud hosting and third-party services. You balance this risk against timeline and team expertise to choose a stack that maintains future flexibility.

Can I use my current team expertise to speed up MVP development?

Yes, you can leverage current team expertise to speed up MVP development by aligning your frontend, backend, and database choices with existing skills. This reduces the learning curve, minimizes operational burden, and helps hit fast market timelines.

When should I not use over-engineered technologies for my startup MVP?

You should not use over-engineered technologies for a startup MVP when your goal is a fast time to market with minimal operational burden. Selecting boring, proven stacks prevents premature optimization and keeps realistic timelines intact.