Orqestria Download
← Back to ERP system builders

Skill · Version 1.0.0

Discover a Laravel codebase

Maps the installed Laravel stack and actual project structure before choosing APIs, conventions or verification commands.

laravel-codebase-discovery

Team members using this skill

See how it helps

When is it useful?

Use when starting work in an unfamiliar Laravel application or checking upgrade assumptions.

What does it help you do?

  • Reads Composer versions and existing test, formatting and analysis configuration.
  • Distinguishes the repository's real application skeleton from newer default layouts.
  • Learns neighboring controller, model, request and policy patterns before implementation.

Try asking this

Map our customer-management feature, installed packages and current verification commands before proposing a new endpoint. Trace an existing customer update through route, request, policy and action. Use those actual conventions to estimate the endpoint and select its focused tests.

Detailed documentation

Read the skill’s original instructions, examples and checks in their authored language.

Details…Show less

Laravel Codebase & Version Discovery

Verify the project's actual Laravel, PHP, package versions and structure before proposing or writing code.

1. Versions, packages and tooling

  • Read composer.json and composer.lock for the installed php constraint, laravel/framework version and first-party or ecosystem packages (Sanctum, Horizon, Cashier, Pennant,Octane, Reverb, Inertia, Livewire, Filament, Spatie packages).
  • Check composer.json scripts, phpunit.xml / phpunit.xml.dist, pest.php, pint.json, phpstan.neon* and rector.php to see how the project runs tests, formatting and static analysis.
  • When version-specific behavior is uncertain, inspect the installed source in vendor/laravel/framework or the official docs for that exact major version. Never assume a newer Laravel feature exists without checking.

2. Skeleton and lifecycle structure

  • Check whether the app uses the Laravel 11+ streamlined skeleton (bootstrap/app.php with Application::configure(), withRouting(), withMiddleware(), withExceptions(), bootstrap/providers.php, Console Commands auto-discovery in app/Console/Commands/ and schedules in routes/console.php) or the Laravel 10 structure (app/Http/Kernel.php, app/Console/Kernel.php, app/Exceptions/Handler.php).
  • An upgraded Laravel 11 or 12 app may intentionally keep its Laravel 10 Kernel and Handler classes. Follow the structure that actually exists in the repository.

3. Infer local conventions from sibling files

  • Read 2–3 sibling files in each directory you will touch (app/Models, app/Http/Controllers, app/Http/Requests, app/Policies, app/Jobs, tests/Feature) before creating or editing code.
  • Note how business logic is organized (thin controllers with Form Requests, Action classes, Services, Events/Jobs, or domain folders) and match it; do not introduce a new layer (such as a Repository or Service layer) unless the codebase already uses it or the task genuinely requires it.
  • Trace the full lifecycle for the affected path across HTTP requests, CLI commands and long-running queue workers, including how tenant or customer context is resolved in each environment.

Included files 2

  • LICENSE.txt
  • SKILL.md