com um clique
laravel-prompt-structure
// Structure prompts for clarity—separate concerns, prioritize requests, specify acceptance criteria, and break work into testable increments
// Structure prompts for clarity—separate concerns, prioritize requests, specify acceptance criteria, and break work into testable increments
Request effective code reviews—specify focus areas, provide context, ask for architectural feedback, reference Laravel conventions
Create effective debugging prompts—include error messages, stack traces, expected vs actual behavior, logs, and attempted solutions
Provide comprehensive context in prompts—files, errors, Laravel version, dependencies, and monorepo details—for accurate AI responses
Refine AI-generated code through specific feedback—point out errors, identify gaps, show desired changes, reference style guides
Use Laravel-specific vocabulary—Eloquent patterns, Form Requests, API resources, jobs/queues—to get idiomatic framework code
Define clear constraints—performance, security, testing, architecture, dependencies—so AI generates code that meets your project standards
| name | laravel:prompt-structure |
| description | Structure prompts for clarity—separate concerns, prioritize requests, specify acceptance criteria, and break work into testable increments |
Well-structured prompts get complete, actionable responses. Poor structure leads to back-and-forth clarifications and incomplete solutions.
"Update the User model to add email verification and also create an API endpoint for password reset and add validation for the profile update form"
Break into focused requests:
Each request has one clear goal. Easier to review, test, and iterate.
"Need authentication, user dashboard, admin panel, and email notifications"
"Let's build authentication first:
Once auth works, we'll add the user dashboard, then admin features, then notifications."
Sequence matters. Build foundation first, then features that depend on it.
"Make the checkout process work"
"Implement checkout process with these requirements:
Clear criteria = clear implementation.
"Build a complete blog system with posts, comments, categories, tags, and search"
"Let's start with core post functionality:
Phase 1: Basic Posts
Phase 2: Categories
Phase 3: Comments (and so on...)
Each phase is testable and deliverable."
"This code is messy, clean it up"
"Refactor UserController@store:
Current problem:
Desired improvements:
Explain the problem and the desired state.
"Add social login"
"Add GitHub OAuth login:
Acceptance criteria:
Testable increments:
Break it down. Make it testable.
Structure your prompts:
Clear structure = clear results.