port-pipeline

name	port-pipeline
description	Port custom model pipeline implementations to Diffusers using phased priorities: preserve behavior first, avoid new dependencies second, and keep device/attention handling configurable throughout. Use when migrating custom or non-Diffusers pipeline code into SD.Next repo-local pipeline files such as pipelines/model_<name>.py or pipelines/<model>/pipeline.py.
argument-hint	Provide source pipeline path, target SD.Next destination path, and target pipeline class name

Port Custom Pipeline To Diffusers

Port an existing custom model pipeline implementation into a Diffusers-compatible pipeline class with behavior parity and SD.Next-friendly conventions. This skill targets SD.Next repo-local pipeline ports only.

When To Use

• A user has a custom pipeline implementation and wants it ported to Diffusers
• Existing model code is runnable but not structured as a Diffusers pipeline
• The destination is SD.Next pipeline code under pipelines/model_*.py or pipelines/<model>/
• The task requires preserving generation behavior without introducing new dependencies
• The task requires removing hard-coded runtime assumptions (device or attention backend)

Guidance

• Consult .github/instructions/core.instructions.md for relevant core runtime and pipeline integration guidance before proceeding.

Mandatory Clarification Gate

Before implementation, confirm these required inputs with the user:

1. Path to the source custom pipeline implementation
2. Destination path in this SD.Next repository (typically under pipelines/)
3. Target pipeline class name