From superpowers-laravel
Structures prompts for clarity by separating concerns, prioritizing requests, specifying acceptance criteria, and breaking work into testable increments. Useful for complex Laravel development tasks.
npx claudepluginhub jpcaparas/superpowers-laravel --plugin superpowers-laravelThis skill uses the workspace's default tool permissions.
Well-structured prompts get complete, actionable responses. Poor structure leads to back-and-forth clarifications and incomplete solutions.
Refines rough Laravel feature ideas into fully-formed designs via collaborative questioning, alternative exploration, and incremental validation before coding.
Guides interactive brainstorming for Laravel features and refactors, clarifying goals, domain, data models, APIs, side-effects, testing, and Sail environments.
Provides production-grade Laravel solutions with clean architecture, security best practices, performance optimizations, and idiomatic patterns for Laravel 10/11+. Use for features, refactoring, APIs, auth, services, DB interactions, and code reviews.
Share bugs, ideas, or general feedback.
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.