10x-tech-stack-selector

Recommends a starter and tech stack from a PRD via a curated registry.

Updated May 24, 2026
One-click install
npx skills add https://github.com/DevMachaj/Projekt-certyfikacyjny --skill 10x-tech-stack-selector-devmachaj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 10x-tech-stack-selector
Source: https://github.com/DevMachaj/Projekt-certyfikacyjny/tree/main/.claude/skills/10x-tech-stack-selector
Command: npx skills add https://github.com/DevMachaj/Projekt-certyfikacyjny --skill 10x-tech-stack-selector-devmachaj

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 from memory or generic comparisons. This Skill turns a written PRD into a concrete starter recommendation by reasoning over a curated, language-aware starter registry, then writes a machine-readable hand-off file that a downstream bootstrapper consumes to scaffold the project. ## 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-path interview: Offers a standard path that accepts a vetted recommended default for the (product_type, language_family) cell, or a custom path that walks a full residual interview covering features, team profile, preferences, deployment, CI/CD, and a five-point self-check. - Quality-gated registry: Filters 25+ starter cards across JS, Python, Ruby, Java, Go, Rust, PHP, .NET, and Dart using four agent-friendly criteria (typed, convention-based, popular in training data, well-documented), with Socratic challenges when a user preference fails a gate. - Use Case: After finishing 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 receive a context/foundation/tech-stack.md hand-off ready for scaffolding. ## 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's product type, scale, and timeline as priors, then either offers a vetted recommended starter for your product type and language family or walks a full interview to design a custom stack.

What starter frameworks does the tech stack selector support?

The registry covers 25+ starters across nine language families, including Next.js, Astro, T3, Hono, Fastify, Django, FastAPI, Rails, Spring Boot, Laravel, Go, Axum, Tauri, Flutter, Expo, and .NET. Each card carries quality-gate booleans, deployment defaults, and a bootstrapper confidence level.

Can I use the tech stack selector 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) and refuses to run otherwise. It redirects you to the upstream shape and PRD skills first, and does not accept conversation history 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, or well-documented) and proposes the strongest passing alternative. You can still proceed with your pick; the hand-off records quality_override: true so the bootstrapper adds compensating conventions.

What is the difference between the standard and custom path?

The standard path accepts the registry's recommended default for your product type and language family, asking only about deployment, CI/CD, and project name. The custom path runs the full interview: feature audit, team profile, tech preferences, framework variant selection, and a five-point self-check before writing the hand-off.

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

It contains YAML frontmatter with the chosen starter_id, package manager, kebab-case project name, and hints covering language family, team size, deployment target, CI provider, bootstrapper confidence, path taken, and feature flags, plus one short paragraph explaining the rationale.