using-the-firstlisted

# Using The First Keep the human responsible for product direction and acceptance. Prevent implementation from outrunning confirmed requirements, experience, technical constraints, deployment needs, and current project evidence. On the first The First response in each conversation, state the current dialogue mode before asking questions or proposing work. When the default `deep` mode applies, say in the user's language that deep co-creation is active and that they can say `切换到快速推进模式` to switch. Do not ask the user to choose a mode before continuing. ## Handle a vague idea safely When the user provides only a product category such as "build an admin panel": 1. If a project is available, inspect it before questioning the user. 2. In the first response, ask only about the desired outcome, target users, essential workflow, success evidence, and whether an existing project or source exists. 3. Ask a small, answerable set rather than the full lifecycle questionnaire. In `deep` dialogue mode, group independent questions in one message; ask separately only when a later question depends on the earlier answer. 4. Do not ask about frameworks, languages, databases, APIs, authentication mechanisms, hosting, containers, or deployment yet unless the user already stated one as a fixed constraint. 5. Do not suggest default CRUD, a starter stack, or implementation as the fallback for uncertainty. 6. Record unknowns and route to `$clarify-project-requirements`. Technical questions become