원클릭으로 Manus에서 모든 스킬 실행

laravel-brainstorming

스타141

포크1

업데이트2025년 11월 3일 03:15

Interactive design refinement tailored to Laravel projects; clarify domain, data, interfaces, testing, and quality gates while accounting for Sail/non‑Sail environments

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

jpcaparas

jpcaparas/superpowers-laravel

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

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.

이 저장소의 다른 Skills

같은 저장소

laravel-ai-sdk

jpcaparas/superpowers-laravel

Build AI features with the first-party Laravel AI SDK (Laravel 13+); agents, embeddings, images, audio, and tool calling with provider-agnostic APIs

2026-07-02141

laravel-api-resources-and-pagination

jpcaparas/superpowers-laravel

Use API Resources with pagination and conditional fields; keep response shapes stable and cache-friendly

2026-07-02141

laravel-blade-components-and-layouts

jpcaparas/superpowers-laravel

Compose UIs with Blade components, slots, and layouts; keep templates pure and testable

2026-07-02141

laravel-code-review-requests

jpcaparas/superpowers-laravel

Request effective code reviews—specify focus areas, provide context, ask for architectural feedback, reference Laravel conventions

2026-07-02141

laravel-daily-workflow

jpcaparas/superpowers-laravel

Practical daily checklist for Laravel projects; bring services up, run migrations, queues, quality gates, and tests

2026-07-02141

laravel-debugging-prompts

jpcaparas/superpowers-laravel

Create effective debugging prompts—include error messages, stack traces, expected vs actual behavior, logs, and attempted solutions

2026-07-02141

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

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.