skills/vendix-backend-domain/SKILL.md
Backend domain architecture for Vendix: domains/* organization, flat namespaced controllers, scoped Prisma services, global guards/interceptors, and shared-service module ownership. Trigger: When working on backend domains.
npx skillsauth add rzyfront/vendix vendix-backend-domainInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
apps/backend/src/domains/apps/backend/src/app.module.tsapps/backend/src/prisma/services/Vendix backend is organized by domain folders such as auth, organization, store, ecommerce, superadmin, and public.
Controllers use flat namespaced routes like store/..., organization/..., superadmin/..., and public/...; current tenancy does not depend on route params like domains/:domain_id/....
Domain services run under:
JwtAuthGuardStoreOperationsGuardRequestContextInterceptorUnderstand these layers before adding manual tenant/auth logic.
If a shared service is exported by another module, import the owning module instead of duplicating the provider in your module. This avoids dependency drift when shared services gain new dependencies.
vendix-backendvendix-backend-apivendix-prisma-scopesvendix-backend-middlewaredevelopment
Mobile app development rules for Vendix Expo/React Native project. Trigger: When editing, creating, or modifying any file under apps/mobile, or when developing mobile-specific features.
development
Feature gating by store subscription state: global store write guard, AI feature gate, Redis feature resolution, quota consumption, frontend paywall interceptor, banner, and subscription UI states. Trigger: When adding feature gates, paywalls, subscription-based access control, protecting store write operations, AI feature gates, or rollout flags.
testing
SaaS subscription billing for Vendix stores: plan pricing, invoices, Wompi platform payments, manual payments, partner commissions, payouts, proration, and dunning. Trigger: When creating SaaS invoices, working with partner rev-share, margin/surcharge pricing, invoice sequence allocation, partner payout batches, subscription payments, manual payments, or dunning flows.
development
Periodic quota counters with Redis, UTC period keys, Lua-based idempotent AI quota consumption, request-id deduplication, and post-success consumption. Trigger: When building quota counters, enforcing monthly/daily feature caps, or reusing AI quota patterns for uploads, emails, exports, or rate-limited features.