negosyohub-core

What problem does it solve?

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.

Core Features & Use Cases

• Cross-sector architecture guardrails: Ensures changes that affect multiple domains are audited and implemented additively instead of rebuilding or duplicating existing systems.
• Multi-tenant data isolation discipline: Reinforces scoping shared logic by store_id and preserving authorization boundaries across customer, store, and admin contexts.
• Workflow- and state separation: Helps keep order_status, payment_status, and delivery_status distinct to avoid corrupting lifecycle semantics.
• Documentation synchronization via PHASING: Guides you to update PHASING.md when features move between not implemented, partial, and complete status.
• Testing and security expectations: Encourages backend Pest and SPA Vitest coverage for shared changes and highlights security-sensitive areas (validation, serialization, mass assignment, token/session behavior).

Quick Start

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."