Cli Laravel Package

Product Decisions This Supports

• Internal Developer Tools (DevTools) Roadmap: Accelerate development of CLI utilities (e.g., data migration scripts, deployment helpers, or internal dashboards) by reducing boilerplate and improving UX.
• Build vs. Buy: Avoid reinventing CLI parsing/UX wheels (e.g., Symfony Console is heavier; this package offers a lightweight alternative with modern features).
• Developer Experience (DX) Initiatives: Standardize CLI tooling across teams with consistent argument parsing, help generation, and terminal output, reducing onboarding friction.
• Monorepo/Modular Architecture: Package CLI tools as reusable, self-contained modules (e.g., php bin/foo for project-specific utilities) without coupling to frameworks.
• Open-Source Contributions: Leverage MIT license to extend or fork for proprietary tools, aligning with community-driven development.

When to Consider This Package

• Adopt when:

  • Building lightweight, standalone CLI tools (e.g., scripts for CI/CD, data processing, or internal workflows).
  • Needing auto-generated help and structured argument parsing without framework bloat (e.g., Symfony Console).
  • Prioritizing terminal UX (colors, prompts, sections) for interactive developer tools.
  • PHP projects already using Laravel but requiring framework-agnostic CLI components.

• Look elsewhere if:

  • Requiring enterprise-grade CLI features (e.g., complex job queues, async processing) → Consider Symfony Console or Laravel Artisan.
  • Building publicly distributed tools with strict branding/license needs (MIT may not suffice).
  • Needing advanced debugging or IDE integration (e.g., PhpStorm CLI tooling).
  • Performance is critical (this prioritizes readability over micro-optimizations).

How to Pitch It (Stakeholders)

For Executives: "adhocore/cli lets us ship high-quality CLI tools 30% faster with less code. It’s the ‘React for PHP CLI’—lightweight, intuitive, and reusable across teams. Think of it as a force multiplier for DevOps, data pipelines, or internal automation. MIT-licensed and dependency-light, so it won’t bloat our stack."

For Engineering: *"This replaces manual getopt() parsing and echo spaghetti with a modern, Laravel-like API for CLI apps. Key wins:

• Auto-help: Define commands once; help docs generate automatically.
• Terminal polish: Built-in colors, prompts, and sections (no more ANSI escape codes).
• Validation: Built-in argument/option validation with defaults.
• No framework lock-in: Works in Laravel, standalone scripts, or even non-PHP projects via PHP CLI. Example: Replace a 50-line argparse-style script with 10 lines of clean, documented code."*

For Developers: *"Imagine writing a CLI tool where:

• --help just works (no manual docs).
• You validate inputs with ->validate(fn($val) => $val > 0).
• Terminal output looks professional with ->section('Progress')->info('Step 1/3'). No more hacking fgets() or parsing $argv manually. Just define your commands and go."