Skip to content

liferay/liferay-portal / workspaces/clarity-solution-workspace/.agents/skills/manage-cloud-project

manage-cloud-project

Verified

Authenticate to and operate on a Liferay Cloud (LXC / DXP Cloud) project via the `lcp` CLI — deploy client extensions, view logs, restart services, list resources. Use when the user mentions lcp/LXC/liferay.cloud, when an LCP.json is present in the workspace, or when the user references a console.liferay.cloud URL.

Manage Cloud Project

Operate on a Liferay Cloud project from the lcp CLI.

When to Invoke

  • lcp, LXC, liferay.cloud, or DXP Cloud is mentioned.
  • An LCP.json file exists in the workspace.
  • The user references a console.liferay.* URL.

"Deploy to dev/uat/prd" alone is not a trigger. Those names also describe local environments under configs/{env}. Require an explicit cloud signal.

Establish Context

Resolve each before proceeding:

  1. lcp --version — is the CLI installed?

  2. lcp remote — is a default remote set?

  3. <project>-<env> — what is the intended target?

Workflow

  1. Identify the target. Confirm <project>-<env> with the user. Use lcp list if uncertain.

  2. Deploy. Run lcp deploy. Discover flags via lcp deploy --help.

  3. Verify runtime health. Tail lcp log for the target service. Apply the runtime activation rule from liferay-rules.md: a successful command exit is not success.

For any other operation, discover available commands via lcp --help.

Patterns and Gotchas

  • <project>-<env> naming overlaps with local configs/{env} directories. Confirm cloud target before assuming.
  • LCP.json placement controls deploy scope: at repo root, lcp deploy deploys all services; from a service folder, it deploys only that one.

Composition

  • Counterpart to deploy-and-verify, which targets local Tomcat or Docker.
  • Consumes the artifacts produced by scaffold-client-extension.
  • Defer credential and secret handling to production-standards.

References

  • lcp --help and lcp <cmd> --help
  • https://learn.liferay.com/w/dxp/cloud/reference/command-line-tool
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall