cloudcc-cli-dev

What This Skill Does

The cloudcc-cli-dev skill serves as an expert assistant for CloudCC CRM developers. It streamlines the entire development lifecycle, from initial requirement decomposition to the final deployment of assets. By integrating with the official cloudcc-cli (cc command), this skill enables users to programmatically manage CloudCC custom objects, fields, application menus, backend apex-style classes, scheduled tasks (timers), triggers, and Vue-based custom components. It acts as a bridge between high-level business requirements and low-level code generation, ensuring that all created assets adhere to the platform's specific architectural patterns and security standards.

Installation

To install this skill, run the following command in your terminal: clawhub install openclaw/skills/skills/androidxhm/cloudcc-cli-dev. Before executing any commands, ensure you have the cloudcc-cli npm package installed globally on your system. Refer to INSTALL_AND_BOOTSTRAP.md to configure your environment variables and secure credentials without exposing them in your code.

Use Cases

This skill is ideal for:

• Rapidly prototyping CRM modules by creating objects and fields via CLI.
• Automating backend logic for complex business requirements using custom classes and triggers.
• Developing custom frontend interfaces using Vue.js components that interact directly with CloudCC data services.
• Standardizing development workflows through automated requirement breakdown and document-driven coding practices.
• Batch operations for pulling, validating, and publishing CRM assets across different environments.

Example Prompts

1. "I need to implement a new 'Project' object in CloudCC with custom fields for 'Budget' and 'Manager'. Please start by creating a requirement breakdown and suggest the schema structure based on my provided specifications."
2. "Generate a new trigger for the 'SalesOrder' object that validates the total amount before record saving. Ensure the code is placed within the @SOURCE_CONTENT_START and @SOURCE_CONTENT_END tags."
3. "Show me the cc commands needed to pull all custom components from my current project and explain how to deploy them to the production environment using the CLI."

Tips & Limitations

• Always read the documentation files (REQUIREMENTS_BREAKDOWN.md, BACKEND_CODE.md, etc.) before initiating tasks to maintain architectural consistency.
• Security first: Never include raw API tokens, secret keys, or authentication tokens in your prompts, code snippets, or documentation files. Utilize environment configuration files instead.
• The tool is designed to work strictly within defined markers. For backend code, ensure your logic is encapsulated between @SOURCE_CONTENT_START and @SOURCE_CONTENT_END for valid serialization and deployment. Similarly, client-side scripts must be contained within the main function provided by the boilerplate.