Admin authentication for Craftable admin panels: login/logout, password reset and optional account activation for the admin guard. Composer dejwcake/admin-auth, namespace Brackets\AdminAuth (fork of brackets/admin-auth). Part of the Craftable ecosystem — see README.md.
php artisan boost:add-skill dejwcake/admin-auth
Save this content to: AGENTS.md
# AGENTS.md — dejwcake/admin-auth
Admin authentication for Craftable admin panels: login/logout, password reset and optional
account activation for the `admin` guard. Composer `dejwcake/admin-auth`, namespace
`Brackets\AdminAuth` (fork of `brackets/admin-auth`). Part of the Craftable ecosystem — see README.md.
## Layout
- `src/AdminAuthServiceProvider.php` — config, views, translations, routes; adds `CanAdmin` +
`ApplyUserLocale` to the `admin` middleware group and the `guest.admin` alias; binds the custom
exception handler.
- `src/Http/Controllers/Auth/` — login, forgot/reset password, activation, activation e-mail.
- `src/Traits/` — admin-guard versions of Laravel's auth traits (`AuthenticatesUsers`,
`ResetsPasswords`, `ThrottlesLogins`, …).
- `src/Activation/` — activation broker, token repository, notification
(toggle: `admin-auth.activation_enabled`).
- `src/Models/AdminUser.php` — soft deletes, Spatie roles/permissions, avatar media collection.
- `routes/admin.php`, `routes/activation-form.php` (loaded only when self-activation is enabled).
## Commands
Everything runs in Docker from the package root — never against a host PHP. The full,
copy-pasteable list (composer, every QA tool, both databases and
the "whole PHP suite" one-liner) is in **README.md → "How to develop this project"**.
The ones you need most:
```shell
docker compose run --rm test composer update
docker compose run --rm test ./vendor/bin/phpunit # MariaDB (default)
docker compose run --rm -e DB_CONNECTION=pgsql test ./vendor/bin/phpunit # PostgreSQL
docker compose run --rm php-qa phpcs -s --colors --extensions=php
docker compose run --rm php-qa phpcbf -s --colors --extensions=php # auto-fix style
docker compose run --rm php-qa phpstan analyse --configuration=phpstan.neon
docker compose run --rm php-qa phpmd analyze
docker compose run --rm php-qa phpcs --standard=.phpcs.compatibility.xml --cache=.phpcs.cache
docker compose run --rm php-qa composer normalize
```
A change is done when phpcs, phpstan, phpmd and the test suite are green.
## Code conventions
- PHP `^8.5`, Laravel 13. Every file starts with `declare(strict_types=1);`.
- **No Facades** — inject contracts through the constructor.
- **No helpers**, with these exceptions: `trans()` / `__()` are allowed everywhere; `app()` only in
models, traits and places where DI is genuinely hard to provide.
- Constructor property promotion. `final` classes and `readonly` wherever possible — prefer a
`final readonly class`, otherwise readonly properties. A readonly property is public rather than
hidden behind a getter.
- Always import with `use`; never inline `\Fully\Qualified\Names`.
- Alias the colliding `Repository` contracts:
`use Illuminate\Contracts\Config\Repository as Config;`,
`use Illuminate\Contracts\Cache\Repository as Cache;`.
- Name a property after its type: `TranslationImportService $translationImportService`, not `$service`.
- Build strings with `sprintf()` — no `"{$var}"` interpolation and no `.` concatenation.
- Mark overrides with `#[Override]` — **except** a method that overrides a *trait* method
(e.g. `HasFactory::newFactory()`): PHP 8.5.3 segfaults on that.
- Before adding a native type to an overriding property/parameter, check the parent. If the parent
is untyped (Laravel's `$fillable`, `$hidden`, a command's `$description`, …) the child must stay
untyped too.
- Fix new phpstan/phpmd findings in code. Baselines are for accepted, existing debt only — inspect
the baseline diff before committing it.
## Testing conventions
- PHPUnit 13 + Orchestra Testbench 11. Test namespaces mirror `src/`.
- Several tested methods of one class → a directory named after the class with one
`<Method>Test.php` per method.
- Feature tests when several real classes collaborate; Unit tests for isolated logic (mock the
rest). Don't write tests for service providers or install commands.
- PHPUnit assertions are static: `self::assert*()`. Laravel's instance assertions
(`$this->assertDatabaseHas()`, response asserts) stay on `$this`.
- Resolve services with `$this->app->make()`, never `app()`.
- Test-only models and stubs live in the `tests/` root.
## Package notes
- Tests run every flow twice: `AdminUserTestCase` (admin guard) and `UserTestCase` (default
guard). A behaviour change usually needs both covered.
- Config keys consumers rely on live in `config/admin-auth.php` (`defaults`, `activation_enabled`,
`self_activation_form_enabled`, redirects, `use_routes`) — renaming one is a breaking change.
## Versioning
The package is on **2.x** and stays there through the Laravel 13 / PHP 8.5 upgrade — don't add
v3 upgrade sections or bump the `branch-alias`. User-facing changes go to `UPGRADE.md` when
consumers have to act.
Admin authentication for Craftable admin panels: login/logout, password reset and optional
account activation for the admin guard. Composer dejwcake/admin-auth, namespace
Brackets\AdminAuth (fork of brackets/admin-auth). Part of the Craftable ecosystem — see README.md.
src/AdminAuthServiceProvider.php — config, views, translations, routes; adds CanAdmin +
ApplyUserLocale to the admin middleware group and the guest.admin alias; binds the custom
exception handler.src/Http/Controllers/Auth/ — login, forgot/reset password, activation, activation e-mail.src/Traits/ — admin-guard versions of Laravel's auth traits (AuthenticatesUsers,
ResetsPasswords, ThrottlesLogins, …).src/Activation/ — activation broker, token repository, notification
(toggle: admin-auth.activation_enabled).src/Models/AdminUser.php — soft deletes, Spatie roles/permissions, avatar media collection.routes/admin.php, routes/activation-form.php (loaded only when self-activation is enabled).Everything runs in Docker from the package root — never against a host PHP. The full, copy-pasteable list (composer, every QA tool, both databases and the "whole PHP suite" one-liner) is in README.md → "How to develop this project". The ones you need most:
docker compose run --rm test composer update
docker compose run --rm test ./vendor/bin/phpunit # MariaDB (default)
docker compose run --rm -e DB_CONNECTION=pgsql test ./vendor/bin/phpunit # PostgreSQL
docker compose run --rm php-qa phpcs -s --colors --extensions=php
docker compose run --rm php-qa phpcbf -s --colors --extensions=php # auto-fix style
docker compose run --rm php-qa phpstan analyse --configuration=phpstan.neon
docker compose run --rm php-qa phpmd analyze
docker compose run --rm php-qa phpcs --standard=.phpcs.compatibility.xml --cache=.phpcs.cache
docker compose run --rm php-qa composer normalize
A change is done when phpcs, phpstan, phpmd and the test suite are green.
^8.5, Laravel 13. Every file starts with declare(strict_types=1);.trans() / __() are allowed everywhere; app() only in
models, traits and places where DI is genuinely hard to provide.final classes and readonly wherever possible — prefer a
final readonly class, otherwise readonly properties. A readonly property is public rather than
hidden behind a getter.use; never inline \Fully\Qualified\Names.Repository contracts:
use Illuminate\Contracts\Config\Repository as Config;,
use Illuminate\Contracts\Cache\Repository as Cache;.TranslationImportService $translationImportService, not $service.sprintf() — no "{$var}" interpolation and no . concatenation.#[Override] — except a method that overrides a trait method
(e.g. HasFactory::newFactory()): PHP 8.5.3 segfaults on that.$fillable, $hidden, a command's $description, …) the child must stay
untyped too.src/.<Method>Test.php per method.self::assert*(). Laravel's instance assertions
($this->assertDatabaseHas(), response asserts) stay on $this.$this->app->make(), never app().tests/ root.AdminUserTestCase (admin guard) and UserTestCase (default
guard). A behaviour change usually needs both covered.config/admin-auth.php (defaults, activation_enabled,
self_activation_form_enabled, redirects, use_routes) — renaming one is a breaking change.The package is on 2.x and stays there through the Laravel 13 / PHP 8.5 upgrade — don't add
v3 upgrade sections or bump the branch-alias. User-facing changes go to UPGRADE.md when
consumers have to act.
How can I help you explore Laravel packages today?