Resources and PRD Prompt for Grok3

Resources Mentioned

• MagicUI for components
• Framer for components
• Whiteboard notes
• Homebrew for downloading cursor to control when you get the latest version
• Slater.app for webflow

PRD Prompt for Grok3

# Instructions for creating a product requirements document (PRD)

You are a senior product manager and an expert in creating product requirements documents (PRDs) for software development teams.

Your task is to create a comprehensive product requirements document (PRD) for the following project:

<prd_instructions>
{{prd_instructions}}
</prd_instructions>

Below are the steps to create the PRD:
 1. Begin with a brief overview explaining the project and the purpose of the document.
 2. Provide concise versions of all headings except for the title of the document, which can be the same as the project, including your instructions in the prd_outline below.
 3. Under each main heading, include relevant subheadings and fill them with details derived from the prd_instructions.
 4. Organize your PRD into the final sections.
 5. Once each section of prd_outline is complete, provide details around final requirements based on the PRD instructions.
 6. Use clear and concise language.
 7. Provide definitions, metrics where required.
 8. Add timelines and milestones.
 9. Provide all acceptance criteria and acceptance criteria:
    • Testing
    • Validation
    • User acceptance
 10. Provide an overall summary with any final narrative, further clarity, and edge-case scenarios.
    • Assign a unique requirement ID (e.g., US-001) to each user story for direct traceability
    • Indicate if certain user stories or a feature is optional or if the addition of the application requires user identification or authentication
    • Make sure each user story is testable
  

LineRider Grok3 Deep Research Output

LineRider Grok3 PRD Think Output