vendix-backend-domain

Organize Vendix backend into domain-based modules with NestJS and Prisma.

5|Updated Aug 23, 2025

Search Tags:#backend #prisma #nestjs #domain-driven #hexagonal-architecture #multitenancy #domain-modules

Ready to run

npx skills add https://github.com/Rzyfront/Vendix --skill vendix-backend-domain

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: vendix-backend-domain
Source: https://github.com/Rzyfront/Vendix/tree/main/skills/vendix-backend-domain
Command: npx skills add https://github.com/Rzyfront/Vendix --skill vendix-backend-domain

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured blueprint for organizing a Vendix backend into domain-based modules, clarifying responsibilities, boundaries, and multi-tenancy considerations.

Core Features & Use Cases

Domain-driven module pattern for auth, organization, store, ecommerce, and common areas.
Controller, service templates, and multi-tenant context via RequestContextService.
Clear guidance on app_type and domain resolution within the domain structure to support scalable growth.

Quick Start

Review apps/backend/src/domains and begin implementing new domain modules (auth, organization, store, ecommerce) following the prescribed Module/Controller/Service templates.

Frequently Asked Questions about vendix-backend-domain

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I structure a NestJS backend with domain-driven modules?▼

You structure a NestJS backend with domain-driven modules by organizing code into specific domain folders like auth, organization, store, and ecommerce. This pattern uses prescribed Module, Controller, and Service templates to enforce clear boundaries and support scalable growth.

What is the best way to implement multi-tenancy in a Prisma and NestJS backend?▼

Implementing multi-tenancy in a Prisma and NestJS backend is handled through a RequestContextService. This service manages multi-tenant context within domain modules, ensuring data isolation across different organizations using the domain structure.

How does hexagonal architecture apply to backend domain modules?▼

Hexagonal architecture applies to backend domain modules by defining clear boundaries that separate core domain logic from external infrastructure. This blueprint uses structured domain folders with dedicated controllers and services to enable a scalable domain resolution strategy.

Can I use this domain module pattern for an existing ecommerce backend?▼

You can apply this domain module pattern to an existing ecommerce backend. Review the apps/backend/src/domains directory and begin implementing new domain modules following the prescribed Module, Controller, and Service templates to clarify responsibilities and boundaries.

How do I handle app_type and domain resolution in a multi-tenant backend?▼

You handle app_type and domain resolution in a multi-tenant backend by applying specific semantics within the domain structure. This blueprint provides clear guidance on configuring app_type and domain resolution to support scalable multi-tenant growth.