synapse: Skill for Claude Code

Laravel Package Development (Synapse)

Distilled from the Laravel 13 package docs, laravelpackage.com, and Synapse's implementation. When these conflict with the repo's existing patterns, follow the repo — the conventions below already match it.

Golden rules

1. register() binds; boot() wires. In register(): only mergeConfigFrom and container bindings — never resolve services, hit the DB, or touch facades that need a booted app. In boot(): routes, views, publishing, commands, events, gates, schedules.
2. Config must be cache-safe. No closures in config files (breaks config:cache). Never call env() at runtime outside a config file — bake env-derived logic into the config's default value and read config() everywhere else. (Synapse's production route-guard does exactly this: 'enabled' => (bool) env('SYNAPSE_ENABLED', env('APP_ENV') !== 'production').)
3. mergeConfigFrom merges only the first level. Don't rely on deep-merging nested config a user partially overrode.
4. Guard console-only work. Register commands and publish groups inside if ($this->app->runningInConsole()).
5. Publish host-owned resources with separate tags. Config, migrations, and the application provider are publishable. Compiled dashboard assets stay inside the package and are never published.
6. Package discovery, not manual registration. The provider is auto-loaded via extra.laravel.providers in composer.json.

Service provider anatomy

public function register(): void
{
    $this->mergeConfigFrom(__DIR__.'/../config/synapse.php', 'synapse');
    // container bindings only
}

public function boot(): void
{
    $this->registerRoutes();                                  // guarded by config
    $this->loadViewsFrom(__DIR__.'/../resources/views', 'synapse');
    $this->registerScheduledTasks();                          // conditional
    if ($this->app->runningInConsole()) {
        $this->registerPublishing();                          // tagged groups
        $this->registerCommands();
    }
}