Topic: Prompt Engineering Essentials
Create a prompt.
I want the AI to use this documentation format:

### **Database Description**
   - **Clear Overview**: Start with a concise overview of the database, highlighting its purpose and key components as per STEP 2.
   - **Assignment Alignment**: Explicitly state how each table and field aligns with the assignment's requirements.

### **Assumptions and Additions**
   - **Explicit Assumptions**: Document any assumptions made while designing the database, such as data types, field lengths, or optional fields.
   - **Justification for Additions**: Explain the rationale behind any additional fields or tables introduced that go beyond the assignment's specifications.

### **Reaction Policies**
   - **Policy Discussion**: Detail the reaction policies used in the database, like CASCADE on delete/update, and explain why they were chosen.

### **Table Descriptions and Data Types**
   - **Detailed Table Descriptions**: For each table, provide a detailed description including the purpose, fields, and data types.
   - **Data Type Rationale**: Explain the choice of data types for each field, aligning with the assignment's emphasis on appropriate data types.

### **Entity-Relationship (ER) Diagram**
   - **Comprehensive ER Diagram**: Include a detailed ER diagram, showcasing the relationships between tables and highlighting primary and foreign keys.
   - **Labeling and Legends**: Ensure the ER diagram is well-labeled and includes a legend for symbols used.

### **Stored Procedures Documentation**
   - **Insert Procedures**: Clearly document each stored procedure for inserting data into the tables, adhering to STEP 3.
   - **Query Procedures**: Document each query procedure, ensuring they are named as per the format specified in STEP 4.

I want them to use this strategy combined with the assignment guidelines (given in the next message). 
I will provide parts of the assignment code piece by piece.
Ensure every part of the assignment guidelines are assessed and then compare it against the documentation and the code. Then document it in detail. Do not just describe it. Ensure reasons are given for why things were chosen.
For parts of the document strategy that are not relevant for the current piece of code, leave as is and ignore. Update the documentation and return the new documentation. You will then use this for your next documentation, so that we are continuosly working on and changing the documentation until it is complete.


Optimise and clarify this prompt for use with AI's.