AI Prompts for Resolving Conflicting API Routes

Please provide a comprehensive list of all currently existing API endpoints and page routes in the project. For each entry, include the method (GET, POST, PUT, DELETE, etc.) and the corresponding path. Additionally, categorize the routes based on their functionality, such as user authentication, data retrieval, and administrative tasks, to give a clearer overview of the project's structure. Format the output in a table for easy reference.

Please provide a detailed list of the new API endpoints or page routes that have been generated recently. For each endpoint or route, include the HTTP methods used (such as GET, POST, PUT, DELETE) and the specific paths associated with them. Additionally, describe the purpose of each endpoint or route and any relevant parameters or data structures that are required. Format this information in a clear, organized manner, so it can be easily referenced for future development.

Please compare the newly generated routes with the existing routes in the system. Identify any duplicates or conflicts that may arise between them. For each conflict found, provide detailed information including the specific routes that are in conflict, the nature of the duplication, and any potential implications for routing efficiency. Format your response in a clear and organized manner, listing each conflict separately with relevant details.

Please review the following routing configuration file: [PASTE CONTENT]. Identify and highlight any inconsistencies or potential conflicts with the new routes that have been introduced. Provide a detailed analysis of the issues found, including the specific lines where conflicts occur, and suggest possible resolutions or adjustments to ensure smooth routing. Additionally, summarize the overall effectiveness of the current configuration in relation to the new routes.

Analyze the usage of the conflicting routes in the application. Identify each route and assess its importance to the overall functionality of the application. Provide a detailed report that includes: a list of the conflicting routes, an explanation of how each route is used within the application, and recommendations on which routes should be prioritized or modified to enhance performance. Additionally, suggest potential solutions for resolving any conflicts that may arise from these routes.

Please help me rename the conflicting routes in my project to ensure each route is unique. Provide a list of alternative names for each conflicting route, making sure they adhere to the project's naming conventions. Include at least three suggestions for each route, and explain briefly how each suggestion aligns with the conventions. Additionally, format the output in a clear table with the original route names and the suggested alternatives.

Please analyze the current routing configuration for potential method conflicts. Identify any routes that are using the same HTTP method and suggest alternative methods that could be used to resolve these conflicts. For each conflicting route, provide a brief explanation of why the suggested method is appropriate and how it aligns with RESTful principles. Format your response as a list, including the original route, the conflicting method, and the recommended method.

Identify the conflicting routes in the current system and propose modifications to their paths to eliminate any overlaps. Ensure that the new paths maintain a logical structure and flow, preserving the overall integrity of the routing system. Provide a detailed explanation of each suggested change, including the reasoning behind it and any potential impacts on the overall routing efficiency. Format your response as a structured list, clearly indicating the original path and the proposed modification for each conflicting route.

Please update the routing configuration to reflect the resolved routes for the project. Ensure that all changes adhere to the established project standards, including naming conventions and structure. Provide a summary of the modifications made, highlighting any routes that were added, removed, or altered. Additionally, include a brief explanation of how these changes improve the overall functionality and performance of the routing system.

Please test the modified routes to ensure they function correctly. Confirm that there are no conflicts with existing routes by checking for overlaps or discrepancies in the routing paths. Provide a detailed report on any issues found, including specific route identifiers and descriptions of the conflicts. Additionally, suggest potential solutions for any identified problems to ensure smooth operation.

Please conduct a thorough check to confirm that there are no conflicting routes in the current system. Summarize the findings in a clear report, detailing any conflicts that were found, their locations, and any actions taken to resolve them. If no conflicts are present, provide a statement confirming that all routes are clear. Include any recommendations for future monitoring or adjustments to prevent similar issues.

Please validate the functionality of all routes in the system, including both new and existing ones. For each route, provide a detailed report on its performance, noting any issues or errors encountered during testing. Include information on the expected behavior versus the actual behavior, and categorize the issues by severity (critical, major, minor). Additionally, suggest potential fixes or improvements for any identified problems. Format your findings in a clear and organized manner, suitable for presentation to the development team.

Please verify the routing configuration file for consistency and accuracy. Identify and highlight any discrepancies or errors present in the file. Provide a detailed report that includes the specific sections where inconsistencies are found, along with suggestions for how to resolve each issue. Ensure that the final output is clear and easy to understand, so that necessary adjustments can be made promptly.

Please review the application logs for any errors related to routing. Summarize the findings by listing any relevant log entries that indicate issues, including the timestamp, error message, and any associated request details. Additionally, provide insights on the potential causes of these errors and suggest possible resolutions or next steps to address the routing issues identified in the logs.

Please verify that users can access all intended routes within the system. Create a detailed report that outlines any access problems detected, including the specific routes that are inaccessible and the nature of the issues encountered. Additionally, provide recommendations for resolving these access problems to ensure all users have the necessary permissions. Include any relevant user roles or permissions that may affect access to these routes in your findings.

Please draft a new rule for the CLAUDE.md documentation that establishes a clear naming convention for routes to prevent duplicates. The rule should include specific guidelines on how to format route names, such as using prefixes or suffixes to indicate the purpose or category of the route. Additionally, provide examples of both compliant and non-compliant route names to illustrate the convention. Ensure the rule is concise yet comprehensive enough for developers to easily understand and implement.

Create a comprehensive checklist for developing new routes that ensures there are no conflicts with existing routes. The checklist should include steps such as reviewing current route maps, analyzing potential overlaps, consulting with stakeholders, and verifying compliance with regulations. Additionally, include a section for documenting findings and decisions made during the route planning process. Format the checklist in a clear, organized manner, using bullet points for easy reference.

Create a route validation script that checks for conflicts whenever new routes are added to the system. The script should take a list of existing routes and a new route as inputs, then determine if the new route overlaps with any existing ones. Include logic to handle different types of routes, such as straight paths and curves, and ensure it returns a clear message indicating whether a conflict exists or not. Please provide the complete code and explain how to integrate this script into an existing routing system.

Please create a rule for documenting all new routes in CLAUDE.md. The rule should specify that every new route must include a description of its purpose, parameters, and any potential conflicts with existing routes. Additionally, provide the exact text to be added to CLAUDE.md, ensuring it is clear and concise. Format the rule in a way that is easy to understand and implement for future reference.

Please define a comprehensive process for reviewing new routes before implementation. The process should include the steps for route evaluation, criteria for approval or rejection, and the roles and responsibilities of team members involved in the review. Additionally, outline how feedback will be collected and incorporated into future route planning. Format this as a detailed document suitable for inclusion in CLAUDE.md, ensuring clarity and thoroughness in each section.