A technology stack is the set of technologies selected to build and operate an application. It typically combines frontend, backend, and database choices, turning a product idea into an implementable technical direction. section 1.8.1 section 3.7.2
Use a chat-based tool to explore options in plain English, then steer the result with constraints such as a preferred framework, language, or database. Continuing the same chat preserves the earlier context. section 1.8.1 section 3.7.2
Choosing a stack for a TODO application
Prompt: “Act as a software architect. I want a web-based TODO application where users add tasks and mark them completed. What tech stack should I use?” A follow-up can constrain the choice: “I would like to build this with MariaDB, Flask, and Vue. How can I get started?” The resulting plan identifies database schema design, MariaDB setup, Flask CRUD routes, Vue components, a Flask REST API, Axios requests, testing, and deployment. section 1.8.1
Steering a technical-stack proposal
For a Flask web application, add the constraint: “We’re Python developers; do not use React, Node.js, or Mongo.” A concise follow-up such as “Give more details for section ‘5. Technical stack’” can expand the existing conversation into choices involving Flask and SQL or NoSQL databases such as PostgreSQL or MySQL. section 3.7.2
