508 skills · sorted by relevance
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.
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.
Extract unwritten coding conventions from an existing project and turn them into an AI style rules file. Resolve conflicting patterns with the user, identify example files, and update the rules as the codebase changes.
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.
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.
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.
Migrate legacy .NET project files to SDK-style format, reducing repetitive XML and explicit file lists. Convert package references, move assembly metadata into project settings, and consolidate shared build and package settings across multiple projects.
Investigate authentication gaps across single sign-on, APIs, and legacy login endpoints. The skill helps map entry points, compare their protections, test token trust between portals, and document whether a flaw grants access to protected accounts or functions.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
既存コード・既存関数・既存モジュールの暗黙契約を抽出するスキル。 戻り値型、副作用、例外、前提条件、境界条件、環境依存挙動を確認し、 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.
The English summary is being prepared. Showing the original description.
Documents a legacy workflow for extracting reusable solutions from Claude Code sessions and saving them as learned skills. Useful for reviewing existing setups and extraction settings; this version is deprecated in favor of continuous-learning-v2.
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.
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.
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.
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.
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.
Upgrade MSTest v1 or v2 projects to v3, including partially completed migrations. Update packages, repair affected assertions and test data, replace legacy settings, and compare test results while preserving the existing test runner.
Assess on-premises SharePoint Server for exposed information, legacy login paths, and conditions associated with known vulnerabilities. It guides evidence collection and helps distinguish meaningful security findings from misleading error messages.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.