README

AI playbook + stub library for bootstrapping the canonical Sander / hihaho dev setup. Pure markdown + stub files. No PHP code in the package itself. Install globally once, use everywhere — same UX as composer global require laravel/installer.

What it does

Walks an AI agent (Claude Code, Cursor, GitHub Copilot, …) through bootstrap, audit, or upgrade of a PHP repo against a canonical baseline:

• pint.json, phpstan.neon.dist, phpstan-baseline.neon, rector.php — code-quality tooling
• .editorconfig, .gitattributes (with the # >>> package-boost (managed) >>> block — sentinel name preserved for backward compat; owned by package-boost-php), .gitignore
• .mcp.json (Laravel-aware categories only; the framework-agnostic categories — php-package, composer-plugin, phpstan-extension, rector-extension, skill-bundle — skip it)
• .config/boost.php — boost-core agent config, pinning Claude Code / Copilot / Codex (every category except laravel-project, which uses laravel/boost). The .config/ layout is canonical (boost-core ≥ 0.17); the sync manifest lives at .config/boost/
• sandermuller/boost-skills — the shared dev-workflow skill library, added to require-dev + .config/boost.php; bootstrap interactively picks which skill tags (php / frontend / github / jira) to activate
• Shared .github/workflows/{phpstan,pint-check,rector-check,update-changelog}.yml + per-category run-tests.yml + dependabot.yml
• tests/Pest.php or phpunit.xml (vendor-driven default)
• Per-category extras (testbench.yaml, workbench/, ServiceProvider, extension.neon, src/Plugin.{shape}.php for composer-plugin, etc.)

Install (one-time per machine)

composer global require sandermuller/repo-init
composer global exec -- boost sync --scope=user --all

The second command publishes the repo-init skill (and any other globally-installed sandermuller/boost-core consumer's skills) into ~/.claude/skills/sandermuller__repo-init/, ~/.cursor/skills/sandermuller__repo-init/, ~/.agents/skills/sandermuller__repo-init/, etc. The skill then auto-activates in any project. Re-run composer global exec -- boost sync --scope=user --all after each composer global update to refresh. (The composer global exec -- form runs boost from Composer's global vendor/bin/ regardless of your current directory; the literal -- separator stops Composer from interpreting boost's flags as its own.) See references/boost-core-user-scope.md for the full contract.

Changed in boost-core 0.6.0. Before 0.6.0 boost-core was a Composer plugin and auto-synced on every composer global install/update. 0.6.0 removed the plugin (boost-core is now type: library); the sync is the one-line manual command above instead. Older boost-core migrations (e.g. the 0.4.0 user-scope slug rename) are covered in UPGRADING.md.

Use

Ask Claude (or any agent with the synced skill):

Set up this repo as a Laravel package. Audit this repo against the canonical setup. Upgrade tooling here to current baseline.

The agent reads the repo-init skill, decides intent + category, and opens the matching phase file from $(composer global config home)/vendor/sandermuller/repo-init/phases/. Everything happens in your conversation; nothing is written to your target repo by repo-init itself (the agent does the writes, following the phase's instructions).

Update

composer global update sandermuller/repo-init
composer global exec -- boost sync --scope=user --all

The second line is required: boost-core 0.6.0 removed the auto-sync plugin, so refreshing the user-scope skill dirs is a manual command after every update.

Repo categories supported

Each has its own bootstrap, audit, and upgrade phase file (23 phase files total — 7 audit + 7 upgrade + 9 bootstrap, the extra 2 bootstraps cover filament-plugin and nova-tool which fall through to laravel-package for audit/upgrade). composer-plugin covers framework-agnostic Composer plugins (e.g. boost-core, package-boost-php) with sub-flags for command-provider / event-subscriber shapes. skill-bundle covers distributable packages whose product is AI agent skills — type: library, sandermuller/boost-core in runtime require, ships resources/boost/skills/, no src/.

What's NOT in the package

• No PHP source under src/. No artisan commands, no Symfony Console binary. The agent does all the work.
• No state files written to your target repo. No .repo-init-state.json, no .ai/playbooks/repo-init/ copies. Stubs are read in place from the global vendor dir.
• No automatic destructive ops. Every overwrite, every dep install, every composer require is gated on a prompt or a documented safety rail (see checklists/per-category-never-touch.md).

Project-local install (escape hatch)

If you want to pin a specific repo-init version per project:

composer require --dev sandermuller/repo-init
vendor/bin/boost sync

The project-local install takes precedence over the global one. Remove with composer remove --dev sandermuller/repo-init.

Uninstall

composer global remove sandermuller/repo-init

Optional skill cleanup (the synced user-level skill dirs survive composer global remove because sync writes file copies — see references/boost-core-user-scope.md):

rm -rf ~/.{claude,cursor,agents,github,amp,gemini,junie,kiro,opencode}/skills/sandermuller__repo-init

(boost-core 0.6+ fans into 9 agent targets — the brace expansion above clears all of them in one line. Keep the synced skills if you might re-install later — re-running the install + composer global exec -- boost sync --scope=user --all re-syncs them, so leaving them in place is harmless.)

Design

See SPEC.md for the full design (markdown-only + global-install model).

Highlights:

• Single entry point — resources/boost/skills/repo-init/SKILL.md.
• 23 self-contained phase playbooks under phases/.
• 18 reference docs under references/ (incl. machine-readable per-category-deps.yml).
• 5 checklists under checklists/.
• 13 stub trees under stubs/ — shared/ + 2 test-framework variants + 10 categories (composer-plugin, filament-plugin, laravel-package, laravel-package-spatie, laravel-project, nova-tool, php-package, phpstan-extension, rector-extension, skill-bundle).

Dependencies

Runtime (require) — what composer global require sandermuller/repo-init pulls in for every consumer:

• sandermuller/boost-core — type: library from 0.6.0 (the Composer plugin was removed in that release). Ships the standalone vendor/bin/boost bin and the BoostAutoSync::run auto-sync engine (silent on no-op installs; prints the one-line sync summary when wrote>0). Categories that depend on boost-core directly (skill-bundle) wire BoostAutoSync::run in post-install-cmd / post-update-cmd; wrapper categories instead wire their wrapper's namespace façade (PackageBoostPhp\Scripts\AutoSync::run / PackageBoostLaravel\Scripts\AutoSync::run), which delegates to it — so the scaffold references only a class from its own direct dependency. See references/composer-scripts.md.

Maintenance (require-dev) — used only by repo-init's own dev workflow; NOT propagated to consumers (Composer never installs a required package's require-dev):

• sandermuller/package-boost-php — the boost-family umbrella repo-init dogfoods (it's also what the php-package / phpstan-extension / rector-extension / composer-plugin scaffolds pin).
• sandermuller/boost-skills — the shared dev-workflow skill library (code-review, bug-fixing, pre-release, evaluate, …); boost-core syncs its skills into repo-init's agent dirs at dev time.
• laravel/pint — code style.

Contributing

See CONTRIBUTING.md.

Security

See SECURITY.md.

Changelog

See CHANGELOG.md.

License

MIT — see LICENSE.