smithery/rzyfront

vendix-backend-domain

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.

Installation

$ npx skills add smithery/rzyfront --skill vendix-backend-domain

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/rzyfront · top by installs.

npx skills add smithery/rzyfront

Browse all from smithery/rzyfront

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Version2.0
LicenseMIT
More metadata
author
rzyfront
version
2.0
scope
["root"]
auto_invoke
Working on backend domains

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,518 B
  • docs SUMMARY.md 73 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Vendix Backend Domain

Source of Truth

  • apps/backend/src/domains/
  • apps/backend/src/app.module.ts
  • apps/backend/src/prisma/services/

Current Architecture

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

Cross-Cutting Runtime

Domain services run under:

  • global JwtAuthGuard
  • global StoreOperationsGuard
  • RequestContextInterceptor
  • scoped Prisma services and AsyncLocalStorage request context

Understand these layers before adding manual tenant/auth logic.

Shared Service Ownership Rule

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.

Related Skills

  • vendix-backend
  • vendix-backend-api
  • vendix-prisma-scopes
  • vendix-backend-middleware