원클릭으로
test-honesty
Ensures factory, seeder, and schema alignment with production database reality
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Ensures factory, seeder, and schema alignment with production database reality
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 | test-honesty |
| description | Ensures factory, seeder, and schema alignment with production database reality |
Prevents schema drift between migrations, factories, and seeders.
Every NOT NULL column defined in migrations must be supported by:
This is a schema-only rule, not a validation rule.
Factories MUST produce valid database rows for the schema.
Factories are schema-aligned, not business-logic aware.
Seeders MUST only insert schema-valid data.
No reliance on implicit database defaults.
MySQL / MariaDB is the canonical database.
SQLite differences are invalid for schema validation assumptions.
The following indicate schema drift:
Primary keys are non-deterministic.
Tests MUST NOT rely on hardcoded IDs.
Schema validation requires:
before running test suites.
This ensures schema correctness before test execution.