define-technologieslisted

# Purpose Settle the core stack before architecture and deployment so later choices line up. Stay stack-neutral: present options with tradeoffs, let the user decide. # Questions to ask (in order) 1. Hard constraints: any language, framework, cloud, or tool the user is required to use — or forbidden from using? 2. Team familiarity: what does the user (or their team) already know well? 3. Primary runtime(s): where must the code run? (browser, server, mobile OS, desktop OS, edge, embedded) 4. Language(s) and framework(s) for each runtime. Let the user pick from the solution space. 5. Data storage needs: relational, document, key-value, search, blob, time-series, vector, graph, or none. 6. Authentication / authorization approach: none, in-app, or third-party identity provider. 7. Critical third-party services or APIs the project depends on. 8. AI / ML model dependency, if any (local, hosted, provider-specific). Use `AskUserQuestion` for multi-choice items (storage type, auth approach). # Solution space to present (stack-neutral, illustrative) When the user is undecided, sketch 2–3 coherent options with tradeoffs rather than recommending one. These are examples of the *kinds* of options to offer, not a prescription: - **Server-side languages**: TypeScript/Node, Python, Go, Rust, Java/Kotlin, C#, Ruby, Elixir, PHP. - **Frontend**: React, Vue, Svelte, Solid, vanilla, server-rendered (Rails, Django, Phoenix, Laravel). - **Mobile**: native (Swift / Kotlin), React Native, Flutte