'legacy' 검색 결과

Document a local codebase with file references, architecture diagrams, and verified project commands. For legacy modernization, assess what still runs and create a phased migration plan with validation methods suited to each component’s current condition.

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

• Creating an onboarding guide for a codebase
• Mapping system architecture and dependencies
• Planning a legacy system migration or rewrite

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

기존 코드에 담긴 암묵적인 명명, 구성, 오류 처리 관례를 읽어 AI가 참고할 규칙으로 정리합니다. 방침의 충돌을 하나씩 확인하고 코드 변경 후 규칙 갱신도 지원합니다.

• 오래된 코드베이스에 AI를 도입할 때
• 암묵적인 코딩 규약을 문서화할 때
• 명명과 구성 방침의 충돌을 정리할 때

Prepare and publish releases of the Cline VS Code extension. Follow separate paths for stable, nightly, and emergency legacy releases, covering version selection, release notes, approval steps, packaged builds, and checks after publication.

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

• Preparing a stable extension release
• Creating a manual nightly build
• Publishing an emergency legacy hotfix

Migrate an existing Android app from the legacy Google Mobile Ads SDK to GMA Next-Gen SDK. The skill maps dependencies, imports, classes, and methods, and guides changes to initialization, ad callbacks, and UI thread handling.

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

• Replace legacy advertising SDK dependencies
• Update ad imports, classes, and method calls
• Adapt initialization and UI updates in callbacks

Plan and implement gradual upgrades of legacy systems while preserving existing business behavior. Map dependencies and risks, create migration stages and routing code, and prepare tests, monitoring, and rollback procedures to validate each step.

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

• Planning a gradual replacement of a legacy system
• Splitting services out of a monolith
• Upgrading a framework or language

Safely change and test untested codebases using Feathers' "Working Effectively with Legacy Code". Use when the user mentions "legacy code", "no tests", "untested codebase", "how do I test this", "seams", "characterization tests", "golden master", "sprout method", "afraid to change this code", "monster method", "dependency breaking", or "inherited a messy codebase". Also trigger when changing code without tests safely, getting a class under test when constructors, statics, or singletons block it, adding features to tangled modules, or planning incremental test coverage for an old codebase. Covers the legacy-code change algorithm, seams, characterization tests, sprout/wrap, and dependency-breaking techniques. For refactoring code that already has tests, see refactoring-patterns. For day-to-day code quality, see clean-code.

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

Port MATLAB Data Acquisition Toolbox code from the discouraged (legacy) session-based interface (daq.createSession, addAnalogInputChannel, startBackground, DataAvailable listeners, queueOutputData, wait) to the recommended DataAcquisition interface (daq("ni"), addinput, start, ScansAvailableFcn, write, preload). Use when migrating legacy DAQ scripts, converting session-API calls, working with DataAcquisition objects, writing multi-feature DAQ scripts that combine triggers, callbacks, continuous acquisition, or analog output. Also use when a user says their DAQ script "used to work" or "errors on R20XX", since modernizing legacy session-API code is a frequent fix for those failures. Trigger keywords: daq, DAQ, NI, session interface, addtrigger, addclock, ScansAvailableFcn, ScansRequiredFcn, daq.createSession, addAnalogInputChannel, startBackground, queueOutputData, DataAvailable, evt.Data, evt.TimeStamps, wait(d), preload, discouraged, legacy, modernize, R2020a.

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

Use when planning or implementing an intentional migration from JavaScript, jQuery, HTML/CSS, server-rendered templates, MPA legacy frontend code, or older framework code toward a modern frontend stack while preserving behavior. Do not use for routine legacy bug fixes that stay in the old stack; Chinese triggers include legacy projects, technology stack upgrades, jQuery migration.

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

既存コード・既存関数・既存モジュールの暗黙契約を抽出するスキル。 戻り値型、副作用、例外、前提条件、境界条件、環境依存挙動を確認し、 reuse前のリスクを可視化する。名前やコメントではなく実際の挙動から 契約を読み取り、不一致を分類し、再利用可否を判定する。 Use when reusing legacy code, verifying actual behavior of existing functions, or extracting implicit contracts before implementation. Covers: hidden contract, implicit contract, reuse risk, legacy behavior, 暗黙契約, 既存資産調査. Analyzes return types, side effects, exceptions, preconditions, boundary conditions, and environment-dependent behavior.

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

Claude Code 세션 종료 시 재사용할 해결 절차를 추출해 저장하는 구버전 방식을 설명합니다. 현재는 사용이 중단되어 기존 환경의 호환성과 설정을 확인하는 참고 자료로 활용합니다.

• 구버전 세션 종료 훅 설정을 확인합니다
• 추출 기준과 대상 분류를 조정합니다
• 저장된 학습 스킬을 검토합니다

Maintain legacy Java code that uses the deprecated Azure Communication CallingServer SDK. Compare old and replacement dependencies, client classes, and recording examples to plan a migration to Call Automation and identify APIs needing verification.

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

• Maintain legacy Java CallingServer code
• Compare dependencies and client class names
• Review existing call recording code

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

Read existing code to reconstruct system specifications, including architecture, data flows, APIs, and business rules. Produces documentation tied to code locations, separating observed behavior from inferences and questions that need clarification.

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

• Understand an undocumented legacy system
• Document existing APIs and business rules
• Map module dependencies and data flows

Assess Bluetooth Classic devices such as older car kits, industrial sensors, and audio accessories. The skill guides device discovery, service inspection, authentication checks, and known vulnerability assessment, helping document exposed functions and device-specific findings.

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

• Assessing older in-car Bluetooth devices
• Checking authentication on industrial device services
• Reviewing exposure to BlueBorne and KNOB

Create an evidence-based plan for modernizing an existing system. Analyze code and dependencies, research technology choices, and produce domain-specific migration plans with testing, rollback steps, and a consolidated roadmap for developers to execute.

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

• Planning a gradual replacement of a legacy system
• Comparing service separation and consolidation strategies
• Preparing a language or framework migration

Refactor legacy codebases, migrate outdated frameworks, and implement gradual modernization. Handles technical debt, dependency updates, and backward compatibility. Use PROACTIVELY for legacy system updates, framework migrations, or technical debt reduction.

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

Maintain classic ASP.NET applications on .NET Framework, including Web Forms, older MVC, and legacy hosting patterns, while planning realistic modernization boundaries. USE FOR: working in Web Forms, legacy MVC, or classic ASP.NET applications; reviewing old IIS-centric configuration and lifecycle behavior; planning migration toward ASP.NET Core. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.

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

Produces comprehensive summaries and insights about legacy codebases to help understand unfamiliar code. Use when onboarding to a new project, planning refactoring efforts, assessing code for acquisition/migration, or generating documentation for undocumented systems. Analyzes architecture, dependencies, code quality issues, and test coverage. Creates high-level overviews with architecture diagrams, key components, entry points, and actionable insights for understanding and improving legacy code.

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

Create, implement, or review legacy circuit mockups work with format, accessibility, performance, and visual-verification controls. Use when the requested deliverable depends on legacy circuit mockups.

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

Expert in understanding and navigating legacy codebases. Covers code archaeology techniques, finding hidden knowledge, mapping dependencies, and extracting understanding from code without documentation. Knows how to read the stories that old code tells. Use when "legacy code, old codebase, understand this code, archaeology, what does this do, no documentation, ancient code, " mentioned.

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

Phase E of a WinForms-to-Avalonia migration: verify behavioral parity against Phase A contracts, record intentional differences, validate supported environments and packaging, and make evidence-based legacy cutover decisions. Use only for an explicit migration when comparing the legacy and Avalonia implementations or when the orchestrator routes here. Do not delete legacy without the cutover checklist and explicit authorization.

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

Systematic framework for resurrecting and modernizing legacy codebases through archaeology, resurrection, and rejuvenation phases. Activate on "legacy code", "inherited codebase", "no documentation", "technical debt", "resurrect", "modernize". NOT for greenfield projects or well-documented active codebases.

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

Systematic framework for resurrecting and modernizing legacy codebases through archaeology, resurrection, and rejuvenation phases. Activate on "legacy code", "inherited codebase", "no documentation", "technical debt", "resurrect", "modernize". NOT for greenfield projects or well-documented active codebases.

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