Audit shared Laravel and Vue changes for multi-tenant consistency.
npx skills add https://github.com/doedoe123-boop/negosyohub --skill negosyohub-core
Please help me install this Agent Skill. Skill: negosyohub-core Source: https://github.com/doedoe123-boop/negosyohub/tree/main/skills/negosyohub-core Command: npx skills add https://github.com/doedoe123-boop/negosyohub --skill negosyohub-core
It prevents architecture regressions and cross-sector inconsistencies when you modify shared multi-tenant marketplace behavior such as auth, payments, orders, notifications, or shared UI/API contracts.
store_id and preserving authorization boundaries across customer, store, and admin contexts.order_status, payment_status, and delivery_status distinct to avoid corrupting lifecycle semantics.PHASING.md when features move between not implemented, partial, and complete status.Use the negosyohub-core skill when changing shared Laravel/Vue infrastructure or multi-tenant flows, then ask: "Review my proposed change plan for shared architecture, multi-tenant scoping, API/UI compatibility, PHASING updates, and the exact tests I should add before I implement it."
High-intent search queries and answers about installing and using this skill.
To safely modify shared multi-tenant marketplace infrastructure, audit existing implementations and apply changes additively. This preserves tenant isolation by scoping logic with store_id and prevents cross-sector inconsistencies in shared Laravel or Vue systems.
Keeping order_status, payment_status, and delivery_status separated requires workflow and state separation discipline. You must maintain distinct lifecycle semantics during shared infrastructure changes to avoid corrupting state transitions across tenant contexts.
Yes, you need backend Pest and SPA Vitest coverage when changing shared multi-tenancy payments or auth flows. Testing shared changes validates that tenant isolation, authorization boundaries, and API contracts remain intact across sectors.
To prevent mass assignment and token session vulnerabilities in a multi-tenant Laravel application, follow security review expectations. You must carefully audit validation, serialization, and authorization boundaries across customer, store, and admin contexts.
You should always audit existing implementations before modifying shared APIs and UI contracts. Auditing ensures you preserve existing response conventions and implement changes additively, preventing architecture regressions across multi-tenant sectors.
callcocamAudit Laravel migrations for multi-tenant issues and generate severity-ordered reports.
pphatdevAutomate Laravel/Pest backend and Nuxt/Vitest frontend tests for multi-tenant ERP.
ducnm-mimhusIdentify security patterns for authentication, authorization, IDOR, PII, and webhook verification.
prof-danielcRun static analysis tools and aggregate results into a prioritized issue report.