identify-stack-slotslisted

Use this skill at the very start of a brand new coding project of any kind (CLI, web app, API service, library, mobile app, desktop app, server, etc.) to figure out the categories of technology decisions the project's stack is composed of. Trigger this whenever a user is kicking off a new project and needs to plan their stack, asks "what do I need to decide" / "help me set up the stack" / "I'm starting a new X project", or whenever you're about to scaffold a project and haven't yet established which decision categories apply. This produces a YAML list of stack "slots" (categories like "web framework", "test framework", "database"), NOT concrete tool picks. The YAML output feeds a later stage that fills each slot.
pricklywiggles/fractally-claude-marketplace · ★ 1 · Code & Development · score 62

Install: claude install-skill pricklywiggles/fractally-claude-marketplace

# Identify Stack Slots Help a user starting a brand new coding project identify the **stack slots** their project requires. A stack slot is a *category* of decision (e.g. "web framework", "test framework", "database"), not a concrete choice (e.g. "Next.js", "Jest", "Postgres"). The YAML output is consumed by a later stage that fills each slot, so do not recommend or select specific tools here. ## Objective Through conversation, determine the minimal, complete set of slots this project's stack is composed of. The set depends entirely on what the project is, so understand the project, research how its class of application is built, and derive the slots from both. ## Process Run discovery and research as interleaved passes, not separate phases. This matters because knowing the application class early lets you ask sharper questions and skip irrelevant ones. 1. **Identify the project type.** Ask what the user is building. Get just enough to determine project type and target platform(s). 2. **First research pass.** As soon as you know the application class, consult authoritative sources online for how it's built today. Let this shape your next questions. Knowing the application type reveals which ambiguities actually change the slot list. 3. **Ask sharper follow-ups.** Use what you learned to ask only slot-determining questions. Examples: Does it persist data? Does it expose an API or just consume one? UI, service, library, or CLI? Single platform or cross-platform? Browser,