Prompts Laravel Package

Product Decisions This Supports

• Interactive CLI-to-Web Workflows: Enables seamless migration of CLI-based user journeys (e.g., onboarding, configuration wizards) to web interfaces without rewriting logic. Ideal for tools like Laravel Forge, Nova, or internal admin dashboards.
• Progressive Enhancement: Supports "build vs. buy" by allowing teams to start with CLI tools (e.g., make:model extensions) and later expose them as web forms without duplicating code.
• Developer Experience (DX) Tools: Accelerates development of interactive CLI commands (e.g., scaffolding, migrations) that can later be surfaced in web UIs (e.g., admin panels, SaaS onboarding).
• Multi-Channel UX: Unifies user flows across CLI (devs, scripts) and web (end-users) for products like dev tools, CMS backends, or SaaS platforms with hybrid workflows.
• Roadmap for Web-First Products: Justifies investing in CLI tools today if the roadmap includes web integrations (e.g., "We’ll build a web dashboard next quarter, so let’s design this CLI flow to be web-compatible now").

When to Consider This Package

• Adopt if:

  • Your Laravel app has CLI commands with multi-step user input (e.g., wizards, setup tools) that could benefit from a web interface.
  • You’re building a hybrid CLI/web product (e.g., dev tools, internal admin panels) and want to avoid duplicating prompt logic.
  • Your team prioritizes developer productivity and wants to reuse CLI flows in web contexts (e.g., Laravel Nova extensions).
  • You need state persistence between steps in both CLI and web (e.g., forms with validation across multiple pages).
  • Your project uses Laravel Artisan and you’re comfortable with PHP’s object-oriented patterns.

• Look elsewhere if:

  • You only need pure CLI prompts (use Laravel’s built-in prompts package or Symfony’s Console component).
  • Your web interface is static (no need for interactive flows; use Blade/Livewire forms instead).
  • You’re building a public-facing SaaS with complex UX (consider dedicated frontend frameworks like React/Alpine.js for better DX).
  • Your team lacks PHP/Laravel expertise to maintain custom command logic in both CLI/web contexts.
  • You need advanced web form features (e.g., real-time validation, rich UI components) beyond what this package offers.

How to Pitch It (Stakeholders)

For Executives: "This package lets us build interactive setup wizards or admin tools once—whether users run them in the terminal or access them via a web browser. For example, our make:model command could later power a web-based scaffolding tool without rewriting the logic. It’s a 10x for developer tools, internal dashboards, or SaaS onboarding flows where CLI and web need to stay in sync. Low risk (MIT license, Laravel-native), high reward for reducing technical debt."

For Engineering: *"Moox/Prompts lets us write Laravel Artisan commands that work in both CLI and web by storing state in public properties and defining steps as methods. No more duplicating prompt logic for web forms—just extend FlowCommand, define your steps, and it handles persistence automatically. Perfect for:

• Internal tools (e.g., db:seed wizards, config generators).
• Laravel Nova/Vue extensions that need interactive setup.
• Dev environments where CLI and web should feel like one flow. Think of it as ‘Turbocharged Artisan’ for hybrid workflows. The API is familiar (like Laravel Prompts), so adoption is easy."*