conventions

Enforce naming conventions and architectural patterns for NestJS and Prisma projects.

Updated Dec 26, 2025
One-click install
npx skills add https://github.com/JoyanLabs/template-nestjs-dashboard-better_auth --skill conventions-joyanlabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: conventions
Source: https://github.com/JoyanLabs/template-nestjs-dashboard-better_auth/tree/main/skills/conventions
Command: npx skills add https://github.com/JoyanLabs/template-nestjs-dashboard-better_auth --skill conventions-joyanlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Establishes and enforces consistent naming conventions and architectural patterns across the template backend to reduce confusion and improve maintainability.

Core Features & Use Cases

  • Naming conventions for Prisma models, tables, foreign keys, and fields to maintain alignment with the database schema.
  • Directory structure and ES module import practices to keep the codebase scalable and maintainable.
  • Git conventions, testing structure, and CQRS guidance to standardize collaboration and quality across teams.

Quick Start

Align new files, models, and modules with the project's naming conventions and documented patterns.

Frequently Asked Questions about conventions

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

FAQPage Schema
How do I enforce consistent naming conventions for Prisma models and NestJS modules?

This standardization establishes rules for models, tables, foreign keys, and fields, alongside directory layout and ES module import practices, reducing confusion and improving backend maintainability across teams.

What are the best practices for structuring CQRS and Git conventions in a NestJS backend?

Best practices for structuring CQRS and Git conventions involve standardizing your testing structure, governance practices, and architectural patterns to maintain alignment and quality across your collaborative development workflow.

Does this coding standard template work with existing Prisma schema migrations?

Yes, this coding standard template applies when adding new Prisma models, entities, or files, ensuring your naming rules for tables and relations align consistently with your existing database schema.

How do I standardize ES module imports and directory structure for a scalable NestJS project?

To standardize ES module imports and directory structure, you enforce specific architectural patterns and directory layouts that keep your NestJS codebase scalable, organized, and maintainable during team collaboration.

When do I need to apply backend naming conventions and architectural patterns?

You need to apply backend naming conventions and architectural patterns when adding new Prisma models, entities, or files, and when structuring contexts, modules, and imports in NestJS projects to ensure consistency.