laravel:debugging-prompts

To write an effective AI debugging prompt for a Laravel error, structure your request by including the exact error message, stack trace, relevant code snippets, expected versus actual behavior, and attempted solutions.

When asking an AI to troubleshoot Laravel application issues, include full error details, relevant log entries, application state information, supporting evidence, and a clear articulation of the discrepancies between expected and actual behavior.

Your AI assistant gives generic solutions because the Laravel stack trace lacks complete context, which this skill resolves by structuring prompts to include database state, hypotheses, and documented attempted solutions to prevent redundant suggestions.

To format expected versus actual behavior in an AI prompt for code assistance, clearly articulate the discrepancy between what your Laravel application should be doing and what it is actually doing alongside the error logs.

This structured prompt approach for troubleshooting PHP applications outside of Laravel works effectively because structuring error messages, state information, and attempted solutions ensures any AI assistant receives complete context for accurate problem diagnosis.

The best way to document attempted solutions when generating an AI debugging prompt is to detail your prior efforts and hypotheses, which prevents the AI assistant from providing redundant suggestions and accelerates the resolution process.