name	build-environment
description	Activate this skill when editing workspace package configurations, running Gradle tasks, or managing dependency locks.

Build Environment & Dependency Integrity

To ensure monorepo build stability and prevent runtime environment conflicts, the following rules must be strictly adhered to:

1. Node & Tooling Constraints

Node.js version: Enforced at v22.22.2 via build.gradle nodeVersion configuration.
Build Infrastructure: Standardized on Vite 6.0.0 and modern build dependencies across all client extensions to resolve native binary and ESM/CJS compatibility conflicts.
Gradle Node Cache: If build/deploy failures occur, always ensure the .gradle/node cache is cleared (rm -rf .gradle/node) before re-running the build to force synchronization with the project's enforced Node version.
Dismissal of Alerts: Any dependabot alerts recommending upgrades for build tools should be reviewed against these pinned versions before applying.

2. Dependabot & Lockfile Integrity

Yarn Dominance: Yarn is the authoritative package manager for this monorepo.
No package-lock.json: To prevent 'npm_and_yarn' conflicts in CI and Dependabot, NEVER commit a package-lock.json file.
Explicit Scoping: The .github/dependabot.yml file explicitly defines the ecosystem and directories for automated updates to ensure monorepo-wide consistency.

Last Updated: 2026-07-19 | Last Reviewed: 2026-07-19

Más de este repositorio

mismo repositorio

coding-standards

peterrichards-lr/liferay-ai-commerce-accelerator

Activate this skill when writing or refactoring microservice and SDK javascript/typescript source files.

2026-07-220

human-in-the-loop

peterrichards-lr/liferay-ai-commerce-accelerator

Activate this skill before opening pull requests, modifying production configurations, or executing deployment and destructive commands to ensure proper human-in-the-loop verification.

2026-07-220

reflection-and-planning

peterrichards-lr/liferay-ai-commerce-accelerator

Activate this skill when beginning complex tasks, proposing architectural changes, or modifying codebase files to ensure proper planning and predictive failure analysis.

2026-07-220

tool-use-react

peterrichards-lr/liferay-ai-commerce-accelerator

Activate this skill when making tool calls, interacting with the terminal, or invoking GitHub APIs to ensure strict ReAct patterns are followed.

2026-07-220

multi-agent-orchestration

peterrichards-lr/liferay-ai-commerce-accelerator

Activate this skill when delegating tasks, defining subagents, or orchestrating parallel agentic workflows.

2026-07-220

documentation

peterrichards-lr/liferay-ai-commerce-accelerator

Activate this skill after implementing code changes to verify, review, and update markdown documentation and timestamps.

2026-07-210

name	build-environment
description	Activate this skill when editing workspace package configurations, running Gradle tasks, or managing dependency locks.

Build Environment & Dependency Integrity

To ensure monorepo build stability and prevent runtime environment conflicts, the following rules must be strictly adhered to:

1. Node & Tooling Constraints

Node.js version: Enforced at v22.22.2 via build.gradle nodeVersion configuration.
Build Infrastructure: Standardized on Vite 6.0.0 and modern build dependencies across all client extensions to resolve native binary and ESM/CJS compatibility conflicts.
Gradle Node Cache: If build/deploy failures occur, always ensure the .gradle/node cache is cleared (rm -rf .gradle/node) before re-running the build to force synchronization with the project's enforced Node version.
Dismissal of Alerts: Any dependabot alerts recommending upgrades for build tools should be reviewed against these pinned versions before applying.

2. Dependabot & Lockfile Integrity

Yarn Dominance: Yarn is the authoritative package manager for this monorepo.
No package-lock.json: To prevent 'npm_and_yarn' conflicts in CI and Dependabot, NEVER commit a package-lock.json file.
Explicit Scoping: The .github/dependabot.yml file explicitly defines the ecosystem and directories for automated updates to ensure monorepo-wide consistency.

Last Updated: 2026-07-19 | Last Reviewed: 2026-07-19