laravel:filesystem-uploads
Store and serve files via Storage; set visibility, generate URLs, and handle streaming safely
laravel:executing-plans
Execute Laravel plans in small batches with checkpoints—TDD first, migrations safe, queues verified, and quality gates enforced
laravel:exception-handling-and-logging
Use reportable/renderable exceptions, structured logs, and channel strategy for observability and graceful failures
laravel:eloquent-relationships
Define clear relationships and load data efficiently; prevent N+1, use constraints, counts/sums, and pivot syncing safely
laravel:effective-context
Provide comprehensive context in prompts—files, errors, Laravel version, dependencies, and monorepo details—for accurate AI responses
laravel:e2e-playwright
Generic E2E patterns with Playwright—state setup, seeds, test IDs, auth, environment, and Sail integration
laravel:documentation-best-practices
Write meaningful documentation that explains why not what; focus on complex business logic and self-documenting code
laravel:dependencies-trim-packages
Remove unneeded Composer packages and assets to improve boot time, memory, and security surface
laravel:writing-plans
Create an actionable Laravel implementation plan—bite-sized tasks with TDD-first steps, migrations, services, jobs, and validation points
laravel:debugging-prompts
Create effective debugging prompts—include error messages, stack traces, expected vs actual behavior, logs, and attempted solutions
laravel:data-chunking-large-datasets
Process large datasets efficiently using chunk(), chunkById(), lazy(), and cursor() to reduce memory consumption and improve performance
laravel:performance-select-columns
Select only required columns to reduce memory and transfer costs; apply to base queries and relations
laravel:performance-eager-loading
Prevent N+1 queries by eager loading; enable lazy-loading protection in non-production; choose selective fields
laravel:performance-caching
Use framework caches and value/query caching to reduce work; add tags, locks, and explicit invalidation strategies for correctness
laravel:using-laravel-superpowers
Read first in Laravel repos; explains runner selection (Sail vs non-Sail), core workflows, and how to apply superpowers skills in Laravel projects without platform lock-in
laravel:using-examples-in-prompts
Provide concrete examples—existing code patterns, style samples, input/output pairs—to guide AI toward your project's conventions
laravel:transactions-and-consistency
Wrap multi-write operations in transactions; use dispatchAfterCommit and idempotency patterns to ensure consistency
laravel:template-method-and-plugins
Stabilize workflows with Template Method or Strategy; extend by adding new classes instead of editing core logic
laravel:tdd-with-pest
Apply RED-GREEN-REFACTOR with Pest or PHPUnit; use factories, feature tests for HTTP, and parallel test runners; verify failures before implementation
laravel:task-scheduling
Schedule tasks with safety; use withoutOverlapping, onOneServer, and visibility settings for reliable cron execution
laravel:strategy-pattern
Use the Strategy pattern to select behavior at runtime; bind multiple implementations to a shared interface
laravel:specifying-constraints
Define clear constraints—performance, security, testing, architecture, dependencies—so AI generates code that meets your project standards
laravel:runner-selection
Choose Sail automatically when available, fall back cleanly to host PHP/Composer/Node; paired command map for both environments
laravel:routes-best-practices
Keep routes clean and focused on mapping requests to controllers; avoid business logic, validation, or database operations in route files
laravel:rate-limiting
Apply per-user and per-route limits with RateLimiter and throttle middleware; use backoffs and headers for clients
laravel:queues-and-horizon
Operate and verify queues with or without Horizon; safe worker flags, failure handling, and test strategies
laravel:quality-checks
Unified quality gates for Laravel projects; Pint, static analysis (PHPStan/Psalm), Insights (optional), and JS linters; Sail and non-Sail pairs provided
laravel:prompt-structure
Structure prompts for clarity—separate concerns, prioritize requests, specify acceptance criteria, and break work into testable increments
laravel:ports-and-adapters
Use hexagonal architecture for external systems; define ports (interfaces) and per-provider adapters; select adapter at composition edge
laravel:policies-and-authorization
Enforce access via Policies and Gates; use authorize() and authorizeResource() to standardize controller protections
git-storytelling-commit-strategy
Use when planning commit strategies or determining when to commit changes. Helps developers commit early and often to tell the story of their development process.
git-storytelling-branch-strategy
Use when planning git branching strategies or managing branches for development. Helps create clear development narratives through effective branch organization and workflow patterns.
elixir-ecto-patterns
Use when Elixir Ecto patterns including schemas, changesets, queries, and transactions. Use when building database-driven Elixir applications.
rspec-advanced
Use when advanced RSpec features including custom matchers, shared examples, metadata, and hooks.
graphql-resolvers
Use when implementing GraphQL resolvers with resolver functions, context management, DataLoader batching, error handling, authentication, and testing strategies.
graphql-performance
Use when optimizing GraphQL API performance with query complexity analysis, batching, caching strategies, depth limiting, monitoring, and database optimization.
graphql-inspector-validate
Use when validating GraphQL operations/documents against a schema, checking query depth, complexity, or fragment usage.
act-docker-setup
Use when configuring Docker environments for act, selecting runner images, managing container resources, or troubleshooting Docker-related issues with local GitHub Actions testing.
graphql-inspector-diff
Use when detecting breaking changes between GraphQL schema versions, comparing schemas across branches, or validating schema migrations.
graphql-inspector-ci
Use when setting up GraphQL Inspector in CI/CD pipelines, GitHub Actions, or GitLab CI for automated schema validation.
graphql-inspector-audit
Use when auditing GraphQL operations for complexity metrics, depth analysis, directive usage, or query performance concerns.
gitlab-ci-variables-secrets
Use when configuring GitLab CI/CD variables, managing secrets, or integrating with external secret providers. Covers secure credential handling.
gitlab-ci-pipeline-configuration
Use when configuring GitLab CI/CD pipelines, defining stages, or setting up workflow rules. Covers pipeline structure, stage ordering, and execution flow.
gitlab-ci-job-configuration
Use when defining GitLab CI jobs, configuring scripts, setting up environments, or managing job dependencies. Covers job structure and execution options.
gitlab-ci-best-practices
Use when optimizing GitLab CI/CD pipelines for performance, reliability, or maintainability. Covers pipeline optimization and organizational patterns.
gitlab-ci-artifacts-caching
Use when configuring artifacts for inter-job data passing or caching for faster builds. Covers cache strategies and artifact management.
docker-compose-production
Use when deploying Docker Compose applications to production including security hardening, resource management, health checks, logging, monitoring, and high-availability patterns.
docker-compose-networking
Use when configuring networks and service communication in Docker Compose including bridge networks, overlay networks, service discovery, and inter-service communication.
docker-compose-basics
Use when defining and running multi-container Docker applications with Docker Compose YAML configuration.
cypress-fundamentals
Use when cypress fundamentals including commands, assertions, fixtures, and E2E testing patterns.
Page 439 of 1362 · 68076 results
