With an AI-agent-supported code editor, setting rules or coding standards that the agent must follow while programming itself is necessary. Additionally, defining project-specific rules is crucial to ensure that the agent’s output aligns with the developer’s intentions.
Traditional PRDs (Product Requirement Documents) are also an essential part of these rules.
For my project, which will use Next.js for the frontend, I first established Project Rules and then skipped the Cursor-specific rules—Rules for AI.
For the Project Rules, I intentionally used the Chat feature in Cursor. Since I have a paid account, ChatGPT-4o-mini is available without limitations. I simply fed it the Next.js documentation (which I believe is already included as a default dev doc reference in Cursor) and provided the following prompt:
“Based on the reference, create a Cursor rule as a coding standard.”
This rule will be referenced from the beginning of development to the end.
Secondly, I established a PRD Rule. The PRD file currently contains example content, but as I continue planning the application, I will add all necessary requirements—from the product’s goals to development specifications, acceptance criteria, documentation, UX requirements, and UI styles.
This example PRD provides a comprehensive overview of the user authentication system’s requirements, ensuring that all stakeholders have a clear understanding of the project’s goals and deliverables. Adjust the content as necessary to fit your specific project needs.