laravel:debugging-prompts
Create effective debugging prompts—include error messages, stack traces, expected vs actual behavior, logs, and attempted solutions
laravel:nova:resource-patterns
Consistent Nova resources—fields, actions, metrics, lenses, filters, authorization—and how to evolve resources alongside schema changes
laravel:migrations-and-factories
Safe database change patterns; when to modify vs add migrations; always pair models with migrations and factories; seeding guidance
laravel:laravel-prompting-patterns
Use Laravel-specific vocabulary—Eloquent patterns, Form Requests, API resources, jobs/queues—to get idiomatic framework code
laravel:iterating-on-code
Refine AI-generated code through specific feedback—point out errors, identify gaps, show desired changes, reference style guides
laravel:performance-caching
Use framework caches and value/query caching to reduce work; add tags, locks, and explicit invalidation strategies for correctness
laravel:internationalization-and-translation
Build with i18n in mind from day one using Laravel translation helpers, JSON files, Blade integration, and locale management
laravel:constants-and-configuration
Replace hardcoded values with constants, enums, and configuration for maintainability; use PHP 8.1+ enums and config files
laravel:controller-cleanup
Reduce controller bloat using Form Requests for auth/validation, small Actions/Services with DTOs, and resource/single-action controllers
laravel:controller-tests
Write focused controller tests using HTTP assertions; keep heavy logic in Actions/Services and unit test them
laravel:api-resources-and-pagination
Use API Resources with pagination and conditional fields; keep response shapes stable and cache-friendly
laravel:writing-plans
Create an actionable Laravel implementation plan—bite-sized tasks with TDD-first steps, migrations, services, jobs, and validation points
laravel:api-surface-evolution
Evolve APIs safely using versioned DTOs/transformers, deprecations, and compatibility tests
laravel:blade-components-and-layouts
Compose UIs with Blade components, slots, and layouts; keep templates pure and testable
laravel:bootstrap-check
Detect Sail/non‑Sail and print the right command pairs for your environment; verify dependencies and key services are reachable
laravel:custom-helpers
Create and register small, pure helper functions when they improve clarity; keep them organized and tested
laravel:daily-workflow
Practical daily checklist for Laravel projects; bring services up, run migrations, queues, quality gates, and tests
laravel:brainstorming
Interactive design refinement tailored to Laravel projects; clarify domain, data, interfaces, testing, and quality gates while accounting for Sail/non‑Sail environments
laravel:code-review-requests
Request effective code reviews—specify focus areas, provide context, ask for architectural feedback, reference Laravel conventions
laravel:complexity-guardrails
Keep cyclomatic complexity low; flatten control flow, extract helpers, and prefer table-driven/strategy patterns over large switches
laravel:config-env-storage
Portable storage configuration across S3/R2/MinIO with optional CDN—env toggles, path-style endpoints, and URL generation
ink-component-patterns
Use when building terminal UIs with Ink component patterns for React-based CLI applications.
terraform-state
Use when managing Terraform state files, remote backends, and state locking for infrastructure coordination.
terraform-modules
Use when creating and using reusable Terraform modules for organizing and sharing infrastructure code.
terraform-configuration
Use when writing and organizing Terraform infrastructure-as-code configurations for cloud resource provisioning.
tailwind-utility-classes
Use when working with Tailwind CSS utility classes for layout, spacing, typography, colors, and visual effects. Covers utility-first CSS patterns and class composition.
tailwind-responsive-design
Use when building responsive layouts and mobile-first designs with Tailwind CSS. Covers breakpoints, container queries, and responsive utilities.
tailwind-performance
Use when optimizing Tailwind CSS for production, reducing bundle size, and improving performance. Covers PurgeCSS, JIT mode, and build optimization.
tailwind-configuration
Use when setting up or customizing Tailwind CSS configuration, theme customization, plugins, and build setup. Covers tailwind.config.js setup and content paths.
tailwind-components
Use when building reusable component patterns with Tailwind CSS. Covers component extraction, @apply directive, and composable design patterns.
syncpack-version-groups
Use when defining version policies, banning dependencies, pinning versions, or creating partitioned version groups in syncpack. Covers advanced version management patterns.
syncpack-configuration
Use when setting up or configuring syncpack for a monorepo. Covers configuration files, workspace detection, and custom rule definitions for dependency version management.
storybook-story-writing
Use when creating or modifying Storybook stories for components. Ensures stories follow CSF3 format, properly showcase component variations, and build successfully.
storybook-play-functions
Use when adding interaction testing to Storybook stories. Enables automated testing of component behavior, user interactions, and state changes directly in stories.
storybook-configuration
Use when setting up or configuring Storybook for a project. Covers main configuration, addons, builders, and framework-specific setup.
storybook-component-documentation
Use when creating or improving component documentation in Storybook. Helps generate comprehensive docs using MDX, autodocs, and JSDoc comments.
storybook-args-controls
Use when configuring interactive controls and args for Storybook stories. Helps create dynamic, explorable component demonstrations with proper type constraints.
rspec-mocking
Use when rSpec mocking with doubles, stubs, mocks, spies, and partial mocking strategies.
rspec-fundamentals
Use when rSpec fundamentals including describe, context, it blocks, let, and basic matchers for BDD testing.
pytest-plugins
Use when pytest plugin ecosystem including pytest-cov, pytest-mock, and custom plugin development.
pytest-fixtures
Use when pytest fixtures, conftest files, parametrize decorators, and fixture scopes for comprehensive test setup.
pytest-advanced
Use when advanced Pytest features including markers, custom assertions, hooks, and coverage configuration.
pulumi-stacks
Use when managing multiple environments with Pulumi stacks for development, staging, and production deployments.
pulumi-components
Use when building reusable infrastructure components with Pulumi for modular, composable cloud resources.
pulumi-basics
Use when writing infrastructure-as-code with Pulumi using programming languages for cloud resource provisioning.
playwright-test-architecture
Use when setting up Playwright test projects and organizing test suites with proper configuration and project structure.
playwright-page-object-model
Use when creating page objects or refactoring Playwright tests for better maintainability with Page Object Model patterns.
playwright-fixtures-and-hooks
Use when managing test state and infrastructure with reusable Playwright fixtures and lifecycle hooks for efficient test setup and teardown.
playwright-bdd-step-definitions
Use when creating step definitions with Given, When, Then, using createBdd() for step functions, implementing Page Object Model patterns, and sharing fixtures between steps.
claude-agent-sdk-context-management
Use when managing agent context, memory, and conversation state in Claude AI agents using the Agent SDK.
Page 592 of 1724 · 86172 results
