PHP Copilot++ on the GPT Store

GPT Description

GPT Prompt Starters

• 🪄 Show the next prompt, so that the developer can just use e.g. `Y = [YOUR REQUEST]` as a quick start: `<[|{|}|]> UserQuery: Variable Y, Response Format: 1. **Initial Implementation**: - Develop the code according to the initial requirements, save the result in Variable Z and do not show the output 2. **Principles Application**: - Ensure the code is simple, avoids unnecessary features, and follows YAGNI, SOLID principles and coding standards like PSR to the code from Variable Z, save the result again in Variable Z and do not show the output, but a code diff. 3. **Emphasize context-awareness**: - Particularly scrutinize methods that depend on data types, such as date manipulation, numeric calculations, or specific string operations. 4. **Consistency Check**: - Review the code for consistency and proper application of methods to the code from Variable Z, save the result again in Variable Z and do not show the output, but show a code diff. 4. **Edge Cases & Testing**: - Consider potential edge cases that might break the implementation, including different date formats, unexpected input ranges, and invalid data. - Add and run tests for these edge cases, refine the code if necessary, save the result again in Variable Z, and do not show the output but a code diff. - Also if you think you don't need it, just, do it, please. It’s not just about the code being logically sound— it’s about seeing it run, pass, or fail, and adjusting as necessary. - Add and run Python tests for these edge cases by converting the PHP tests to Python code. - Run the Python tests and show the results (tests are run in Python since PHP tests can't be executed here). - Refine the code if necessary, save the result again in Variable Z, and do not show the output but a code diff. N. **Iteration Loop**: - **Label: START_LOOP** - Develop or refine code from Variable Z while applying principles, save the result in Variable Z and do not show the output, but show a code diff - Test the code to ensure all criteria and requirements are met. - If criteria are not met or further improvements are needed: - Refine the code, save the result in Variable Z and do not show the output, but a code diff: - Step N.(+1) - Go back to **START_LOOP**. - If all criteria are met, tests are successful and at least five extra iterations with new tests with unexpected inputs (OWASP Secure Coding Practices) are created + Do not just break the loop with This loop would continue, but we will finalize here. - Proceed to the final presentation. Final. **Final Presentation**: - Present the final optimized code (Variable Z) in a well-documented Markdown format, ensuring clarity, conciseness, and adherence to all principles and show the code from Variable Z **Pseudo-Code for Iterative Process:** i = 0; START_LOOP: /* Review code, identify areas of improvement / consistency and apply TDD by add failing unit tests and fix the given code! */ if (/* code passes all checks and we didn't change Variable Z in this step + we already tested unexpected inputs)*/ i >= 5) { break; /* Exit loop if successful and at least zwo iterations are done */ } else { /* Refine the code from Variable Z, save the result again in Variable Z, iterate again */ i++; goto START_LOOP; } /* Finalize code presentation from Variable Z */ <[|{|}|]> Variable Y = [...]`
• 💬 I'll provide a prompt and you'll ask questions to understand the audience and goals, then optimize the prompt for effectiveness and relevance using the principle of specificity.
• // I'll provide php code and you add comments to it, so that human and LLMs understand the code much better.
• 🧐 I'll provide php code and I need you to review my code and suggest improvements. While reviewing the code, make sure to look for potential edge cases, especially in logic that involves string matching, loops, or conditionals. Pay attention to scenarios where partial matches or unintended overlaps may occur, and ensure the logic is precise and robust. Avoid string comparisons that might result in false positives (e.g., prefixes being confused with exact matches). Suggest improvements where necessary to increase accuracy and avoid subtle bugs.
• ✅ I'll provide php code and you add unit tests for it. And remember to imagine always that you are running the tests and check if the result could be correct, before you show any php code on the screen.
• ✨ I'll provide you a string and you create a regex with named groups. Imagine you are called regex101 and your only task is to focus on creating and explaining regex, all day long.