backend-models

Create standards-compliant Blueprint and Amber schema designs for the StockX platform.

Updated Dec 20, 2025
One-click install
npx skills add https://github.com/sulhicmz/jasaweb --skill backend-models-sulhicmz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend-models
Source: https://github.com/sulhicmz/jasaweb/tree/main/.opencode/skills/backend-models
Command: npx skills add https://github.com/sulhicmz/jasaweb --skill backend-models-sulhicmz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a comprehensive guide for designing and enforcing robust database models with clear naming conventions, appropriate data types, constraints, and relationships to ensure data integrity across the JasaWeb architecture.

Core Features & Use Cases

  • Establishing consistent naming conventions for models and tables (singular model names, plural table names) to reduce ambiguity.
  • Enforcing data type guidelines, constraints, and cascade relationship patterns to ensure data integrity and predictable behavior.
  • Providing testing patterns and integration rules to validate models and relationships across services.
  • Use Case: When adding a new domain entity, follow these standards to generate a Prisma schema, define relationships, and implement necessary constraints.

Quick Start

Create a Prisma model for a new domain entity following the naming conventions, data types, and constraints described above.

Frequently Asked Questions about backend-models

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

FAQPage Schema
How do I define database models and constraints in Prisma to ensure data integrity?

You define database models by applying singular model names, plural table names, appropriate data types, and cascade relationship patterns. This approach ensures data integrity and predictable behavior across your architecture through enforced validation and indexing standards.

What naming conventions should I use for ORM database models and table mapping?

For ORM database models, use singular model names and plural table names. This convention reduces ambiguity and establishes clear mapping between your ORM classes and underlying database tables.

How do I test Prisma schema relationships and constraints effectively?

Testing Prisma schema relationships involves implementing specific integration rules and validation patterns. These testing patterns validate database models and verify that constraints and relationships function correctly across services.

Can I use this guide for modifying existing ORM classes and data model relationships?

Yes, this guide applies to modifying existing ORM classes and data model relationships. It supports creating and modifying Prisma schemas, defining relationships, and implementing necessary constraints when updating domain entities.

What cascade relationship patterns should I apply when adding a new domain entity?

When adding a new domain entity, apply cascade relationship patterns that ensure data integrity and predictable behavior. These patterns define how foreign keys and relationships handle deletions and updates across connected database models.