Skill UI

A comprehensive guide for developers upgrading the Lokalise Node.js SDK across major versions (e.g., v8 CommonJS to v9 ESM). This skill detects and resolves breaking changes, including module system shifts (require to import), updating package configurations, and modernizing pagination from offset to cursor-based methods, ensuring smooth API integration.

This deep-dive guide provides a comprehensive framework for migrating complex operational data into the MaintainX platform. It systematically guides users through assessing source data quality from legacy CMMS systems (like Maximo), spreadsheets, or custom databases. The process covers essential steps including data assessment, schema mapping, and executing robust ETL processes for work orders and assets, ensuring a smooth re-platforming transition.

Guides designing and implementing horizontal database sharding, covering key selection, migration planning, and cross-shard coordination for scalable systems.

This skill outlines a comprehensive, low-downtime process for migrating APIs between different versions, frameworks, or platforms. It guides the implementation of advanced architectural patterns like the Strangler Fig pattern, traffic shadowing, and canary deployments. Use this when upgrading a monolithic API to microservices or transitioning between incompatible API versions.

Automates migration guide creation by providing step-by-step documentation patterns, best practices, and validated snippets for APIs, user guides, and architecture docs.

A comprehensive guide for migrating existing AI integrations from providers like OpenAI or Anthropic to Mistral AI. This blueprint covers the entire lifecycle: initial assessment of AI touchpoints, detailed model mapping (e.g., gpt-4o to mistral-large), implementing a provider-agnostic adapter pattern, and executing controlled, feature-flag-controlled rollout plans for major refactoring projects.

This comprehensive skill guides developers through major version upgrades of the Mistral AI SDK. It specifically detects breaking changes, such as the shift from CommonJS to ESM, and provides detailed steps, automated code transformation scripts, and best practices for migrating existing code. Use this when jumping major SDK versions or refactoring complex Mistral integrations to ensure a smooth transition to the latest API.

Guides setting up modern Python projects with uv, ruff, ty, pytest, prek, and security checks, covering initialization, pyproject configuration, dependency and tool management, quick-start scripts, full project layout, and migrations from legacy tooling.

This guide provides essential, production-ready architectural patterns for building highly reliable Obsidian plugins. It addresses common development pitfalls such as managing typed settings with versioned migration, implementing safe vault operations (check-before-act), and handling event listeners to prevent memory leaks. Use these patterns when hardening your plugin for public release or refactoring for maximum stability.

A comprehensive guide for developers migrating and upgrading Obsidian plugins across major API versions. It covers critical steps such as auditing plugin compatibility, implementing version-aware settings migration logic (for user data persistence), replacing deprecated API calls (e.g., Vault, Editor, FileManager), and updating configuration files like manifest.json to ensure stability on new Obsidian releases.

This deep dive guide provides comprehensive strategies and detailed checklists for migrating to the OpenEvidence platform. It covers various migration methods, such as parallel run, Strangler fig, and Big bang approaches. The guide assists technical teams in planning the transition by addressing key areas including API mapping, data migration plans, rollback procedures, and performance baselines, ensuring a secure and smooth transition for healthcare IT systems.

This guide provides a comprehensive roadmap for migrating and upgrading integrations with the OpenEvidence clinical AI platform. It addresses critical API changes, such as schema restructuring (e.g., flat answers to structured evidence), version detection, and updated citation formats. Developers can use this knowledge to implement robust migration logic, ensuring that downstream clinical applications maintain high levels of accuracy and safety when accessing evolving medical evidence.