cabloy-domain-planning

Validate Cabloy suite and module naming before code generation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps Cabloy developers avoid premature scaffolding by turning unclear business domain ideas into validated suite, module, and naming plans.

Core Features & Use Cases

  • Domain Structure Planning: Guides users in deciding whether a business area should become a suite or module and validates providerId, suite, and module naming.
  • Naming Validation: Checks Cabloy naming rules, proposes alternatives, and preserves custom naming options before generation begins.
  • Use Case: When designing a new CRM, ERP, OA, or training domain, use this Skill to create a confirmed suite-first structure before running scaffold commands.

Quick Start

Ask the skill to plan a new Cabloy business domain and recommend valid suite and module names before scaffolding.

Frequently Asked Questions about cabloy-domain-planning

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

FAQPage Schema
How do I plan suite and module structures before scaffolding a Cabloy business domain?

Cabloy domain planning requires deciding whether a business area becomes a suite or module, validating providerId and naming rules, and passing confirmation gates before scaffolding.

When do I need suite-first planning for a new CRM, ERP, or OA domain?

Suite-first planning is required for long-lived business domains like CRM, ERP, OA, and training systems to ensure naming decisions and scaffold preparation are validated before code generation begins.

What is the best way to validate Cabloy naming rules for modules and suites?

The best way to validate Cabloy naming rules is using a confirmation gate that checks providerId, suite, and module names, proposes alternatives, and preserves custom naming options before scaffolding.

Can I scaffold a new Cabloy module without validating the domain structure first?

Scaffolding without validation risks premature code generation. Domain planning enforces suite-first structure decisions and naming rule checks through confirmation gates before CLI handoff.

How do I get CLI-oriented handoff guidance after planning a Cabloy business domain?

You get CLI-oriented handoff guidance by completing the domain planning confirmation gates, which validate suite and module structures and output scaffold-ready commands for the Cabloy CLI workflow.