'migrate' 검색 결과

Migrate workloads from Google Cloud Platform to AWS — plus AI and agentic workloads from any provider. Triggers on: migrate from GCP, GCP to AWS, move off Google Cloud, migrate Terraform to AWS, migrate Cloud SQL to RDS, migrate GKE to EKS, migrate Cloud Run to Fargate, migrate App Engine to Elastic Beanstalk, migrate from OpenAI to Bedrock, move off OpenAI, switch from ChatGPT API to AWS, migrate from Gemini to Bedrock, migrate LangChain to Bedrock, migrate LangGraph to AWS, migrate agentic workloads to AWS, move AI workloads to AWS, migrate my AI app to AWS. Runs a 6-phase process: discover GCP resources from Terraform, app code, or billing exports, then clarify, design, estimate costs, generate artifacts, and collect feedback. Clarify must finish before Design, Estimate, or Generate. Do not use for: Azure migrations (see azure-to-aws), on-premises migrations, AWS-to-GCP reverse migration, general AWS architecture advice without migration intent, or GCP-to-GCP refactoring.

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

Migrate workloads from Google Cloud Platform to AWS — including AI and agentic workloads regardless of cloud provider. Triggers on: migrate from GCP, GCP to AWS, move off Google Cloud, migrate Terraform to AWS, migrate Cloud SQL to RDS, migrate GKE to EKS, migrate Cloud Run to Fargate, Google Cloud migration, migrate from OpenAI to Bedrock, move off OpenAI, switch from ChatGPT API to AWS, migrate from Gemini to Bedrock, migrate LangChain to Bedrock, migrate LangGraph to AWS, migrate agentic workloads to AWS, move AI workloads to AWS, migrate my AI app to AWS. Runs a 6-phase process: discover GCP resources from Terraform files, app code, or billing exports, clarify migration requirements, design AWS architecture, estimate costs, generate migration artifacts, and collect optional feedback. Clarify must finish before Design, Estimate, or Generate. Includes AI provider migration guidance (for example, OpenAI to Amazon Bedrock) by selecting closest-fit Bedrock model families for required modality, latency/quality targets, context windows, and cost constraints. Model mapping is compatibility-guided, not 1:1 parity; validate prompts, tool-calling behavior, and eval metrics before cutover. Do not use for: Azure or on-premises migrations to AWS, AWS-to-GCP reverse migration, general AWS architecture advice without migration intent, GCP-to-GCP refactoring, or multi-cloud deployments that do not involve migrating off GCP.

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

Import existing notes and agent instructions into LifeOS by splitting content into sections and proposing destinations. Review uncertain classifications, approve selected groups, and retain source information alongside the imported material.

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

• Importing Obsidian or Notion exports into LifeOS
• Moving notes from an older LifeOS installation
• Reviewing and importing CLAUDE.md or Cursor rules

Migrate workloads from Heroku to AWS. Triggers on: migrate from Heroku, Heroku to AWS, move off Heroku, migrate Heroku Postgres to RDS, migrate Heroku Redis to ElastiCache, migrate Heroku Kafka to MSK, migrate dynos to Elastic Beanstalk, migrate dynos to Fargate, migrate Heroku Private Space, Heroku to ECS, leave Heroku, what-if workshop, compare migration scenarios, workshop mode. Runs a 6-phase process: discover Heroku resources live via the authenticated Heroku CLI (read-only, consent-gated) and/or from Terraform, Procfile/app.json, and billing exports, then clarify, design, estimate costs, generate artifacts, and collect feedback. Clarify must finish before Design, Estimate, or Generate. An optional post-Estimate what-if workshop reprices region/HA/compute/Graviton scenarios. Do not use for: GCP migrations (see gcp-to-aws), Azure migrations (see azure-to-aws), AWS-to-Heroku reverse migration, general AWS architecture advice without migration intent, or Heroku-to-Heroku refactoring.

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

Finish a NanoClaw v1-to-v2 migration after the migration script completes. The skill checks real message routing, assigns owner access, coordinates legacy memory migration, reviews container settings, and helps decide how to carry over customizations.

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

• Finish follow-up work after the v2 migration script
• Review owner permissions and sender access
• Migrate legacy memory and check container settings

Migrate workloads from Microsoft Azure to AWS. Triggers on: migrate from Azure, Azure to AWS, move off Azure, migrate AKS to EKS, migrate App Service or Azure VMs to AWS compute, migrate Azure SQL or Azure Database to RDS, migrate Cosmos DB to DynamoDB, migrate Azure OpenAI to Bedrock, move Azure AI or agentic workloads to AWS, estimate AWS costs for my Azure infrastructure, what-if workshop. Runs a 6-phase process: discover Azure resources from Terraform, the live `az` CLI, app code, and billing exports, then clarify, design, estimate costs, optionally reprice scenarios, generate artifacts, and collect feedback. Clarify gates Design, Estimate, and Generate; Generate is opt-in at the post-Estimate decision gate. Bicep/ARM discovery is not yet implemented; a Bicep/ARM-only workspace halts. Do not use for: GCP migrations (see gcp-to-aws), Heroku migrations (see heroku-to-aws), general AWS architecture advice (see architect-for-startups), AWS-to-Azure reverse migration, or Azure-to-Azure refactoring.

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

AI-DLC環境の v2→v3 移行を実行するスキル。 プリフライト検証、config/state 変換、アーカイブ索引生成を行う。 v1 環境は v2-maintenance branch の aidlc-migrate を案内する。 Use when the user says "start migrate", "aidlc migrate", "マイグレーション".

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

Assess and migrate cross-cloud workloads to Azure with reports and code conversion. Supports Lambda→Functions, Beanstalk/Heroku/App Engine→App Service, Fargate/Kubernetes/Cloud Run/Spring Boot→Container Apps. WHEN: migrate Lambda to Functions, AWS to Azure, migrate Beanstalk, migrate Heroku, migrate App Engine, Cloud Run migration, Fargate to ACA, ECS/Kubernetes/GKE/EKS to Container Apps, Spring Boot to Container Apps, cross-cloud migration.

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

Assess and migrate cross-cloud workloads to Azure with reports and code conversion. Supports Lambda→Functions, Beanstalk/Heroku/App Engine→App Service, Fargate/Kubernetes/Cloud Run/Spring Boot→Container Apps. WHEN: migrate Lambda to Functions, AWS to Azure, migrate Beanstalk, migrate Heroku, migrate App Engine, Cloud Run migration, Fargate to ACA, ECS/Kubernetes/GKE/EKS to Container Apps, Spring Boot to Container Apps, cross-cloud migration.

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

Flask-specific delta on top of python-foundation:sqlalchemy-patterns: Flask-SQLAlchemy extension setup, db.Model declarative models (3.x Mapped style and 2.x legacy db.Column), synchronous db.session lifecycle bound to the app context, Flask-Migrate integration. Used by flask-architect (model definitions) and flask-migrate-specialist (column finalization and migration). Activated automatically by flask-plugin/stack.md. Use this skill to: - Set up the SQLAlchemy and Migrate extensions with the app-factory pattern. - Write Flask-SQLAlchemy models with the db.Model base. - Query with db.session and manage the request-scoped session lifecycle. - Integrate Flask-Migrate for Alembic-based migrations managed via flask db commands. Do NOT use this skill for: - Framework-agnostic model, column, relationship, and querying rules — see python-foundation:sqlalchemy-patterns (load it first). - Flask routing and template/API patterns — see flask-plugin:flask-conventions. - Migration execution (flask db migrate, flask db upgrade) — that's flask-migrate-specialist's job.

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

Move or sync the hub role of an agent-plus-vault setup between computers, where an always-on desktop is the hub and laptops are satellites. Checklist with counters verified before and after, and it never migrates silently. Triggers: "/migrate", "/migrate check", "/migrate pack", "/migrate bootstrap".

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

Convert an existing SGLang cookbook page to shared templates driven by model configuration. Preserve its deployment commands and interactive choices, transfer eligible benchmark measurements, and check equivalence, links, and rendered behavior.

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

• Migrating a legacy SGLang cookbook page
• Moving deployment choices into model configuration
• Transferring reproducible benchmark measurements

Migrate Infrahub docs feature pages from the legacy topic+guide pair into a cleaner structure (single merged page, hub+spokes, or tutorial extraction). Supports both single-feature migrations (one feature like Profiles or Webhooks) and section-wide migrations (a whole section like Branches & Change Control with multiple features migrated together) when the team has agreed on a section-wide restructure plan. Trigger when the user names a specific feature or section to migrate (e.g. "let's migrate profiles", "start the Resource Manager migration", "do the entire Branches & Change Control section"). Each migration is its own branch off `demo/groups-diataxis-example`, its own PR back to that branch.

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

Move GitHub labels and Project V2 field values into organization-wide issue fields, structured properties shared across repositories. Review mappings and conflicts before migration, preserve existing values, and optionally remove migrated labels.

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

• Convert priority labels into a shared Priority field
• Copy project priorities and due dates into issue fields
• Preview migration changes without updating issues

Guide an RxJS 7 project to RxJS Next by testing existing behavior, reviewing how subscriptions start and end, and validating small batches of changes. Record approved behavior choices, verification results, and unresolved blockers in migration reports.

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

• Assess RxJS usage and test coverage before migration
• Plan how subscriptions and cleanup should behave
• Migrate code and TestScheduler tests in small batches

Move legacy NanoClaw memory and Claude auto-memory into a shared structure used across providers. The skill separates lasting facts from standing instructions, updates indexes, records each file's outcome, and verifies recall after approval.

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

• Migrating memory after a shared-memory update
• Organizing legacy CLAUDE.md and Claude auto-memory
• Separating lasting facts from standing instructions

Migrate Vue applications from Table v8 to v9 by checking table creation, rendering, and reactive state updates. Combine Vue-specific changes with the shared core migration checklist, then verify types and affected feature behavior.

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

• Upgrading Vue tables from v8 to v9
• Reviewing table creation and rendering changes
• Fixing reactive state updates after migration

Migrate TanStack Table from v8 to v9 in React by reviewing table creation, state updates, rendering, and shared application hooks. Provides a React-specific checklist and verification steps alongside the required core migration guidance.

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

• Upgrade a React table from v8 to v9
• Review state and rendering issues after migration
• Update shared table hooks and wrappers

Migrate Angular tables from Table v8 to v9 by reviewing table creation, rendering, state updates, and reusable app hooks. Provides an Angular checklist alongside the core migration checks needed for shared API changes.

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

• Upgrading an Angular table from v8 to v9
• Replacing createAngularTable with injectTable
• Reviewing signal-based state and FlexRender rendering

Migrate Solid tables from Table v8 to v9, covering creation, rendering, and reactive state reads. Helps review controlled updates, changing data, and enabled table features alongside the shared core migration checklist.

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

• Upgrading a Solid table from v8 to v9
• Replacing createSolidTable with createTable
• Fixing stale state after migration

Migrate Svelte tables from Table v8 to v9 by reviewing table creation, rendering, state handling, and shared hooks. The checklist also guides type checking and verification of data updates and enabled table features.

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

• Migrating Svelte tables from Table v8 to v9
• Replacing writable-store setup with runes and getters
• Reviewing rendering and state handling after migration

Migrate TanStack Table from v8 to v9 in Preact using its native package. Reviews compatibility aliases, table setup, state subscriptions, and rendering, with verification steps to check the upgraded implementation alongside the required core migration guidance.

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

• Upgrade a Preact table from v8 to v9
• Switch table imports to the native Preact package
• Review state and rendering issues after migration

Guide a TanStack Table migration from v8 to v9 in Lit applications. Review table construction, rendering helpers, state updates, and shared application hooks, alongside the required migration checks for the core library.

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

• Migrate a Lit table from v8 to v9
• Update TableController construction and render calls
• Review state updates during migration

Move browser tests from Cypress or Selenium to Playwright with file-by-file conversion and verification. The skill also adapts shared helpers and element selectors, updates CI workflows and documentation, and reports tests that need manual work.

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

• Migrate a Cypress test suite
• Convert Selenium tests to Playwright
• Try migration on a single test file