'upgrade' 검색 결과

Plans, executes, and validates Google Kubernetes Engine upgrades for Standard and Autopilot clusters. Creates environment-specific upgrade plans, checklists, and command-based runbooks, with guidance on maintenance timing, node upgrade strategies, workload readiness, and stalled upgrades.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Planning a GKE version upgrade
• Choosing release channels and maintenance schedules
• Preparing node pool upgrades for databases or GPU workloads

Design and improve in-app screens that invite users to pay or upgrade. Plan messages, timing, feature previews, and payment steps for usage limits, locked features, and trial endings, with clear options to dismiss or continue free.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Design upgrade prompts at free usage limits
• Improve trial expiration screens
• Explain paid features when users try to access them

Plans, executes, and validates Google Kubernetes Engine (GKE) cluster upgrades and maintenance operations for both Standard and Autopilot clusters. Produces upgrade plans, pre/post-upgrade checklists, maintenance runbooks with gcloud commands, release channel strategy, and troubleshooting guides. Handles node pool upgrade strategies (surge, blue-green), version compatibility, PDB management, and workload-specific concerns (stateful, GPU, operators). Use this skill whenever the user mentions GKE upgrades, Kubernetes version bumps, node pool maintenance, GKE patching, cluster version management, release channel selection, maintenance windows, surge upgrades, stuck upgrades, or any GKE lifecycle management task — even casual mentions like "we need to upgrade our clusters" or "plan our next GKE maintenance" or "our upgrade is stuck." Don't use for GKE cluster creation, application onboarding, general networking/routing setup, or security policy configurations (use gke-basics or relevant GKE skills instead).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design and improve in-app upgrade prompts, paid feature screens, and trial expiration notices. Plan when they appear, what they say, how users reach payment, and which metrics to track while keeping dismissal options clear.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Improving free-to-paid upgrade screens
• Explaining usage limits and paid options
• Planning trial expiration notices

Keep gbrain current by checking available updates, summarizing release changes, and applying or deferring upgrades according to configured preferences. Migration instructions take priority when a release requires an operator to supervise the update.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check whether gbrain has an available update
• Review release changes before upgrading
• Defer update reminders during ongoing work

Design and improve in-app screens that invite users to paid plans. Develop complete screen copy, prompt timing rules, upgrade flows, and experiment ideas based on the value users have already experienced.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Improve prompts shown at free usage limits
• Rewrite trial expiration screens
• Design prompts for paid-only features

Clean up after (or abandon) a Rails upgrade. Drop NextRails.next? and NextRails.current? branches and retire dual-boot scaffolding (Gemfile.next, Gemfile.next.lock, conditional Gemfile groups), keeping either the next or the current version. Trigger when the user says they are done with the upgrade, want to clean up dual-boot, want to drop NextRails branches, want to finish the upgrade, want to abandon or revert the upgrade attempt, want to roll back to the current Rails version, or want to pause this upgrade hop. Based on FastRuby.io's "Finishing an Upgrade" methodology, extended with an abandon/pause path.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions "paywall," "upgrade screen," "upgrade modal," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," "in-app pricing," "free users won't upgrade," "trial to paid conversion," or "how do I get users to pay." Use this for any in-product moment where you're asking users to upgrade. Distinct from public pricing pages (see page-cro) — this focuses on in-product upgrade moments where the user has already experienced value. For pricing decisions, see pricing-strategy.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create a personalized nanobot upgrade skill after confirming how it was installed, which optional packages are needed, and whether a proxy is required. The saved skill includes environment checks, an upgrade command, and version verification.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Set up repeatable nanobot upgrades
• Include optional packages in future upgrades
• Configure upgrades through an HTTP proxy

Updates an Ant Design Pro project by comparing it with the latest official template. It merges dependency and configuration changes while preserving custom pages and business logic, then checks for deprecated APIs and build errors.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Update an existing Ant Design Pro project
• Merge template changes while preserving custom code
• Check deprecated APIs during an upgrade

Changing DOCA versions safely: upgrading or downgrading the host DOCA packages, refreshing the BlueField BFB, bumping the NGC DOCA container tag, or rolling back, with the discipline detect -> report -> ASK -> only then a guided upgrade. Trigger on "is there a newer DOCA", "I want the newest DOCA features, can I just apt upgrade in place", "should I move to the next release", "the upgrade stopped midway and dpkg is in a broken state", "my component is being deprecated, what now", or "roll me back", even without the word upgrade. Detect what is installed, find the newer release, report the gap, then STOP and ask for explicit confirmation; never upgrade automatically. Not for a runtime error on an unchanged install (doca-debug). Version detection alone belongs to doca-version, first-time install to doca-setup, any hardware / firmware / reboot step to doca-hardware-safety, and public-docs or sunset routing to doca-public-knowledge-map.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Upgrades an MWAA environment to a newer Airflow version — within 2.x, within 3.x, or across the 2.x-to-3.x boundary. Computes the version-jump path, inserting the 2.11.x stepping-stone and Python-transition step when needed. Chooses an approach by whether run history and the same environment (URL/ARN) must be kept: a new-environment upgrade (blue-green), a rehearsed in-place upgrade validated on a test copy, or a direct in-place upgrade. Runs Ruff scanning and deprecation-warning log scans for 3.x moves, plus Docker validation, batched deployment, and switchover. Saves a resumable upgrade plan for multi-session work. Triggers on: upgrade MWAA, upgrade Airflow, migrate to Airflow 3, MWAA Airflow 3, Airflow 2 to 3, preserve Airflow history, keep same MWAA environment, blue-green cutover, validation environment before cutover. Not for authoring new DAGs (authoring-mwaa-workflow), debugging unrelated DAG failures (debugging-mwaa-workflow), or MWAA Serverless YAML workflows (provisioned Python DAGs only).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Designing free-to-paid conversion flows for SaaS products. Trigger moments, paywall design, value demonstration, upsell vs downsell, win-back flows, churn prevention. Honest about paywall-everywhere (gates everything aggressively), free-forever-trap (no upgrade path surfaces), and value-triggered-upgrade (paywall surfaces at moments of demonstrated value) patterns. Triggers on upgrade flow, paywall, free-to-paid, freemium conversion, trial conversion, plan upgrade, subscription upgrade, win-back flow, churn prevention. Also triggers when free-to-paid conversion is low, when paywalls are blocking the wrong moments, or when upgrade flows are being scoped for the first time.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions "paywall," "upgrade screen," "upgrade modal," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," "in-app pricing," "free users won't upgrade," "trial to paid conversion," or "how do I get users to pay." Use this for any in-product moment where you're asking users to upgrade. Distinct from public pricing pages (see cro) — this focuses on in-product upgrade moments where the user has already experienced value. For pricing decisions, see pricing.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions "paywall," "upgrade screen," "upgrade modal," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," "in-app pricing," "free users won't upgrade," "trial to paid conversion," or "how do I get users to pay." Use this for any in-product moment where you're asking users to upgrade. Distinct from public pricing pages (see cro) — this focuses on in-product upgrade moments where the user has already experienced value. For pricing decisions, see pricing.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Upgrade gstack to the latest version. Detects global vs vendored install, runs the upgrade, and shows what's new. Use when asked to "upgrade gstack", "update gstack", or "get latest version". Voice triggers (speech-to-text aliases): "upgrade the tools", "update the tools", "gee stack upgrade", "g stack upgrade".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Update gstack by detecting how it is installed, refreshing registered installations, and handling project copies and version migrations. Receive a summary of user-facing changes, along with installation-specific recovery information if an upgrade fails.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Upgrade an existing gstack installation
• Sync a project copy with the primary installation
• Review release changes after an upgrade

Upgrade an existing Storybook installation to version 11.0 or later using the official upgrade guide. If the latest stable release is below 11.0, the skill uses the 11.0 alpha, a prerelease version.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Upgrade an existing Storybook installation
• Meet a Storybook 11.0 minimum version requirement
• Use the 11.0 alpha when stable releases are below 11.0

Update context-mode from GitHub, rebuild and reinstall it, and configure hooks that connect it to the agent environment. Review the actual version and upgrade results in a checklist, then restart the session.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Update context-mode to the latest version
• Repair context-mode hooks and settings
• Review upgrade results and the installed version

Update outdated project packages on an isolated branch, handle changes that break compatibility, and run installation, code checks, builds, tests, and security audits. Open a pull request only after every required check passes, with deferred upgrades recorded.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Run a weekly dependency update sweep
• Plan migrations for major package upgrades
• Create an update pull request after verification

Manage KubeSphere extensions from discovery through installation, configuration, upgrades, and removal. Check dependencies and exact versions, prepare an InstallPlan deployment resource, and inspect status and logs to investigate installation or upgrade failures.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Find extensions and available versions
• Install a specific extension version
• Change settings or upgrade an extension

When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions "paywall," "upgrade screen," "upgrade modal," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," or "in-app pricing." Distinct from public pricing pages (see page-cro) — this skill focuses on in-product upgrade moments where the user has already experienced value.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions "paywall," "upgrade screen," "upgrade modal," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," or "in-app pricing." Distinct from public pricing pages (see page-cro) — this skill focuses on in-product upgrade moments where the user has already experienced value.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Quando o usuário quer criar ou otimizar paywalls in-app, telas de upgrade, modais de upsell ou feature gates. Use também quando o usuário mencionar "paywall", "tela de upgrade", "modal de upgrade", "upsell", "feature gate", "converter free para paid", "conversão freemium", "tela de expiração de trial", "tela de limite atingido", "prompt de upgrade de plano" ou "preço in-app". Distinto de páginas de preço públicas (veja page-cro) — esta skill foca em momentos de upgrade in-product onde o usuário já experimentou valor.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.