Stats
Actions
Tags
Expert guidance for shipping the DevOpser self-evolving software template to a real environment or producing signed mobile artifacts. Covers target selection (Lightsail, Cloud Run, Fly, ECS Fargate, Kubernetes, VPS), AWS Secrets Manager in NODE_ENV=production, cross-account AssumeRole for multi-tenant hosting, and Android/iOS release builds. Triggers on "deploy this", "ship to Lightsail / Cloud Run / Fargate / Kubernetes", "wire up triggerDeployment", "cross-account trust role", "build the Android APK", "sign the iOS release".
How this skill is triggered — by the user, by Claude, or both
Slash command
/devopser-agent-skills:devopser-deployThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Expert guidance for the **intentionally-blank deployment layer** of the DevOpser template, plus Capacitor Android/iOS release builds. This skill helps the agent pick a target, reason about multi-tenancy, wire the stub in `backend/routes/sites.js → triggerDeployment()`, and produce signed mobile artifacts using `./build-mobile.sh` and `./configure-android-signing.sh` — no new scripts added to th...
Expert guidance for the intentionally-blank deployment layer of the DevOpser template, plus Capacitor Android/iOS release builds. This skill helps the agent pick a target, reason about multi-tenancy, wire the stub in backend/routes/sites.js → triggerDeployment(), and produce signed mobile artifacts using ./build-mobile.sh and ./configure-android-signing.sh — no new scripts added to the repo. Canonical playbook: AGENTS.md → "Adding a deployment target".
| Rule | Description |
|---|---|
| target-selection | Decision matrix — Lightsail / Cloud Run / Fly / ECS Fargate / K8s / VPS, with a recommended default |
| lightsail | Reference implementation — what DevOpser actually uses |
| secrets-manager | The NODE_ENV=production pattern: secret names, not values |
| cross-account | CUSTOMER_CROSS_ACCOUNT_ROLE_ARN + AssumeRole for multi-tenant managed hosting |
| mobile-release | Android keystore + configure-android-signing.sh, iOS via Xcode |
AGENTS.md. If this skill contradicts it, AGENTS.md wins — report the contradiction to DevOpser.target-selection.md.customers table, always.NODE_ENV === 'production', never on feature flags or fork-specific files.keystore.properties, the keystore file, or .env. The .gitignore already excludes them; do not add exceptions.| Situation | Go to |
|---|---|
| "Deploy this" with no more context | target-selection.md → default recommendation |
| DevOpser's own hosting — you're building the reference impl | lightsail.md |
Moving from local dev to production, MAIL_PASSWORD breaks | secrets-manager.md |
| Multi-tenant platform, each customer in their own AWS account | cross-account.md |
| "Ship the Android app" / "build the iOS release" | mobile-release.md |
If AGENTS.md contradicts this skill, AGENTS.md wins — report the contradiction to DevOpser.
Provides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
npx claudepluginhub devopser-io/self-evolving-software-template --plugin devopser-agent-skills