orchardcore-ai-prompting

Orchard Core AI Prompting

Choose the correct template surface

Use prompt files for reusable rendered instructions, and use AI profile templates for reusable Orchard-managed profile defaults. They are related but are not interchangeable.

Need	Use
Reuse a Liquid-rendered prompt in a profile, interaction, or script	A prompt file discovered by CrestApps.OrchardCore.AI.Prompting
Prepopulate a new AI profile with provider, deployment, capability, and chat settings	An AIProfileTemplate with Source = Profile
Maintain a reusable system-message template in the AI template catalog	An AIProfileTemplate with Source = SystemPrompt

AIProfileTemplate is a SourceCatalogEntry. Its Orchard manager is INamedSourceCatalogManager<AIProfileTemplate>, not INamedCatalogManager<AIProfileTemplate>. Recipes that import one must supply the Name, DisplayText, and Source fields. The Name plus Source pair identifies an existing entry when ItemId is absent.

Enable the right feature

Enable CrestApps.OrchardCore.AI.Prompting when editors need to select prompt files in AI profiles, profile templates, or chat interactions. The base AI feature owns the AIProfileTemplate catalog and its Templates screen.

{
  "steps": [
    {
      "name": "Feature",
      "enable": [
        "CrestApps.OrchardCore.AI",
        "CrestApps.OrchardCore.AI.Prompting"
      ],
      "disable": []
    }
  ]
}

The prompting feature replaces the default template service with an Orchard-aware service. It filters module prompt files by the active tenant's enabled features and de-duplicates template IDs case-insensitively.

Author prompt files

Put prompt files in an Orchard module at:

Templates/Prompts/

The module provider reads assets below that directory. A root-level prompt is associated with the module's default feature. A prompt in a first-level subdirectory is associated with the feature whose ID is that subdirectory name, so it is available only while that feature is enabled.