aio — Cursor Rules

The AI should adapt its questions based on the prompt, but here are some common areas to explore: • Problem/Goal: "What problem does this feature solve for the user?" or "What is the main goal we want to achieve with this feature?" • Target User: "Who is the primary user of this feature?" • Core Functionality: "Can you describe the key actions a user should be able to perform with this feature?" • User Stories: "Could you provide a few user stories? (e.g., As a [type of user], I want to [perform an action] so that [benefit].)" • Acceptance Criteria: "How will we know when this feature is successfully implemented? What are the key success criteria?" Scope/Boundaries: "Are there any specific things this feature should not* do (non-goals)?" • Data Requirements: "What kind of data does this feature need to display or manipulate?" • Design/UI: "Are there any existing design mockups or UI guidelines to follow?" or "Can you describe the desired look and feel?" • Edge Cases: "Are there any potential edge cases or error conditions we should consider?"

To guide an AI assistant in creating a detailed Product Requirements Document (PRD) in Markdown format, based on an initial user prompt. The PRD should be clear, actionable, and suitable for a junior developer to understand and implement the feature.

• Receive Initial Prompt: The user provides a brief description or request for a new feature or functionality. • Ask Clarifying Questions: Before writing the PRD, the AI must ask clarifying questions to gather sufficient detail. The goal is to understand the "what" and "why" of the feature, not necessarily the "how" (which the developer will figure out). Make sure to provide options in letter/number lists so I can respond easily with my selections. • Generate PRD: Based on the initial prompt and the user's answers to the clarifying questions, generate a PRD using the structure outlined below. • Save PRD: Save the generated document as prd-[feature-name].md inside the /tasks directory.

The generated PRD should include the following sections: • Introduction/Overview: Briefly describe the feature and the problem it solves. State the goal. • Goals: List the specific, measurable objectives for this feature. • User Stories: Detail the user narratives describing feature usage and benefits. • Functional Requirements: List the specific functionalities the feature must have. Use clear, concise language (e.g., "The system must allow users to upload a profile picture."). Number these requirements. • Non-Goals (Out of Scope): Clearly state what this feature will not include to manage scope. • Design Considerations (Optional): Link to mockups, describe UI/UX requirements, or mention relevant components/styles if applicable. • Technical Considerations (Optional): Mention any known technical constraints, dependencies, or suggestions (e.g., "Should integrate with the existing Auth module"). • Success Metrics: How will the success of this feature be measured? (e.g., "Increase user engagement by 10%", "Reduce support tickets related to X"). • Open Questions: List any remaining questions or areas needing further clarification.