ワンクリックで
factory-contract-system
Ensures factories generate valid model instances aligned with database schema constraints
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Ensures factories generate valid model instances aligned with database schema constraints
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Ensures correct execution order of migrations, seeders, and tests in CI
Defines DTO structure, lifecycle, and transformation rules across the application
Handles Filament multi-tenancy: tenant scoping, TenantAware trait, observer behaviour, isScopedToTenant, and tenant switching. Activates when adding tenant-aware models, fixing company_id scoping, working with Filament::getTenant, debugging tenant isolation, or when the user mentions company scope, tenant, multi-tenancy, or company_id.
Configures Filament panel providers. Activates when adding a new panel, registering module resources in a panel, configuring tenant middleware, adjusting auth or theme settings, or when the user mentions PanelProvider, viteTheme, discoverResources, or panel configuration.
Defines the Filament v4 resource page structure used in this project: Resource + Pages + Schemas + Tables split, action patterns, and BaseResource conventions.
Creates and modifies code inside a modular Laravel structure. Targets internachi/modular (modules as real Composer packages with src/). Activates when adding a new module, adding a model/factory/migration/resource/service to an existing module, registering a module with Filament, or when the user mentions modules, modular, or a specific module name.
| name | factory-contract-system |
| description | Ensures factories generate valid model instances aligned with database schema constraints |
Ensures factories produce valid database-ready model instances.
Factories MUST:
Factories do NOT:
If a migration introduces a NOT NULL column:
Each factory represents the smallest valid persisted entity.
Not random data. Not business scenarios. Only valid schema state.
Factories SHOULD align with service-layer expectations but do NOT depend on it.
Service layer = behavior Factory = valid structure
Seeders depend on factories.
Factories MUST NOT depend on seeders.