PHPackages springloadedco/turbo - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Utility & Helpers](/categories/utility) 4. / 5. springloadedco/turbo ActiveLibrary[Utility & Helpers](/categories/utility) springloadedco/turbo ==================== Springloaded's Laravel AI development toolkit. 35.3k[3 issues](https://github.com/springloadedco/turbo/issues)[5 PRs](https://github.com/springloadedco/turbo/pulls)PHPCI passing Since Feb 3Pushed 2mo agoCompare [ Source](https://github.com/springloadedco/turbo)[ Packagist](https://packagist.org/packages/springloadedco/turbo)[ RSS](/packages/springloadedco-turbo/feed)WikiDiscussions main Synced 3w ago READMEChangelogDependenciesVersions (25)Used By (0) [![Turbo](turbo.png)](turbo.png) What is Turbo? -------------- [](#what-is-turbo) Turbo is Springloaded's opinionated toolkit for AI-assisted Laravel development. It combines open source [Superpowers](https://github.com/obra/superpowers) — brainstorming, plan creation, and plan execution — with Springloaded's own standards, skills, and tooling to create a consistent, high-quality environment for building applications. ### Superpowers Workflow [](#superpowers-workflow) Turbo installs [Superpowers](https://github.com/obra/superpowers) during setup, which provides a structured development workflow through slash commands: ``` /brainstorming ──> /writing-plans ──> /executing-plans ──> Review ^ │ └────────── needs changes ───────────┘ ``` CommandWhat it does`/brainstorming`Explore the idea — ask questions, consider approaches, produce a design`/writing-plans`Turn the design into a step-by-step implementation plan`/executing-plans`Execute the plan with review checkpoints between stepsOther superpowers activate automatically when relevant — test-driven development before writing code, systematic debugging when something breaks, verification before claiming work is done. ### Skills [](#skills) **Skills** encode how Springloaded builds Laravel apps — controllers, actions, testing, validation, Inertia, GitHub workflows, and more. They work with any agent that supports skills (Claude, Cursor, Codex, GitHub Copilot) via [`npx skills`](https://skills.sh), so the whole team builds the same way regardless of which agent they use. ### Docker Sandbox [](#docker-sandbox) **Docker Sandbox** lets you run Claude in an isolated environment with your project workspace mounted, so agents can work freely without touching your local machine. The pre-built sandbox image includes PHP 8.4, Composer, Node 22, Chromium, and fixes for native binary corruption during npm install — just launch and go. ### Feedback Loops [](#feedback-loops) **Feedback Loops** wire your project's verification commands (tests, linting, static analysis) directly into skill templates, so agents check their own work as they go. ### Prerequisites [](#prerequisites) - PHP 8.4+ - Laravel 11 or 12 - Node.js / npm (required for `npx skills`) - sbx CLI (required for sandbox commands -- `brew install docker/tap/sbx`) Installation ------------ [](#installation) Turbo is currently pre-release. Until a stable version is tagged, require it with `@dev`: ``` composer require springloadedco/turbo:@dev --dev ``` ### From a Local Clone [](#from-a-local-clone) If you have Turbo cloned locally and want to symlink it instead, point Composer at your local clone: ``` composer config repositories.turbo path /path/to/turbo ``` You'll need to disable symlinking if you plan on using Laravel Boost. If you install without the symlink, you'll need to re-run composer require any time you want to pull changes. ``` composer config repositories.turbo.options.symlink false ``` Then require the package: ``` composer require springloadedco/turbo:@dev --dev ``` Composer will automatically symlink the local directory, so changes are reflected immediately without re-installing. Getting Started --------------- [](#getting-started) Run the install command to configure skills, set up a GitHub token, and create the Docker sandbox: ``` php artisan turbo:install ``` Then launch an interactive Claude session in the sandbox: ``` php artisan turbo:claude ``` On the first run, you'll be prompted to authenticate with Claude. This only needs to be done once per sandbox. To re-publish Turbo's skills after a package update: ``` php artisan turbo:skills ``` Skills ------ [](#skills-1) Turbo ships skills organized into groups. During `turbo:install` you pick which groups to install; individual skills within each group can be customized. **Laravel patterns** — opinionated Laravel development conventions: SkillDescription`laravel-controllers`Invokable controller patterns with Inertia`laravel-actions`Business logic encapsulation patterns`laravel-validation`Form Request validation patterns`laravel-testing`Pest/PHPUnit testing best practices`laravel-inertia`TypeScript page component patterns**Project utilities** — installed by default: SkillDescription`feedback-loops`Enforces project verification commands before claiming work done, committing, or opening a PR`agent-captures`Standardizes agent-browser screenshot/PDF/video output locations**GitHub workflow** (opt-in): SkillDescription`github-issue`Atomic issue creation with verifiable acceptance criteria`github-labels`Consistent label taxonomy (type/priority)`github-milestone`Well-structured milestones grouping related issues**Third-party integrations** — installed by default: SkillDescription`superpowers`[Superpowers](https://github.com/obra/superpowers) — brainstorming, plan writing, subagent-driven development, code review, TDD, and more (14 skills)`agent-browser`Browser automation via [vercel-labs/agent-browser](https://agent-browser.dev/)Configuration ------------- [](#configuration) Publish the config file to customize Turbo's behavior: ``` php artisan vendor:publish --tag=turbo-config ``` This creates `config/turbo.php` where you can configure feedback loops — the verification commands injected into skill templates at publish time: ``` 'feedback_loops' => [ 'composer lint', 'composer test', 'composer analyse', 'npm run lint', 'npm run types', 'npm run build', 'npm run test', ], ``` Remove or add commands to match your project's toolchain. The `feedback-loops` skill uses these commands to enforce that agents verify their work before claiming tasks complete. They're rendered into skill templates via the `{{ $feedback_loops }}` and `{{ $feedback_loops_checklist }}` placeholders at install time. The config also includes Docker sandbox settings: ``` 'docker' => [ 'image' => env('TURBO_DOCKER_IMAGE', 'docker.io/springloadedco/turbo:latest'), 'workspace' => env('TURBO_DOCKER_WORKSPACE', base_path()), ], ``` KeyDescriptionDefault`image`Fully-qualified OCI registry image for the sandbox template`docker.io/springloadedco/turbo:latest``workspace`Local directory mounted into the sandbox`base_path()`Commands -------- [](#commands) CommandDescription`turbo:install`Set up Turbo for your project (see [Getting Started](#getting-started))`turbo:skills`Re-publish Turbo skills after a package update`turbo:claude`Start an interactive Claude session in the sandbox`turbo:prompt {prompt}`Run Claude with a one-off prompt in the sandbox`turbo:exec {command}`Execute a command inside the sandbox`turbo:prepare`Configure sandbox host access (/etc/hosts + policy)`turbo:ports`List, publish, or unpublish sandbox ports`turbo:start`Start the sandbox (without attaching)`turbo:stop`Stop the sandbox (preserving state)`turbo:rm`Remove the sandbox and all its state`turbo:doctor`Run a health check on the sandbox environment### Docker Sandbox [](#docker-sandbox-1) Turbo uses the [sbx CLI](https://docs.docker.com/reference/cli/sbx/) to manage sandboxes. See the [Docker Sandboxes documentation](https://docs.docker.com/ai/sandboxes/) for more details. Turbo publishes a pre-built sandbox image to Docker Hub as [`springloadedco/turbo`](https://hub.docker.com/r/springloadedco/turbo), based on `docker/sandbox-templates:claude-code` with PHP 8.4, common extensions, Composer, Node.js 22, and Chromium pre-installed. Most users don't need to build anything — `turbo:install` uses the published image by default and sbx pulls it from Docker Hub. **Extending the image:** If your project needs additional tools, create a Dockerfile in your project root: ``` FROM springloadedco/turbo:latest USER root RUN apt-get update && apt-get install -y redis-tools USER agent ``` Set your own registry image in `.env`: ``` TURBO_DOCKER_IMAGE=docker.io/my-org/my-sandbox:latest ``` Then build and push with Docker: ``` docker build --push -t docker.io/my-org/my-sandbox:latest . ``` **Start an interactive Claude session:** ``` php artisan turbo:claude ``` This opens an interactive Claude session inside the sandbox with your project workspace mounted. **Run a one-off prompt:** ``` php artisan turbo:prompt "Write tests for the UserController" ``` Sends the prompt to Claude inside the sandbox and streams the output back to your terminal. Development ----------- [](#development) When working on Turbo itself, use `bin/turbo` to run commands via Orchestra Testbench: ``` bin/turbo install # turbo:install bin/turbo claude # turbo:claude bin/turbo prompt "…" # turbo:prompt ``` Optionally, install [direnv](https://direnv.net) to drop the `bin/` prefix and just use `turbo `: ``` brew install direnv ``` Add the hook to your shell (`~/.zshrc`): ``` eval "$(direnv hook zsh)" ``` Then allow the project's `.envrc`: ``` direnv allow ``` After that, `turbo claude`, `turbo prompt "…"`, etc. work directly whenever you're in the project directory. Testing ------- [](#testing) ``` composer test ``` Changelog --------- [](#changelog) Please see [CHANGELOG](CHANGELOG.md) for more information on what has changed recently. Contributing ------------ [](#contributing) Please see [CONTRIBUTING](CONTRIBUTING.md) for details. Security Vulnerabilities ------------------------ [](#security-vulnerabilities) Please review [our security policy](../../security/policy) on how to report security vulnerabilities. Credits ------- [](#credits) - [Jeff Sagal](https://github.com/sagalbot) - [All Contributors](../../contributors) License ------- [](#license) The MIT License (MIT). Please see [License File](LICENSE.md) for more information. ### Health Score 26 — LowBetter than 40% of packages Maintenance36 Infrequent updates — may be unmaintained Popularity28 Limited adoption so far Community10 Small or concentrated contributor base Maturity25 Early-stage or recently created project Bus Factor1 Top contributor holds 92.6% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Community Maintainers ![](https://www.gravatar.com/avatar/0dafcec0352ac1a4de72f679bf2c72752d967bd388ec4e9c186142738993b945?d=identicon)[owenconti](/maintainers/owenconti) ![](https://www.gravatar.com/avatar/4ae5691168bf4514c10cf8ec89671d4712af795b62a445482153dd68b2651d36?d=identicon)[sagalbot](/maintainers/sagalbot) --- Top Contributors [![sagalbot](https://avatars.githubusercontent.com/u/692538?v=4)](https://github.com/sagalbot "sagalbot (126 commits)")[![Copilot](https://avatars.githubusercontent.com/in/1143301?v=4)](https://github.com/Copilot "Copilot (9 commits)")[![raven-pierce](https://avatars.githubusercontent.com/u/108248559?v=4)](https://github.com/raven-pierce "raven-pierce (1 commits)") ### Embed Badge ![Health badge](/badges/springloadedco-turbo/health.svg) ``` [![Health](https://phpackages.com/badges/springloadedco-turbo/health.svg)](https://phpackages.com/packages/springloadedco-turbo) ``` ### Alternatives [moosend/website-tracking By installing the Moosend PHP Tracking library you are can track page views, product views, add to cart events and successful purchases. You can later use these details to segment your user base, run automations, check how successful your latest promo has been and how many conversions your landing page has led to. 1121.9k1](/packages/moosend-website-tracking) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)