Skip to content

liferay/liferay-portal / workspaces/clarity-solution-workspace/.agents/skills/production-standards

production-standards

Verified

Production guardrails applied when generating or modifying any code or configuration intended for a nonlocal environment (UAT, prod, customer facing deploys). Use whenever the agent's output may reach a higher environment — to enforce state integrity, secret management, and security preserving debugging practices.

Production Standards

Configuration and State Integrity

  • State Integrity (Source of Truth): configuration is the source of truth for version control — never mutate the runtime directly. For Tomcat, this is configs/local/portal-ext.properties; copy to bundles/portal-ext.properties and restart to apply. For Docker with a prebuilt image, this is liferay.env (env vars); changes require a container restart. For Docker with a custom image, this is configs/docker/portal-ext.properties; changes require rebuilding the image.
  • No Silent Edits to Runtime: never modify the live runtime state (e.g., bundles/portal-ext.properties) without explicitly announcing the change in your response. Edits that propagate from configs/[env]/ via the normal sync flow are preferred.
  • No Security Disabling Debug Shortcuts: never set portal.security.manager.strategy=none, disable CSRF enforcement, or otherwise weaken security as a debugging shortcut — even temporarily. If a 403 cannot be resolved through Roles, Permissions, or OAuth2 scope configuration, declare it a blocker and surface it to the user rather than disabling the protection.

Production Deployment Guardrails

  • Environment Specific Configs: mandate the configs/prod or configs/uat directory for environment properties; these must be bundled into Docker images / Liferay Cloud builds, not hot deployed via Blade.
  • Secret Management: explicitly forbid hardcoded credentials. Mandate Liferay's Secret Management or environment variables (e.g., ${env.SECRET_NAME}).
  • Performance & Caching: mandate proper caching headers for custom endpoints / Client Extensions, and use of Liferay.Util.fetch to route through authenticated caching layers.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall