Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

vendra-api-development

Estrelas1

Forks0

Atualizado16 de julho de 2026 às 21:36

Use this skill when creating, modifying, reviewing, or testing the Vendra API infrastructure module in packages/vendra-api. Trigger for shared JSON:API filters, sorters, reusable query building blocks, and API service-provider wiring consumed by the per-domain vendra-*-api modules.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

misaf

misaf/vendra

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	vendra-api-development
description	Use this skill when creating, modifying, reviewing, or testing the Vendra API infrastructure module in packages/vendra-api. Trigger for shared JSON:API filters, sorters, reusable query building blocks, and API service-provider wiring consumed by the per-domain vendra-*-api modules.

Vendra API

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 when tests are added or changed. Before code changes, use Laravel Boost application-info and search-docs for Laravel JSON:API.

Module Boundary

Treat packages/vendra-api as shared JSON:API infrastructure, not a domain API.

Use namespace Misaf\VendraApi.
Keep only cross-cutting, reusable JSON:API building blocks here: JsonApi/Filters, JsonApi/Sorting, and API service-provider wiring.
Do not add domain schemas, resources, routes, or servers here — those live in the per-domain API modules (vendra-faq-api, vendra-product-api, vendra-multimedia-api, vendra-blog-api, vendra-custom-page-api).
Keep all API packages localization-package agnostic: do not require misaf/vendra-localization or attach vendra.locale; the host application owns optional locale resolution.
Never depend on a domain module or a concrete tenant provider (Misaf\VendraTenant); this package must build and run standalone and tenant-agnostic.

Standards

Keep filters and sorters generic and resource-type agnostic so any domain API can reuse them.
Follow Laravel comment style: PHPDoc with array shapes and generics; inline comments only for genuinely complex logic.
Keep public class and method signatures stable — these are consumed by every domain API module.

Testing And Verification

Keep tests purposeful: cover filter/sorter behavior and edge cases, not framework internals.
Keep Pest architecture tests in tests/ArchTest.php: the php, security, and laravel presets, plus arch()->expect('Misaf\VendraApi')->not->toUse('Misaf\VendraTenant').
Run module checks: composer --working-dir=packages/vendra-api test and composer --working-dir=packages/vendra-api analyse.
If PHP files changed, run vendor/bin/pint --dirty --format agent.

Mais deste repositório

mesmo repositório

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-testing-development

misaf/vendra

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.

2026-07-201

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

name	vendra-api-development
description	Use this skill when creating, modifying, reviewing, or testing the Vendra API infrastructure module in packages/vendra-api. Trigger for shared JSON:API filters, sorters, reusable query building blocks, and API service-provider wiring consumed by the per-domain vendra-*-api modules.

Vendra API

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.

Module Boundary

Treat packages/vendra-api as shared JSON:API infrastructure, not a domain API.

Use namespace Misaf\VendraApi.
Keep only cross-cutting, reusable JSON:API building blocks here: JsonApi/Filters, JsonApi/Sorting, and API service-provider wiring.
Do not add domain schemas, resources, routes, or servers here — those live in the per-domain API modules (vendra-faq-api, vendra-product-api, vendra-multimedia-api, vendra-blog-api, vendra-custom-page-api).
Keep all API packages localization-package agnostic: do not require misaf/vendra-localization or attach vendra.locale; the host application owns optional locale resolution.
Never depend on a domain module or a concrete tenant provider (Misaf\VendraTenant); this package must build and run standalone and tenant-agnostic.

Standards

Keep filters and sorters generic and resource-type agnostic so any domain API can reuse them.
Follow Laravel comment style: PHPDoc with array shapes and generics; inline comments only for genuinely complex logic.
Keep public class and method signatures stable — these are consumed by every domain API module.

Testing And Verification

Keep tests purposeful: cover filter/sorter behavior and edge cases, not framework internals.
Keep Pest architecture tests in tests/ArchTest.php: the php, security, and laravel presets, plus arch()->expect('Misaf\VendraApi')->not->toUse('Misaf\VendraTenant').
Run module checks: composer --working-dir=packages/vendra-api test and composer --working-dir=packages/vendra-api analyse.
If PHP files changed, run vendor/bin/pint --dirty --format agent.