cabloy-master-detail

Guide Cabloy master-detail and nested-detail backend scaffolding workflows.

970|131|Updated Jan 14, 2018
One-click install
npx skills add https://github.com/cabloy/cabloy --skill cabloy-master-detail
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cabloy-master-detail
Source: https://github.com/cabloy/cabloy/tree/main/.claude/skills/cabloy-master-detail
Command: npx skills add https://github.com/cabloy/cabloy --skill cabloy-master-detail

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers correctly design and scaffold Cabloy master-detail and nested-detail backend workflows while avoiding incorrect ownership, DTO placement, and generator usage decisions.

Core Features & Use Cases

  • Master-Detail Classification: Identifies first-level detail, recursive nested-detail, aggregate-only, standalone-capable, and documentation-focused scenarios.
  • Generator-First Guidance: Routes scaffold-oriented tasks toward the Cabloy master-detail generator workflow instead of manual implementation.
  • DTO and Relation Preservation: Maintains nested detail naming, placement, aggregate boundaries, and verification practices across Cabloy modules.
  • Use Case: A developer adding a student training record hierarchy can use this Skill to choose the correct detail mode, generate resources, and verify nested DTO and relation consistency.

Quick Start

Use the cabloy-master-detail skill to analyze my Cabloy repository task and guide me through the correct master-detail implementation workflow.

Frequently Asked Questions about cabloy-master-detail

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

FAQPage Schema
How do I scaffold a master-detail backend workflow in Cabloy?

To scaffold a master-detail backend workflow in Cabloy, use the Cabloy master-detail generator workflow to correctly route parent-owned details, wire relations, and generate resources instead of implementing them manually.

What is the difference between aggregate-only and standalone-capable details in Cabloy?

Aggregate-only details in Cabloy exist solely within the parent aggregate's boundary, while standalone-capable details can operate independently; classifying your detail scenario correctly determines DTO placement, relation wiring, and module boundaries.

How do I organize nested DTOs for recursive detail resources in Cabloy?

Organizing nested DTOs for recursive detail resources in Cabloy requires preserving specific naming conventions and maintaining aggregate boundaries to ensure nested-detail relation consistency and proper backend aggregation.

When should I use the Cabloy master-detail generator instead of manual implementation?

You should use the Cabloy master-detail generator whenever scaffolding parent-owned details, recursive nested resources, or aggregate workflows to avoid incorrect ownership decisions and maintain DTO placement consistency across modules.

How do I verify nested detail relation consistency in a Cabloy backend?

Verify nested detail relation consistency in a Cabloy backend by checking DTO naming conventions, validating aggregate boundaries, and ensuring relation wiring aligns with the generated master-detail module structure.