Save this content to: .claude/skills/vendra-address-development/SKILL.md

# Vendra Address

## Workflow

- Inspect `composer.json`, sibling files, and existing tests before changing the package.
- Use Laravel Boost `application-info` and `search-docs` before code changes.
- Apply `laravel-best-practices` to Laravel PHP and `pest-testing` whenever tests change.
- Apply `tailwindcss-development` only when changing Blade markup or Tailwind classes.
- Keep changes inside this package's boundary and preserve its public contracts.
- Add or update focused Pest coverage, then run `php artisan test --compact --testsuite=vendra-address` and `composer stan`.

## Translatable Persistence

- Making a persisted model field translatable is an explicit domain choice unless this package already requires it.
- Every field listed in a model's `$translatable` array must definitely use a JSON database column. Keep its model traits/casts, factories, validation, Filament locale UI, API serialization, and tests translation-aware.
- A field not listed in `$translatable` must use the appropriate scalar database type and must not use Spatie Translatable, translatable slug traits, locale switchers, translated callbacks, or translation-shaped array data.

## Vendra Transitive API Policy

- Treat a Vendra dependency intentionally exposed through the public API of a directly required Vendra platform package as part of the supported public contract of that package.
- Do not add a redundant direct Composer requirement solely because source code imports a type from that exposed dependency.
- Apply this only to Vendra platform packages listed under `require`; never extend it to `require-dev`, `suggest`, incidental implementation dependencies, or third-party packages. Removing or replacing an exposed dependency is a breaking change; keep `self.version` alignment across the Vendra package graph.

- Register every table whose migration calls `TenantSchema::addTenantColumn()` with `TenantTableRegistry` in this package's service provider, preserving configured table names and connections, so `vendra-tenant:enable {tenant}` can retrofit schemas migrated before tenancy was enabled.

- Keep this package independently installable and coupled only one-way to `vendra-user-profile`.
- Register `addresses` dynamically and contribute UI through `UserProfileRelationManagers`; User Profile must never import this package.
- Keep `AddressPolicy`, `AddressPolicyEnum`, and `PermissionPolicySeeder` aligned for Filament strict authorization.
- Model international addresses with ISO country code and generic locality/administrative fields. Put country-specific structured fields in JSON metadata.
- Do not mark address fields translatable unless explicitly added to `$translatable`; otherwise use scalar columns and normal Filament inputs.
- Store no concrete tenant provider references; tenant ownership comes from Vendra Support.
- Keep exactly one default address (`is_default`) per user profile through the synchronous `Observers\AddressObserver`, which uses vendra-support's `MaintainsSingleFlagPerOwner`; the `default_profile_guard` unique index backs it in the database.