New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Cabloy Master Detail

by cabloy in cabloy/cabloy

This skill should be used when the main Cabloy task is parent-owned detail aggregation: master-detail or nested-detail backend scaffolding, choosing aggregate-owned vs standalone-capable detail…

MITAuto-check passedDevelopment

Install Cabloy Master Detail

skills CLI
$ npx skills add cabloy/cabloy --skill cabloy-master-detail -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install cabloy/cabloy cabloy-master-detail --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/cabloy/cabloy.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/cabloy-master-detail .claude/skills/cabloy-master-detail && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
cabloy-master-detail
GitHub stars
982
Token cost
~2.3k tokens
SKILL.md length
1,124 words
Files
1
Skills in repo
12
Repo updated
First seen
Licence
MIT

At a glance

This skill should be used when the main Cabloy task is parent-owned detail aggregation: master-detail or nested-detail backend scaffolding, choosing aggregate-owned vs standalone-capable detail…

  • Works in 8 steps: Detect repo, edition, and task shape → Start from shared entrypoints and the… → Preserve the current nested detail… → …
  • Tasks that involve Project scaffolding
  • SKILL.md covers Goals, Step 1: Detect repo, edition,…, Step 2: Start from shared… and Step 3: Preserve the current…, plus 6 more sections
  • Calls npm

What it does

Cabloy Master Detail is an agent skill from cabloy/cabloy. This skill should be used when the main Cabloy task is parent-owned detail aggregation: master-detail or nested-detail backend scaffolding, choosing aggregate-owned vs standalone-capable detail mode, running :tools:masterDetail, or preserving nested detail DTO naming and placement rules. Prefer it when the core problem is detail aggregation rather than ordinary standalone CRUD scaffolding or cross-stack contract drift.

Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Project scaffolding. The repository describes itself as: Cabloy is a Node.js fullstack framework for AI vibe coding, with AI Spec-Driven Development guiding work from confirmed specs to verifiable delivery. The licence is MIT.

When your agent uses it

  • Tasks that involve Project scaffolding

Example prompts

  • “/cabloy-master-detail”

Workflow steps

8 steps, taken from the step headings in SKILL.md.

  1. Detect repo, edition, and task shape
  2. Start from shared entrypoints and the generator
  3. Preserve the current nested detail invariants
  4. Distinguish aggregate vs standalone mode deliberately
  5. Inspect the specimen modules before manual follow-up edits
  6. Preserve the instance boundary across the aggregate
  7. Keep fullstack boundaries explicit
  8. Verification guidance

What it can do on your machine

Read from SKILL.md and the folder at commit a12cf91. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Cabloy Master Detail loads about 2.3k tokens when it runs. Until then it costs about 111 tokens; SKILL.md has 1,124 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~111
When it runs · the whole SKILL.md, loaded when a task matches
~2.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from cabloy/cabloy at commit a12cf91, republished under its MIT licence (© cabloy). 1,124 words, ~2,343 tokens.

Download SKILL.mdSave it as .claude/skills/cabloy-master-detail/SKILL.md (or your agent's skills folder).
name
cabloy-master-detail
description
This skill should be used when the main Cabloy task is parent-owned detail aggregation: master-detail or nested-detail backend scaffolding, choosing aggregate-owned vs standalone-capable detail mode, running `:tools:masterDetail`, or preserving nested detail DTO naming and placement rules. Prefer it when the core problem is detail aggregation rather than ordinary standalone CRUD scaffolding or cross-stack contract drift.

Cabloy Master-Detail

Use this skill when the user wants to add, extend, analyze, or preserve a Cabloy master-detail or nested-detail backend workflow.

Read the public Master-Detail Workflow for the canonical operational explanation and Master-Detail Source Reading Map for the current source evidence. This skill is the thinner orchestration layer: it should classify the detail shape, choose the generator-first path, preserve the naming and placement invariants, and finish with the right verification path.

Goals

  1. detect whether the active repository is Cabloy Basic or Cabloy Start
  2. classify the request as first-level master-detail, recursive nested-detail, aggregate-only detail, standalone-capable detail, or docs/source-reading only
  3. prefer npm run vona :tools:masterDetail over manual scaffolding when the task is really generator-oriented
  4. preserve nested detail DTO naming and placement invariants
  5. keep aggregate vs standalone detail mode explicit
  6. finish with verification guidance that matches the actual detail shape

Step 1: Detect repo, edition, and task shape

Check the repository root for these marker files:

  • __CABLOY_BASIC__
  • __CABLOY_START__

Interpretation:

  • only __CABLOY_BASIC__ present → this is Cabloy Basic
  • only __CABLOY_START__ present → this is Cabloy Start
  • both markers present → treat the repository as ambiguous or invalid and stop before making edition-specific assumptions
  • neither marker present → inspect the owning package scripts and nearby repository structure, then ask before making an edition-specific assumption

Then classify the request into one of these entry shapes.

Shape A: first-level master-detail

Use this shape when the user wants a master resource to own one detail collection, such as:

  • student -> trainingRecords
  • parent resource plus one nested child collection
Shape B: recursive nested-detail

Use this shape when a detail resource itself becomes the immediate parent of another detail collection, such as:

  • student -> trainingRecords -> trainingRecordSubjects

Treat this as the same master-detail pattern repeated one level lower, not as an unrelated mechanism.

Shape C: aggregate-only detail

Use this shape when the detail should remain owned by the aggregate and should not keep a standalone controller/service/DTO resource surface in source.

Shape D: standalone-capable detail

Use this shape when the detail must still participate in nested editing but also keep its own ordinary standalone resource surface.

Shape E: docs or source-reading only

Use this shape when the user is not changing the scaffold but wants explanation, diagnosis, or source-reading guidance. In that case, anchor the answer in the two public master-detail docs instead of pretending the next step is generation.

Step 2: Start from shared entrypoints and the generator

Inspect these surfaces before proposing implementation:

  • the repository package.json
  • npm run vona
  • vona/packages-cli/cli-set-api/src/lib/command/tools.masterDetail.ts
  • vona/packages-cli/cli-set-api/src/lib/bean/cli.tools.masterDetail.ts
  • the two public master-detail docs

If the task is scaffold or generator oriented, prefer the generator path first.

Typical command shape:

  • npm run vona :tools:masterDetail resourceName -- [--module=] [--detailModule=] [--detailResourceName=] [--relationName=] [--fk=] [--detailMode=aggregate|standalone]

Important rule:

  • use canonical module relative names such as training-student and training-record
  • do not substitute package names for module names

Step 3: Preserve the current nested detail invariants

Nested detail DTO naming

Keep nested detail DTOs on the detail* prefix so their role remains explicit.

Representative examples:

  • detailRecordBase
  • detailRecordMutate
  • detailRecordResItem
  • detailRecordView
  • detailRecordSubjectBase
  • detailRecordSubjectMutate
  • detailRecordSubjectResItem
  • detailRecordSubjectView

Do not rewrite these into ordinary child-resource CRUD names when the DTOs are really describing nested detail editing under a parent.

Nested detail DTO placement

Keep nested detail DTOs beside the immediate parent DTOs that consume them.

That means:

  • first-level detail DTOs live with the master DTOs
  • second-level detail DTOs live with the first-level parent DTOs
  • deeper levels repeat the same immediate-parent rule recursively

Do not move nested detail DTOs into the child module just because the child may also have its own standalone resource surface.

Step 4: Distinguish aggregate vs standalone mode deliberately

Aggregate mode

Use --detailMode=aggregate when the detail should remain aggregate-owned only.

Preserve the source-backed rule:

  • aggregate mode removes or disallows standalone controller/service/DTO resource surfaces as appropriate
Standalone mode

Use --detailMode=standalone when the detail must also keep its own ordinary resource surface.

Preserve the source-backed rule:

  • standalone mode still uses nested detail* DTOs in the parent-owned editing flow
  • standalone child CRUD in the child module can keep its ordinary resource DTO names
Show full SKILL.md (460 more words)Show less

Step 5: Inspect the specimen modules before manual follow-up edits

Use the current specimen chain as the strongest current reference path:

  • training-student
  • training-record
  • training-recordsubject

Especially inspect:

  • parent model relation wiring
  • parent service include lifecycle
  • parent create/update/view DTOs
  • sibling nested detail DTO files
  • child entity FK support
  • generated .metadata/index.ts exports

Important rule:

  • do not start from hand-patching DTO placement or relation semantics until the generator path and specimen shape have been checked first

Step 6: Preserve the instance boundary across the aggregate

Master-detail ownership is separate from Vona's tenant/instance boundary:

  • in the current tenancy model, a tenant corresponds to an instance and normal parent/detail model operations retain the active instance scope
  • relation and foreign-key checks must preserve that scope; aggregate ownership does not authorize bypassing it
  • treat a missing parent or detail from the normal scoped aggregate flow as absent; do not add unscoped existence probes merely to distinguish a foreign-instance row
  • if a future multi-merchant design is needed, model merchant ownership explicitly within the instance in addition to the aggregate relation

For the canonical tenancy explanation, read Multi-Instance and Instance Resolution and Model Guide.

Step 7: Keep fullstack boundaries explicit

This skill is primarily for backend detail aggregation.

If the task later becomes a backend/frontend contract synchronization or stale generated consumer problem, the root cabloy-contract-loop skill may become the better primary workflow.

Use this skill first when the core problem is still:

  • parent-owned detail aggregation
  • nested detail recursion
  • generator choice
  • aggregate vs standalone detail mode
  • nested detail DTO naming or placement in a scaffolding context

Step 8: Verification guidance

Always finish with verification that matches the detail shape.

Typical checks include:

  • confirm the parent model contains the expected hasMany relation
  • confirm parent service create/view/update/delete includes the nested detail relation
  • confirm parent create/update/view DTOs consume the nested detail DTOs
  • confirm nested detail DTO names still follow the detail* pattern
  • confirm nested detail DTOs are placed with the immediate parent DTOs that consume them
  • confirm the recursive immediate-parent rule still holds for deeper nesting
  • confirm the detail entity contains the FK field when expected
  • confirm detail schema/index support is present
  • confirm both modules’ .metadata/index.ts outputs reflect the expected nested detail DTOs
  • if standalone mode applies, confirm the detail module still exposes its standalone resource surface
  • if this workflow changes meta.version.ts, run npm run test so the test database is reinitialized and schema/data consistency issues surface early

Response pattern

When helpful, structure the response around these points:

  1. detected edition
  2. detected detail shape
  3. recommended generator-first path
  4. aggregate vs standalone decision
  5. nested DTO naming and placement reminders
  6. verification steps

Keep the response practical. The value of this skill is to route master-detail requests into the correct generator-first workflow while preserving the recursive ownership rules encoded by the current source.

© cabloy, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/cabloy-master-detail of cabloy/cabloy.

Open the folder on GitHubat commit a12cf91

Compare with similar skills

Cabloy Master Detail next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Cabloy Master Detail compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Cabloy Master Detail this skillcabloy/cabloy982—~2.3kAutomated safety check: PassMIT
Nx Generatenomcopter/react-mosaic4.8k7 repos~1.9kAutomated safety check: PassCustom licence
PonytailDavidObando/gsharp5657 repos~1.7kAutomated safety check: PassMIT
Run Nx Generatornrwl/nx29k2 repos~592Automated safety check: NotesMIT
Conductor Setupgemini-cli-extensions/conductor3.8k—~4.2kAutomated safety check: PassApache-2.0
Mirage VFS Adapter Authoringstrukto-ai/mirage3.7k—~2.5kAutomated safety check: PassApache-2.0

Similar skills

  • Nx Generate

    nomcopter/react-mosaic

    Generate code using nx generators. An agent skill from nomcopter/react-mosaic.

    4.8k GitHub starsUsed in 7 repos~1.9k tokens
    DevelopmentAuto-check passed

  • Ponytail

    DavidObando/gsharp

    Forces the laziest solution that actually works, simplest, shortest, most minimal.

    565 GitHub starsUsed in 7 repos~1.7k tokens
    DevelopmentAuto-check passed

  • Run Nx Generator

    nrwl/nx

    Run Nx generators with prioritization for workspace-plugin generators.

    29k GitHub starsUsed in 2 repos~592 tokens
    DevelopmentAuto-check: notes

  • Conductor Setup

    gemini-cli-extensions/conductor

    Scaffolds the project and sets up the Conductor environment.

    3.8k GitHub stars~4.2k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

  • Mirage VFS Adapter Authoring

    strukto-ai/mirage

    Builds or extends a custom Mirage virtual filesystem adapter for an API, database, object store or app data, with a working mount configuration and filesystem tests.

    3.7k GitHub stars~2.5k tokensUpdated today
    DevelopmentAuto-check passed

  • Siteboon Backend Module Standards

    siteboon/claudecodeui

    Enforces this repository's TypeScript backend module architecture under server/: feature folders, barrel exports, and where shared types and utilities belong.

    14k GitHub stars~1.2k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from cabloy/cabloy

All 12 skills in this repo

  • Cabloy Spec Generation

    cabloy/cabloy

    A skill your agent uses to create or maintain Cabloy suite specifications under repo-specs, including PRD, SRS, PDP/WBS, acceptance planning, progress, and suite ADRs.

    982 GitHub stars~3.2k tokensUpdated today
    Auto-check: notes

  • Cabloy Domain Planning

    cabloy/cabloy

    A skill your agent uses whenever the user wants to plan a new business domain in this Cabloy repo, such as CRM, OA, training, ERP, or a similar long-lived domain.

    982 GitHub stars~2.1k tokensUpdated today
    Auto-check passed

  • Cabloy Worktree Environment

    cabloy/cabloy

    This skill must be used only when the user explicitly invokes /cabloy-worktree-environment or explicitly asks to perform the named Cabloy worktree-environment setup.

    982 GitHub stars~2.8k tokensUpdated today
    Auto-check: notes

  • Cabloy Backend Scaffold

    cabloy/cabloy

    This skill should be used when the user needs the Vona backend scaffold/extend path in this Cabloy repo, especially to choose the right npm run vona generator or CRUD command and the required…

    982 GitHub stars~3.1k tokensUpdated today
    Auto-check passed

  • Cabloy Contract Loop

    cabloy/cabloy

    A skill your agent uses whenever a Cabloy task crosses the Vona-to-Zova contract boundary: backend DTO, controller, validation, entity, inferred DTO, or OpenAPI changes that should drive SDK…

    982 GitHub stars~5.1k tokensUpdated today
    Auto-check passed

  • Cabloy Frontend Scaffold

    cabloy/cabloy

    A skill your agent uses whenever the user wants the Zova frontend path in this Cabloy repo: create or extend pages, components, api or model beans, route/query/params work, metadata refresh…

    982 GitHub stars~4.1k tokensUpdated today
    Auto-check passed

Categories

Questions about Cabloy Master Detail

What does Cabloy Master Detail do?

This skill should be used when the main Cabloy task is parent-owned detail aggregation: master-detail or nested-detail backend scaffolding, choosing aggregate-owned vs standalone-capable detail…. Cabloy Master Detail is an agent skill from cabloy/cabloy. This skill should be used when the main Cabloy task is parent-owned detail aggregation: master-detail or nested-detail backend scaffolding, choosing aggregate-owned vs standalone-capable detail mode, running :tools:masterDetail, or preserving nested detail DTO naming and placement rules.

When should I use Cabloy Master Detail?

Cabloy Master Detail fits situations like: tasks that involve Project scaffolding.

How do I install Cabloy Master Detail in Claude Code?

Run `npx skills add cabloy/cabloy --skill cabloy-master-detail -a claude-code`. Or copy the skill folder (.agents/skills/cabloy-master-detail in cabloy/cabloy) into .claude/skills/cabloy-master-detail in your project. Claude Code loads it when a task matches its description.

How do I install Cabloy Master Detail in Codex?

Run `npx skills add cabloy/cabloy --skill cabloy-master-detail -a codex`. Or copy the skill folder (.agents/skills/cabloy-master-detail in cabloy/cabloy) into .agents/skills/cabloy-master-detail in your project. Codex loads it when a task matches its description.

Can I use Cabloy Master Detail in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cabloy/cabloy --skill cabloy-master-detail -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cabloy-master-detail, .gemini/skills/cabloy-master-detail, .github/skills/cabloy-master-detail and .opencode/skills/cabloy-master-detail in your project.

What does Cabloy Master Detail need to run?

Going by SKILL.md and its folder, Cabloy Master Detail needs the command-line tools its instructions call (npm).

Does Cabloy Master Detail access the network?

SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Cabloy Master Detail safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Cabloy Master Detail use?

Cabloy Master Detail is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Cabloy Master Detail use?

About 2.3k tokens (SKILL.md is roughly 9.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Cabloy Master Detail?

Skills that share tags, products or a category with Cabloy Master Detail: Nx Generate (nomcopter/react-mosaic, 4.8k stars), Ponytail (DavidObando/gsharp, 565 stars), Run Nx Generator (nrwl/nx, 29k stars) and Conductor Setup (gemini-cli-extensions/conductor, 3.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Cabloy Master Detail?

cabloy (a GitHub organization) maintains it in cabloy/cabloy, which has 982 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 10, 2026.

Source: cabloy/cabloy on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.