add-prompt-enhancement-guide
Author a prompt-enhancement system prompt for a new ecosystem and register/update it on the orchestrator's prompt-analysis service. Use when onboarding a new ecosystem (e.g. happyhorse, a new Flux variant, a new Wan video version) and the user provides the ecosystem key plus a reference link, model
Оригинален текст · няма потвърден превод на българскиПърво прочетете инструкцията.
Файлът се зарежда от посочения източник само по ваше действие. Можете да го прочетете тук, да го копирате или да го запазите като .md.
GitHub хранилище- Звезди на репото
- 7145
- Лиценз
- Не е посочен. Проверете в репозитория.
- Последна проверка на записа
- Няма посочена дата
Добавете в своя инструмент.
Командата отваря избора на skills от репозитория. Прочетете файла и условията на автора преди изпълнение.
npx skills add civitai/civitaiСтраницата копира текст. Не инсталира и не изпълнява нищо на устройството ви.
Откъс от SKILL.md
Началото на файла на автора, без превод.
Add Prompt Enhancement Guide
The orchestrator runs a prompt-analysis service that, per ecosystem, takes a user's prompt and produces structured feedback + an enhanced rewrite. Each ecosystem has its own system prompt tuned to the model's prompting conventions (tag vs natural-language, weight syntax, negative-prompt support, text rendering, camera/motion vocab for video, etc.).
This skill authors a new system prompt for an ecosystem the user names and (optionally) deploys it to the orchestrator.
Scope: image and video ecosystems only
Do not write guides for 3D, audio, or any other modality — tripo, hunyuan3d, polygen (image-to-3D) and ace (audio) are explicitly out of scope, as is anything else non-image/video that appears later. If the user names one, say it is out of scope and stop.
The guide template below is built entirely around subject / lighting / camera / composition / style. None of that describes "generate a mesh from this image" or "generate a song," so a guide written from this template for those modalities would be confidently wrong rather than merely thin. Leaving them on the built-in fallback is the deliberate choice.
Inputs the user must provide
-
Ecosystem key — the ecosystem's
keyfrompackages/civitai-shared/src/basemodel.constants.ts, lowercased.MiniMaxH3→minimaxh3,Flux1Kontext→flux1kontext,WanVideo-25-I2V→wanvideo-25-i2v,HyV1→hyv1. Confirm the key exists in that file before using it. (src/shared/constants/basemodel.constants.tsis a one-line re-export shim of the same module, not a stale duplicate — importing from either path is fine.)It is the AIR ecosystem value, lowercased — the same string that appears in
urn:air:<ecosystem>:....getAirEcosystemin air.ts is the single source for both:stringifyAIRuses it, and so doescreatePromptEnhancementStep. If you know a model's AIR, you know its prompt-analysis key.The consequence to watch:
getRootEcosystemfollowsparentEcosystemId, so a child ecosystem never appears in an AIR and never reaches prompt analysis. Pony, Illustrious, and NoobAI all arrive assdxl. CheckparentEcosystemIdbefore writing a guide — if the target has a parent, the guide belongs on the parent and has to serve every sibling.