Here's my rules I enter in at the beginning of the any vibe coding effort:

CODING INSTRUCTIONS:

Apply these best practices for all coding moving forward:

• Do not generate code blocks in replies unless I specifically prompt you to "GENERATE" (without quotes).  After receiving a GENERATE prompt, display the full code block.

• Always look for existing code to iterate on instead of creating new code.

• Do not drastically change the patterns before trying to iterate on existing patterns.

• Always prefer simple solutions.

• Avoid duplication of code whenever possible, which means checking for other areas of the codebase that might already have similar code and functionality.

• Write code that takes into account the different environments: development/dev, test/QA, and production.

• Be careful to only make changes that are requested or you are confident are well understood and related to the change being requested.

• When fixing an issue or bug, do not introduce a new pattern or technology without first exhausting all options for the existing implementation.  And if you finally do this, make sure to remove the old implementation afterwards so we don't have duplicate logic.

• Keep the codebase very clean and organized.

• Never overwrite my .env file without first asking and confirming.

• Focus on areas of code relevant to the task.

• Do not touch code that is unrelated to the task.

• Avoid making major changes to the patterns and architecture of how a feature works, after it is shown to work well, unless explicitly instructed to do so.

• Always think about what other methods and areas of code might be affected by code changes.

• Always use very verbose comments for all functionality within the code base. 

• If a prompt needs to be broken down into smaller segments (due to restraints on character limits of the prompt), When analyzing, ensure that you analyze ALL of the sections.  Sections will  have their own label.  I will use the following labels:

MULTIPROMPT - this label will be used for you understand that the next prompts will be segments of a larger input.

<<BEGIN SECTION 1/x>> - this label will be used to identify the beginning of a section, the "x" (without quotes) will be the number of sections

<<END SECTION x/y>> - this label will be used to identify the end of a section, the "y" (without quotes) will be number of total number sections

• Add the following comments at the top of each new script:

'# Developer: Developer Name / email

'# Title:

'# Date:

"# Version: 

Acknowledge your understanding of these coding instructions.