backend-datamodels

Define and validate Drumr Framework backend data models with fields, relationships, and permissions.

Updated Sep 16, 2025
One-click install
npx skills add https://github.com/slingr-stack/qa-test-drumr --skill backend-datamodels
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend-datamodels
Source: https://github.com/slingr-stack/qa-test-drumr/tree/main/project-management-app/.agents/skills/backend-datamodels
Command: npx skills add https://github.com/slingr-stack/qa-test-drumr --skill backend-datamodels

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you define consistent, production-ready backend data models for Drumr Framework so entities, fields, relationships, validation, and persistence rules stay aligned with the application’s domain logic.

Core Features & Use Cases

  • Entity and Field Design: Model text, choice, date, numeric, reference, and composition fields with clear typing and business-driven constraints.
  • Lifecycle and Behavior: Add validation, calculated fields, indexing, optimistic locking, and save-time hooks where the domain needs them.
  • Access and Exposure: Prepare models for CRUD usage by registering permissions and keeping backend schema concerns separate from frontend presentation.
  • Use Case: Build a customer, order, or project model with the right primary key, relationships, and validation rules before wiring it into APIs and workflows.

Quick Start

Ask the skill to design a Drumr backend data model for your feature, including the entity fields, relationships, validation rules, primary key, and required permissions.

Frequently Asked Questions about backend-datamodels

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

FAQPage Schema
How do I define backend data models with TypeScript validation and schema relationships?

Backend data models are defined using the @DataModel decorator and BaseDataModel inheritance, with unified field decorators for typing, relationships, validation rules, and a required primary key.

What is the best way to structure entity fields and relationships for a backend schema?

The best way to structure entity fields is by modeling text, choice, date, numeric, and reference fields with clear typing, while using composition fields and relationship decorators to maintain domain-driven constraints.

How do I add lifecycle hooks and calculated fields to a backend data model?

Lifecycle hooks and calculated fields are added directly within the data model definition to handle save-time validation, optimistic locking, and indexing where the domain logic requires dynamic behavior.

Do I need to register permissions for CRUD operations on backend data models?

Yes, you must register permissions for any API-exposed backend data model to ensure proper CRUD access control and keep backend schema concerns separate from frontend presentation layers.

Does the Drumr Framework require a primary key for every backend data model?

Yes, the Drumr Framework requires every backend data model to define a primary key using the @DataModel decorator and BaseDataModel inheritance to support persistence and CRUD operations.

When should I not use calculated fields in backend schema design?

Calculated fields should not be used when the domain logic requires static persistence, as they introduce dynamic save-time behavior and validation hooks that may conflict with straightforward entity field storage.