Package development in Bagisto. Activates when creating packages, migrations, models, repositories, routes, controllers, views, localization, DataGrid, menus, ACL, or system configuration. Use references to skills for specific areas: @core, @data, @ui, @features.
Admin theme development in Bagisto. Activates when creating custom admin themes, modifying admin layouts, building admin theme packages, or working with admin panel styling and interface customization.
Blade template conventions for any Bagisto package or module (Admin, Shop, or any custom Webkul-style package). Activates when creating or editing Blade views, building Blade components (anonymous @props components or Vue-backed x-template components), wiring forms, datagrids, modals, layouts, or slots, or matching the project's markup, attribute-binding, indentation, and formatting style. The conventions are framework-wide; only the per-package namespace tokens differ.
Shop theme development in Bagisto. Activates when creating custom storefront themes, modifying shop layouts, building theme packages, or working with Vite-powered assets for the customer-facing side of the application.
Payment gateway development in Bagisto. Activates when creating payment methods, integrating payment gateways like Stripe, PayPal, or any third-party payment processor; or when the user mentions payment, payment gateway, payment method, Stripe, PayPal, or needs to add a new payment option to the checkout.
Tests applications using the Pest 3 PHP framework in Bagisto. Activates when writing tests, creating unit or feature tests, adding assertions, testing Livewire components, architecture testing, debugging test failures, working with datasets or mocking; or when the user mentions test, spec, TDD, expects, assertion, coverage, or needs to verify functionality works.
ALWAYS use when building an ADMIN app or UI on the Bagisto Admin API — a back-office dashboard, order/catalog/customer/marketing/CMS/settings management screen, an admin mobile app, the Create-Order flow, or ANY admin panel page on the API. Also when the user mentions admin orders, products, customers, cart rules, CMS, settings, reporting, or 'admin panel on the API'. Routes each menu to a reference page; asks the client's platform/stack first; treats the api-docs as the source of truth for exact shapes.
Use when working INSIDE the bagisto-api package — installing or removing it, adding/changing a REST or GraphQL endpoint or resource, building an admin menu's API, or fixing package behaviour. Also when the user mentions ApiResource, Provider, Processor, DTO, resolver, 'install/remove the bagisto-api package', or 'add/extend an endpoint'. Install/remove happen only on explicit request, never automatically. Reference files live in reference/: install, uninstall, structure, api-structure, conventions, precautions, limitations, testing.