laravel:brainstorming
Interactive design refinement tailored to Laravel projects; clarify domain, data, interfaces, testing, and quality gates while accounting for Sail/non‑Sail environments
Works with
--- name: laravel:brainstorming description: Interactive design refinement tailored to Laravel projects; clarify domain, data, interfaces, testing, and quality gates while accounting for Sail/non‑Sail environments license: MIT --- # Brainstorming (Laravel) Use this when shaping features or refactors. Keep answers concise, then propose a design and gather confirmation before planning. ## Ask (one at a time) - Goal: What outcome should users achieve? - Domain: Which bounded contexts or packages are involved? - Data: New models/relations? Required queries and invariants? - Interfaces: HTTP/API/CLI? Required inputs/outputs? Authz? - Side‑effects: Email, storage, queues, external systems? - Performance: Throughput, latency, pagination, N+1 risks? - Observability: Logs, metrics, events, failure handling? - Testing: TDD entry point, fixtures/factories, edge cases? - Environment: Sail or host? DB/cache/mail/storage availability? ## Propose Present a design of 200–300 words, covering: - Routes/contracts, validation, DTOs/transformers - Services (ports+adapters, strategies/pipelines) - Data model changes and migrations - Jobs/events/listeners where relevant - Test strategy (feature/unit), factories and seeds - Quality gates and rollout plan ## Prepare Next Steps Suggest a short implementation plan; then use `laravel:writing-plans` to formalize it.
More Testing skills
tdd
mattpocock/skills
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
setup-pre-commit
mattpocock/skills
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.
agent-browser
vercel-labs/agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
