product-view
Step out of code-language and describe a feature, bug, or plan from the perspective of whoever is on the other side of the screen — the customer, user, player, reader, student, or patient. Use when the user asks to "explain how X works", "walk me through Y", "translate this", "from the product perspective", "as a user flow", "what does this look like to the user", "from the customer POV", "view on", "/product-view", or pastes a bug report, PR, or ticket and asks what's wrong in plain terms. Auto-activate when the user asks for the experience or impact of a user-facing feature — but not on explanations of internal components (a service, a queue, an algorithm), which stay in code-language. Do NOT use for pure algorithm, data-structure, performance, or internal-infrastructure questions (CI, build, deploy, container orchestration), code style review, or library selection on technical merits — those are inside-the-code questions where staying in code-language is correct.
