Skill

laravel:brainstorming

Guides interactive brainstorming for Laravel features and refactors, clarifying goals, domain, data models, APIs, side-effects, testing, and Sail environments.

Laravel

Php

Docker

backend

testing

npx claudepluginhub jpcaparas/superpowers-laravel --plugin superpowers-laravel

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Use this when shaping features or refactors. Keep answers concise, then propose a design and gather confirmation before planning.

SKILL.md

Similar Skills

laravel-brainstorming

Refines rough Laravel feature ideas into fully-formed designs via collaborative questioning, alternative exploration, and incremental validation before coding.

laravel-claude-agents

laravel:prompt-structure

131

Structures prompts for clarity by separating concerns, prioritizing requests, specifying acceptance criteria, and breaking work into testable increments. Useful for complex Laravel development tasks.

superpowers-laravel

brainstorming

159

Refines rough ideas into fully-formed designs via phased process: Socratic questioning for understanding, alternative exploration with trade-offs, and incremental validation before coding.

ed3d-plan-and-execute

Stats

Stars131

Forks0

Last CommitNov 3, 2025

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

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.

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.