10x-tech-stack-selector

Recommends a starter and tech stack from a PRD using a curated registry and quality gates.

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/michaail/hybrid-logs-analyzer --skill 10x-tech-stack-selector-michaail
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 10x-tech-stack-selector
Source: https://github.com/michaail/hybrid-logs-analyzer/tree/main/.cursor/skills/10x-tech-stack-selector
Command: npx skills add https://github.com/michaail/hybrid-logs-analyzer --skill 10x-tech-stack-selector-michaail

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Choosing a technology stack for a greenfield project is slow and error-prone when done ad hoc. This Skill turns a written PRD into a concrete starter recommendation and a machine-readable hand-off file, so the project scaffolding step can proceed without re-litigating stack decisions. ## Core Features & Use Cases - PRD-driven recommendation: Reads context/foundation/prd.md frontmatter (product_type, target_scale, timeline_budget) and feature requirements as decision priors, refusing to run without the file on disk. - Two decision paths: A standard path that short-circuits to a vetted recommended default per (product_type, language_family) cell, and a custom path that walks a residual interview (features, team profile, preferences, deployment, CI/CD, framework variant, self-check). - Quality-gated registry: Reasons over a curated starter registry spanning JS, Python, Ruby, Java, Go, Rust, PHP, .NET, and Dart, applying four agent-friendly gates (typed, convention-based, popular in training data, well-documented) with Socratic challenges when a user preference fails a gate. - Use Case: After writing a PRD for a solo SaaS MVP, invoke the skill to get a recommended starter (e.g., an Astro + Supabase + Cloudflare stack), confirm deployment and CI choices, and produce context/foundation/tech-stack.md for the bootstrapper to scaffold. ## Quick Start Ask the assistant to pick a tech stack for the project based on the PRD at context/foundation/prd.md.

Frequently Asked Questions about 10x-tech-stack-selector

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

FAQPage Schema
How do I choose a tech stack for a new project from a PRD?

Invoke the skill after writing a PRD at context/foundation/prd.md. It reads the PRD frontmatter for product type, scale, and timeline, then either recommends a vetted default starter for your product type and language family or walks a short interview to design a custom stack.

What starters and frameworks does the registry cover?

The registry covers JavaScript/TypeScript (Next.js, Astro, T3, Nuxt, SvelteKit, Hono, NestJS, Expo), Python (Django, FastAPI), Ruby (Rails), Java (Spring Boot), PHP (Laravel), Go, Rust (Axum, Tauri), .NET, and Dart (Flutter), plus monorepo tools like Turborepo and Nx.

Can I use the skill without a PRD file?

No. The skill requires a PRD file on disk at context/foundation/prd.md (or a path passed as an argument). If the file is missing, it stops and redirects you to run the shape and PRD skills first; conversation context is not accepted as a substitute.

What happens if my preferred framework fails the quality gates?

The skill surfaces a Socratic challenge naming the failed criteria (typed, convention-based, popular in training data, well-documented) and the strongest passing alternative. You can still proceed with your pick; the hand-off records quality_override: true so the bootstrapper adds compensating conventions to the project's instruction files.

What does the tech-stack.md hand-off file contain?

It contains frontmatter with the chosen starter_id, package_manager, project_name, and hints (language family, team size, deployment target, CI provider and flow, bootstrapper confidence, path taken, feature flags), plus one short paragraph explaining why the stack was chosen.

When should I not use this stack selection skill?

Skip it when working mid-implementation on an existing codebase, such as adding a library or replacing a single dependency. It is designed for greenfield stack selection after a PRD exists, not for incremental changes to established projects.