What problem does it solve? Upgrading a CopilotKit v1 application to v2 involves a ground-up rewrite: hooks are renamed, packages are consolidated, the GraphQL protocol is replaced by AG-UI, and service adapters are removed. This Skill guides that migration systematically so no deprecated API is missed. ## Core Features & Use Cases - Deprecation Mapping: Complete tables mapping every v1 hook, component, runtime class, and type to its v2 replacement (e.g., useCopilotAction to useFrontendTool, CopilotKit to CopilotKitProvider). - Before/After Code Examples: Detailed migration patterns for providers, hooks, runtime configuration, and endpoint setup, including the shift from service adapters to BuiltInAgent and Hono-based createCopilotEndpoint. - Breaking Changes Reference: Documents protocol changes (GraphQL to AG-UI/SSE), Zod-based parameter schemas replacing v1 parameter descriptors, and removed packages like @copilotkit/react-textarea. - Use Case: A team with a production Next.js app using useCoAgent, CopilotChat, and OpenAIAdapter can follow the workflow to audit imports, replace deprecated APIs, and reconfigure the runtime for v2. ## Quick Start Migrate my CopilotKit v1 app to v2 by scanning for deprecated hooks and updating the runtime configuration.