CaPhe-Agentic-Stack

Determine intended product behavior before implementation, review, or debugging. Use when an agent must infer what a function, button, state transition, alert, backend feature, UI affordance, or operator workflow should do; when deciding between permanent dismissal, snooze, no-op, deletion, resolution, or recurrence; when a feature was built without an obvious UI path; or when the agent should infer from user role, existing app patterns, comparable software, and UX theory before asking the user.

Build read-only context for the current branch or pull request before follow-up work. Use when the user asks what a branch does, asks for PR context, inherits an unclear branch, or wants to continue work from an existing branch.

Review diffs and pull requests for reuse, composition, codebase consistency, unnecessary indirection, React or frontend state slop, and avoidable diff churn. Use when the user asks for PR review, refactor review, cleanup review, reuse review, code-quality review, or slop detection.

Create UX-first plans for product or interface changes by mapping current and desired flows before implementation anchors. Use when planning non-trivial UX, product behavior, screen flows, operator workflows, or UI architecture changes.