Add D&D scene description extractor

This commit is contained in:
2026-07-23 20:09:59 +00:00
parent 2f36b7c3b6
commit cd29265d5d
14 changed files with 876 additions and 0 deletions

View File

@@ -0,0 +1,40 @@
id: dnd.scene_descriptions
version: "v1"
default_profile: gemini-2-flash
inputs:
- name: transcript
required: true
content_type: application/json
- name: players
required: false
content_type: text/plain
- name: party
required: false
content_type: text/plain
- name: glossary
required: false
content_type: text/plain
messages:
- role: system
content_file: ./sharedassets/common-dnd-system.md
- role: user
content_file: ./sharedassets/common-dnd-identity.md
cache_control:
type: ephemeral
- role: user
content_file: ./sharedassets/common-dnd-references.md
cache_control:
type: ephemeral
- role: user
content_file: ./task.md
- role: user
content_file: ./instructions.md
cache_control:
type: ephemeral
- role: user
content_file: ./sharedassets/common-dnd-transcript.md
output:
format: json
validation_mode: json_schema
schema_path: dnd_scene_descriptions_llm.v1.json
repair_attempts: 0

View File

@@ -0,0 +1,9 @@
Choose exactly one kind: combat, narrative, recap, or meta. When a chunk is
mixed, use this precedence: combat, then recap, then meta, then narrative.
The title should identify the central event or subject. The summary should
describe only what the accepted chunk establishes. Campaign references may
disambiguate names but never add events or lore.
Do not return identifiers, source identifiers, source ranges, unit identifiers,
participants, confidence, or any fields besides kind, title, and summary.

View File

@@ -0,0 +1,5 @@
Describe exactly one accepted Dungeons & Dragons scene from the supplied
transcript chunk. The complete chunk is the evidence boundary: do not split it
into multiple scenes or use facts that are not supported by it.
Return one kind, one concise title, and one concise summary.