Vercel deployment and configuration for Adynato projects. Covers environment variables, vercel.json, project linking, common errors like VERCEL_ORG_ID/VERCEL_PROJECT_ID, and CI/CD setup. Use when deploying to Vercel, configuring builds, or troubleshooting deployment issues.
Staging and production deployment using Laravel Deployer with health checks, cache management, and rollback support (HUMAN-ONLY execution)
Vercel deployment patterns and best practices. Use when deploying frontend applications, configuring edge functions, setting up preview deployments, or optimizing Next.js applications.
Monitor and interact with Vercel deployments, build logs, and environment details using the Vercel CLI. Use this to check build status, wait for deployments, view logs, and debug CI/CD failures.
Next.js deployment - Vercel, Docker, self-hosting strategies
Build and distribute Dev Client APK/IPA via EAS Build with automatic Android Keystore generation. Automatically runs setup if eas.json is missing. Use when native changes are required (permissions, native modules, deep links, app configuration, icons) or when the user mentions "native build", "dist-dev-client", "Dev Client build", "APK", "IPA", or "EAS build".
Build, package, tag, and release Naki app to GitHub. Use when the user asks to "release", "publish", "tag", "build DMG/ZIP", or "upgrade version". Handles the complete release workflow from build to GitHub release creation.
Manage dependencies and supply chain security to prevent vulnerable or malicious packages. Use this skill when you need to audit dependencies, update packages, check for vulnerabilities, understand supply chain attacks, or maintain dependency security. Triggers include "dependencies", "npm audit", "supply chain", "package security", "vulnerability", "npm update", "security audit", "outdated packages".
Validates story implementations through testing, code review, and quality gate assessment. Uses testing skill for execution, checks standards compliance, and creates quality gate decisions (PASS/CONCERNS/FAIL/WAIVED).
Right-side-of-V verification/validation orchestration for a change or PR. Produces a single Quality Gate Report with evidence covering: code review, security audit, performance regression risk, requirements traceability, acceptance/UAT scenarios, and (when UI changes) visual regression testing. Use when preparing a PR for merge/release, doing a “ready?” check, or enforcing an engineering quality gate.
Use for DevOps work in m0sh1.cc homelab repos (infra and helm-charts), covering GitOps/ArgoCD rules, Helm wrapper charts, Terraform lab workflow, Ansible Vault boundaries, and supply-chain checks. Includes repo-specific guard/scaffold tools.
View logs for a specific deployment. Requires authentication. Use for Agentuity cloud platform operations
Clones HEC-HMS components (basins, met models, control specs, runs) using the CLB Engineering LLM Forward approach. Creates non-destructive, traceable, GUI-verifiable copies for QAQC comparison, scenario analysis, and parameter sensitivity testing. Use when creating alternative scenarios, setting up QAQC workflows, comparing baseline vs updated models, or preserving original while testing modifications. All clones appear in HEC-HMS GUI with separate DSS outputs for side-by-side comparison. Trigger keywords: clone, duplicate, copy, QAQC, scenario, alternative, baseline, comparison, side-by-side, non-destructive, traceable.
Use when you have a spec or requirements for a multi-step task, before touching code
GitLab CI/CD pipeline optimization, Docker image building, caching strategies, and 3-stage deployment workflow
Watch an Azure DevOps UAT PR for maintainer feedback or approval by polling threads and reviewer votes until approved/passed.
Iterate bootstrap-qcow2 sysroot/rootfs build plans inside the container using sysroot-runner overrides, state bookmarks, and failure reports, then back-annotate stable fixes into SysrootBuilder for reproducible clean builds.
Prevent unbounded growth of system artifacts. Use when checking system health, consolidating files, or managing archives.
Diagnose and fix common Haskell Bazel build errors, especially dependency visibility issues
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of Flutter development work by presenting structured options
