What is the primary purpose of the etendo-_guidelines skill?

It provides shared conventions and environment configurations that ensure all other Etendo skills behave consistently when interacting with the ERP system.

Does this skill support both Docker and local Etendo installations?

Yes, it includes logic to detect the environment type from gradle.properties and adjusts database (psql) and Tomcat commands accordingly.

Why is Java 17 specifically required by these guidelines?

Etendo's Gradle build system requires Java 17; these guidelines automate its detection to prevent 'Unsupported class file major version' errors during builds.

What are the rules for extension columns (EM_ prefix)?

When a module adds a column to a table owned by a different module, these guidelines enforce the EM_{PREFIX}_ naming convention to ensure ERP compatibility.

How does the skill handle long-running Gradle tasks?

It mandates the use of general-purpose subagents for long tasks like smartbuild to prevent the main agent context from being consumed by log output.

Etendo Development Guidelines

Name: Etendo Development Guidelines
Author: etendosoftware

byetendosoftware

•

Developer Tools

Establishes consistent development standards, environment configurations, and execution patterns for the Etendo Dev Assistant ecosystem.

This skill acts as the foundational framework for all Etendo ERP development within Claude Code. It provides standardized protocols for environment detection, Gradle task execution, and Application Dictionary naming conventions. By centralizing logic for context resolution, Docker vs. local fallback handling, and webhook communication, it ensures that every interaction with the Etendo platform is reliable, consistent, and follows ERP best practices. It is essential for developers automating complex ERP customizations, module management, and metadata synchronization.

Key Features

011 GitHub stars

02Automated naming convention enforcement for Database and Application Dictionary objects

03Standardized environment detection for Java 17 and Gradle configurations

04Pre-defined webhook protocols and post-creation metadata synchronization hooks

05Unified project context resolution via .etendo/context.json integration

06Optimized Gradle execution patterns using subagents for background processing

Use Cases

01Automating the detection of JAVA_HOME and environment variables for build tasks

02Enforcing naming standards and prefix rules for custom ERP module extensions

03Maintaining architectural consistency across multiple Etendo-specific Claude skills

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add etendosoftware/etendo_claude_marketplace etendo-_guidelines

For use in Claude.ai and ChatGPT

Key Features

011 GitHub stars

02Automated naming convention enforcement for Database and Application Dictionary objects

03Standardized environment detection for Java 17 and Gradle configurations

04Pre-defined webhook protocols and post-creation metadata synchronization hooks

05Unified project context resolution via .etendo/context.json integration

06Optimized Gradle execution patterns using subagents for background processing

Use Cases

01Automating the detection of JAVA_HOME and environment variables for build tasks

02Enforcing naming standards and prefix rules for custom ERP module extensions

03Maintaining architectural consistency across multiple Etendo-specific Claude skills

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add etendosoftware/etendo_claude_marketplace etendo-_guidelines

For use in Claude.ai and ChatGPT