add-generation-support

Wire an existing ecosystem into the Civitai generation system with graph, handler, and router integration.

7.2k|734|Updated Oct 11, 2022
One-click install
npx skills add https://github.com/civitai/civitai --skill add-generation-support
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-generation-support
Source: https://github.com/civitai/civitai/tree/main/.claude/skills/add-generation-support
Command: npx skills add https://github.com/civitai/civitai --skill add-generation-support

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @civitai/client.

What problem does it solve?

Adding a new AI model ecosystem to Civitai's generation form requires coordinated edits across constants, data graphs, orchestrator handlers, discriminators, and routers — plus manual database seeding that is easy to miss, causing features to silently half-work.

Core Features & Use Cases

  • End-to-end wiring checklist: Updates basemodel.constants.ts, workflows.ts, ecosystem-graph.ts, and the ecosystems router in one guided pass.
  • Type-safe handler generation: Checks the latest @civitai/client package for ecosystem-specific input types before writing the handler, falling back to generic step templates when needed.
  • Graph structure guidance: Helps choose between single graphs, version-variant discriminators, and version-dependent defaults based on model research.
  • Post-onboarding DB steps: Provides the exact SQL for GenerationCoverage, GenerationBaseModel, and AuctionBase tables that must be seeded manually per environment.
  • Use Case: After onboarding a new video model ecosystem, use this Skill to make it appear in the generation form with correct sliders, aspect ratios, and a typed orchestrator handler.

Quick Start

Ask the assistant to add generation support for your ecosystem, providing the model version IDs and recommended settings from the model card.

Frequently Asked Questions about add-generation-support

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a new ecosystem to the Civitai generation form?

Add the ecosystem to ecosystemSupport and ecosystemSettings in basemodel.constants.ts, create a graph file and handler file, register them in ecosystem-graph.ts and the ecosystems router, then add the ecosystem to the correct workflow array in workflows.ts.

What is the difference between add-ecosystem and add-generation-support?

The add-ecosystem skill creates the ecosystem, base model, license, and family records. Add-generation-support runs afterward to wire that existing ecosystem into the generation form with graphs, handlers, and router cases.

Why does a new base model not appear as generatable after adding form support?

The GenerationBaseModel table is not derived from constants and must be seeded manually with the base model display name. File-less API checkpoints may instead need an EcosystemCheckpoints row keyed by ModelVersion id.

Should I use ecosystem-specific types from @civitai/client in the handler?

Yes, always check the latest published @civitai/client version for ecosystem-specific input types first, since they provide exact field shapes and strict enum literals. Fall back to generic ImageGenStepTemplate or VideoGenStepTemplate only when no types exist.

When should I add cross-ecosystem compatibility rules?

Add explicit crossEcosystemRules entries whenever LoRAs or other addons trained on one ecosystem should work on another, such as Pony LoRAs on Illustrious checkpoints. The parentEcosystemId relationship alone does not infer compatibility.

Why should slider defaults not be reset with a graph effect across variants?

An effect that sets slider values overwrites user-tuned localStorage values and also fires during server-side validation, replacing submitted input with defaults. Declare defaults on each subgraph's sliderNode instead and let zod clamping handle out-of-range values.