Skill UI

This guide outlines the process of migrating codebase dependencies and logic when upgrading the Ideogram API from legacy versions (V1/V2) to the robust V3 endpoints. It addresses critical breaking changes, including the shift from JSON body to multipart/form-data, changes in model naming, aspect ratio syntax, and the integration of new V3 features like rendering speed and style presets. Provides structured code adapters for smooth transition.

This comprehensive guide walks developers through migrating complex LLM codebases from raw SDK calls (OpenAI, Anthropic) or legacy frameworks (LlamaIndex) to the structured LangChain framework. It covers code assessment, pattern-by-pattern migration, advanced agent construction, robust tool calling, and transforming custom RAG pipelines into scalable, standardized chains.

Provides a senior migration architect workflow that researches legacy codebases, maps bounded contexts, and writes Strangler Fig-based modernization roadmaps so other teams can incrementally reshape systems.

A comprehensive guide for safely migrating monolithic or aging codebases. It details incremental modernization strategies, dependency mapping, and the implementation of the Strangler Fig pattern. Learn how to build safety nets using characterization tests, manage rollouts with feature flags, and achieve zero-downtime refactoring to reduce technical debt without business disruption.

A comprehensive guide detailing advanced strategies for migrating complex, rule-based automations from platforms like Zapier, Make, n8n, or custom codebases to Lindy AI. It teaches users how to redesign workflows, leveraging AI agents to replace rigid conditional logic with adaptable reasoning, ensuring a smooth and intelligent transition across multiple phases.

This skill guides developers on migrating their codebase from direct OpenAI API calls to using OpenRouter. By making minimal changes—primarily updating the base URL and API key—users gain access to over 400 models from multiple providers (including Anthropic and Google) through a unified SDK interface, ensuring high compatibility and flexible model switching.

This skill automates the entire software development process overnight. By leveraging mandatory Git hooks, it strictly enforces Test-Driven Development (TDD). Use this when complex features need building, large codebases need refactoring, or bugs need fixing autonomously, guaranteeing that every commit passes rigorous testing cycles and meets high production-ready standards.

This skill performs deep, line-by-line scanning of an entire codebase to understand its architecture, patterns, and dependencies. It systematically identifies critical issues across security vulnerabilities (SQL injection, secrets), performance bottlenecks (N+1 queries, caching), architectural flaws, and code quality gaps. It then automatically refactors and fixes all identified issues, transforming the code into professional, production-grade, enterprise-level quality.

Showcases modern Python practices, covering strict 3.12 type hints, dataclasses vs Pydantic decisions, asyncio/httpx patterns, src-layout projects, pyproject tool configs, virtual env workflows, and pytest guidance for reliable codebases.

This skill guides developers through modernizing React applications. It covers migrating from class components to functional components using hooks, upgrading React versions, adopting concurrent features (like Suspense), and applying automated refactoring techniques using codemods. It is essential for maintaining high-performance, modern React codebases and integrating TypeScript.

This skill functions as an expert technical writer, generating comprehensive and structured README.md documentation for software projects. It meticulously analyzes the codebase, identifying project structure, tech stack, prerequisites, dependencies, and deployment pipelines, ensuring users receive a complete guide for local setup and production deployment.

Guidelines for responding to code review feedback with technical rigor: read every comment, restate requirements, verify against the codebase, ask clarifying questions, push back when technically needed, and implement fixes one at a time with testing.