Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

vendra-testing-development

Estrellas1

Forks0

Actualizado20 de julio de 2026 a las 13:38

Use this skill when creating, modifying, reviewing, or testing the Vendra Testing utilities module in packages/vendra-testing. Trigger for shared Pest Expectations, TranslationParity helpers, and other reusable test scaffolding consumed by other Vendra module test suites.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

misaf

misaf/vendra

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Analistas de garantía de calidad de software y probadoresOcupaciones informáticas y matemáticas·SOC 15-1253

SKILL.md

readonly

name	vendra-testing-development
description	Use this skill when creating, modifying, reviewing, or testing the Vendra Testing utilities module in packages/vendra-testing. Trigger for shared Pest Expectations, TranslationParity helpers, and other reusable test scaffolding consumed by other Vendra module test suites.

Vendra Testing

Workflow

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.

Always use this skill together with laravel-best-practices for Laravel PHP and pest-testing for test conventions. Before code changes, use Laravel Boost application-info and search-docs.

Module Boundary

Treat packages/vendra-testing as shared, module-agnostic test utilities.

Use namespace Misaf\VendraTesting.
Own reusable Pest expectations and helpers (Expectations, TranslationParity) here.
Own the provider-agnostic helpers in src/Helpers.php (files-autoloaded): testTenantModel(), createTestTenant(), makeCurrentTestTenant(), switchToTestTenant(), currentTestTenant(), forgetCurrentTestTenant() (via the misaf/vendra-support TenantResolver / TenantAwareness contracts) and testUserModel() / createTestUser() (via auth.providers.users.model). They no-op (returning null) when tenancy is disabled.
Module test suites must use these helpers instead of importing Misaf\VendraTenant; only vendra-tenant and vendra-subscription tests may import the concrete provider (enforced by the root PackageManifestConsistencyTest).
Keep utilities generic: no dependency on a specific domain module and no concrete tenant provider reference (Misaf\VendraTenant). misaf/vendra-support is the one sanctioned dependency.
Keep cross-module dependencies explicit in composer.json.

Utility Standards

Keep custom expectations composable and well-named so consuming suites read clearly.
Keep translation-parity and key-sorting helpers deterministic and locale-order independent.
Treat helper signatures as a public contract; deprecate rather than break when evolving them.

Testing And Verification

Cover the utilities themselves with focused tests where behavior is non-trivial (e.g. key-sorting comparison logic).
Keep Pest architecture tests in tests/ArchTest.php: the php, security, and laravel presets, plus arch()->expect('Misaf\VendraTesting')->not->toUse('Misaf\VendraTenant').
Run module checks: composer --working-dir=packages/vendra-testing test and composer --working-dir=packages/vendra-testing analyse.
If PHP files changed, run vendor/bin/pint --dirty --format agent.

Más de este repositorio

mismo repositorio

vendra-subscription-development

misaf/vendra

Use this skill when creating, modifying, reviewing, or testing the Vendra Subscription module in packages/vendra-subscription — a generic, subscriber-agnostic subscription engine. Trigger for the Plan and Subscription models, PeriodUnit/SubscriptionStatus enums, PlanInUseException/SubscriptionPaymentException, plan pricing/trials/entitlements, subscription scopes and lifecycle state, the subscriber_id decoupling, and subscription service-provider wiring. NOT for Reseller, quota, provisioning, PlanSeeder, or reseller actions/notifications — those live in the host app.

2026-07-221

vendra-tenant-development

misaf/vendra

Use this skill when creating, modifying, reviewing, or testing the Vendra Tenant provider module in packages/vendra-tenant. Trigger for the Tenant / TenantDomain models, VendraTenantResolver, DomainTenantFinder, SwitchAppTask / SwitchMailTask, TenantPlugin, TenantServiceProvider, EnableTenancyAction, the vendra-tenant:enable command, TenantTableRegistry schema retrofits, Spatie multitenancy wiring, and the TenantResolver binding that enables tenant awareness.

2026-07-221

vendra-support-development

misaf/vendra

Use this skill when creating, modifying, reviewing, or testing the Vendra Support module in packages/vendra-support, changing tenant awareness, optional capability resolvers, or shared Filament sidebar navigation. Trigger for TenantResolver, TagResolver, TagIntegration, NullTenantResolver, TenantAwareness, BelongsToTenant, TenantScope, TeamScope, TenantSchema, TenantTableRegistry, RequiresCurrentTenant, TenantSeeders, shared seeders and commands, Filament NavigationGroup taxonomy, navigation groups, package sidebar priority, package icons, clusters, sub-navigation, shared Filament concerns, shared events/listeners, ResolvesPolicyPermissions, the composable policy ability traits (Authorizes*Abilities), and permission policy enum conventions.

2026-07-211

vendra-address-development

misaf/vendra

Create, modify, review, or test the optional Vendra Address provider in packages/vendra-address, including international user-profile addresses, migrations, models, factories, and Filament relation management.

2026-07-191

vendra-attribute-development

misaf/vendra

Create, modify, review, or test the Vendra Attribute package in packages/vendra-attribute. Use for Attribute, AttributeValue, AttributableModel, HasAttributeValues, AttributeResolver wiring, configurable units, optional attribute tags, migrations, factories, policies, Filament resources and relation managers, translations, and package registration.

2026-07-191

vendra-authify-log-development

misaf/vendra

Create, modify, review, or test the Vendra Authify Log package in packages/vendra-authify-log. Use for AuthifyLog records, Redis-buffered authentication logging, drain commands, authentication listeners and notifications, policies, Filament resources and filters, configuration, translations, package wiring, and tests.

2026-07-191

name	vendra-testing-development
description	Use this skill when creating, modifying, reviewing, or testing the Vendra Testing utilities module in packages/vendra-testing. Trigger for shared Pest Expectations, TranslationParity helpers, and other reusable test scaffolding consumed by other Vendra module test suites.

Vendra Testing

Workflow

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.

Always use this skill together with laravel-best-practices for Laravel PHP and pest-testing for test conventions. Before code changes, use Laravel Boost application-info and search-docs.

Module Boundary

Treat packages/vendra-testing as shared, module-agnostic test utilities.

Use namespace Misaf\VendraTesting.
Own reusable Pest expectations and helpers (Expectations, TranslationParity) here.
Own the provider-agnostic helpers in src/Helpers.php (files-autoloaded): testTenantModel(), createTestTenant(), makeCurrentTestTenant(), switchToTestTenant(), currentTestTenant(), forgetCurrentTestTenant() (via the misaf/vendra-support TenantResolver / TenantAwareness contracts) and testUserModel() / createTestUser() (via auth.providers.users.model). They no-op (returning null) when tenancy is disabled.
Module test suites must use these helpers instead of importing Misaf\VendraTenant; only vendra-tenant and vendra-subscription tests may import the concrete provider (enforced by the root PackageManifestConsistencyTest).
Keep utilities generic: no dependency on a specific domain module and no concrete tenant provider reference (Misaf\VendraTenant). misaf/vendra-support is the one sanctioned dependency.
Keep cross-module dependencies explicit in composer.json.

Utility Standards

Keep custom expectations composable and well-named so consuming suites read clearly.
Keep translation-parity and key-sorting helpers deterministic and locale-order independent.
Treat helper signatures as a public contract; deprecate rather than break when evolving them.

Testing And Verification

Cover the utilities themselves with focused tests where behavior is non-trivial (e.g. key-sorting comparison logic).
Keep Pest architecture tests in tests/ArchTest.php: the php, security, and laravel presets, plus arch()->expect('Misaf\VendraTesting')->not->toUse('Misaf\VendraTenant').
Run module checks: composer --working-dir=packages/vendra-testing test and composer --working-dir=packages/vendra-testing analyse.
If PHP files changed, run vendor/bin/pint --dirty --format agent.