Use API Resources with pagination and conditional fields; keep response shapes stable and cache-friendly
meistro57/chat_bridge
SkillsMP has collected 16 skills from meistro57/chat_bridge. Open a skill to review its source and details.
- Latest recorded source activity
- SkillsMP catalog refreshed
- skills collected
- 16
- GitHub stars
- 1
- GitHub forks
- 0
Skills in this repository
Showing 16 of 16 collected skills.
Compose UIs with Blade components, slots, and layouts; keep templates pure and testable
Request effective code reviews—specify focus areas, provide context, ask for architectural feedback, reference Laravel conventions
Practical daily checklist for Laravel projects; bring services up, run migrations, queues, quality gates, and tests
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
Define clear relationships and load data efficiently; prevent N+1, use constraints, counts/sums, and pivot syncing safely
Move validation and authorization into Form Requests; use rule objects, custom messages, and nested data handling to keep controllers slim
Use Laravel-specific vocabulary—Eloquent patterns, Form Requests, API resources, jobs/queues—to get idiomatic framework code
Safe database change patterns; when to modify vs add migrations; always pair models with migrations and factories; seeding guidance
Use framework caches and value/query caching to reduce work; add tags, locks, and explicit invalidation strategies for correctness
Enforce access via Policies and Gates; use authorize() and authorizeResource() to standardize controller protections
Operate and verify queues with or without Horizon; safe worker flags, failure handling, and test strategies
Define clear constraints—performance, security, testing, architecture, dependencies—so AI generates code that meets your project standards
Schedule tasks with safety; use withoutOverlapping, onOneServer, and visibility settings for reliable cron execution
Wrap multi-write operations in transactions; use dispatchAfterCommit and idempotency patterns to ensure consistency