Laravel Eloquent query optimization and relationship management patterns with N+1 prevention.
Works with
Eager load relationships with with() and use withCount() for efficient aggregations instead of triggering additional queries in loops
Select only needed columns at query time and define return types on relationship methods for better IDE support and clarity
Use query scopes to encapsulate reusable filtering logic and leverage database-level operations ( update() , increment() ) instead of lo
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versioneloquent-best-practicesExecute the skills CLI command in your project's root directory to begin installation:
Fetches eloquent-best-practices from iserter/laravel-claude-agents and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate eloquent-best-practices. Access via /eloquent-best-practices in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
31
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
31
stars
// ❌ N+1 Query Problem
$posts = Post::all();
foreach ($posts as $post) {
echo $post->user->name; // N additional queries
}
// ✅ Eager Loading
$posts = Post::with('user')->get();
foreach ($posts as $post) {
echo $post->user->name; // No additional queries
}
// ❌ Fetches all columns
$users = User::all();
// ✅ Only needed columns
$users = User::select(['id', 'name', 'email'])->get();
// ✅ With relationships
$posts = Post::with(['user:id,name'])->select(['id', 'title', 'user_id'])->get();
// ✅ Define reusable query logic
class Post extends Model
{
public function scopePublished($query)
{
return $query->where('status', 'published')
->whereNotNull('published_at');
}
public function scopePopular($query, $threshold = 100)
{
return $query->where('views', '>', $threshold);
}
}
// Usage
$posts = Post::published()->popular()->get();
use Illuminate\Database\Eloquent\Relations\BelongsTo;
use Illuminate\Database\Eloquent\Relations\HasMany;
class Post extends Model
{
public function user(): BelongsTo
{
return $this->belongsTo(User::class);
}
public function comments(): HasMany
{
return $this->hasMany(Comment::class);
}
}
// ❌ Triggers additional queries
foreach ($posts as $post) {
echo $post->comments()->count();
}
// ✅ Load counts efficiently
$posts = Post::withCount('comments')->get();
foreach ($posts as $post) {
echo $post->comments_count;
}
class Post extends Model
{
// ✅ Whitelist fillable attributes
protected $fillable = ['title', 'content', 'status'];
// Or blacklist guarded attributes
protected $guarded = ['id', 'user_id'];
// ❌ Never do this
// protected $guarded = [];
}
class Post extends Model
{
protected $casts = [
'published_at' => 'datetime',
'metadata' => 'array',
'is_featured' => 'boolean',
'views' => 'integer',
];
}
// ✅ Process in chunks to save memory
Post::chunk(200, function ($posts) {
foreach ($posts as $post) {
// Process each post
}
});
// ✅ Or use lazy collections
Post::lazy()->each(function ($post) {
// Process one at a time
});
// ❌ Slow - loads into memory first
$posts = Post::where('status', 'draft')->get();
foreach ($posts as $post) {
$post->update(['status' => 'archived']);
}
// ✅ Fast - single query
Post::where('status', 'draft')->update(['status' => 'archived']);
✓Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
✓Save 3-5 hours/week on communication overhead
Implementation Guide
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Steps
- 1Install product management skill
- 2Start with user story generation for known feature
- 3Progress to competitive analysis: research 2-3 competitors
- 4Use for roadmap prioritization: apply RICE/ICE scoring
- 5Draft stakeholder communications and refine based on feedback
- 6Build template library for recurring PM tasks
- 7Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Related Skills
nestjs-best-practices
76kadajett/agent-nestjs-skills
Productivity2 shared tagstypescript-best-practices
164jwynia/agent-skills
Backend2 shared tagsreact-vite-best-practices
58asyrafhussin/agent-skills
Frontend2 shared tagsgrill-me
704mattpocock/skills
Productivitysame categorypremortem
218parcadei/continuous-claude-v3
Productivitysame categorydeslop
164cursor/plugins
Productivitysame categoryReviews
4.7★★★★★55 reviews- NNoah Harris★★★★★Dec 28, 2024
Keeps context tight: eloquent-best-practices is the kind of skill you can hand to a new teammate without a long onboarding doc.
- SSoo Ndlovu★★★★★Dec 24, 2024
eloquent-best-practices is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- LLiam Mensah★★★★★Dec 8, 2024
I recommend eloquent-best-practices for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- AAarav Dixit★★★★★Dec 8, 2024
Useful defaults in eloquent-best-practices — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- CChaitanya Patil★★★★★Dec 4, 2024
We added eloquent-best-practices from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- LLiam Martinez★★★★★Dec 4, 2024
eloquent-best-practices fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- NNoah Srinivasan★★★★★Dec 4, 2024
eloquent-best-practices reduced setup friction for our internal harness; good balance of opinion and flexibility.
- HHarper Brown★★★★★Nov 27, 2024
We added eloquent-best-practices from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- PPiyush G★★★★★Nov 23, 2024
Useful defaults in eloquent-best-practices — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- NNoah Huang★★★★★Nov 23, 2024
eloquent-best-practices is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 55
1 / 6Discussion
Comments — not star reviews- No comments yet — start the thread.