Zonghao Yuan
0e4c2ebef4
Squash-merge the cloudflare-migration branch (7 commits by Kai ki) into staging with conflict resolution, feature integration, and bug fixes. Engine: - Paradigm D: single-stream Writer replacing dual-phase Plan/Beats - Delete Architect agent; story bible generated via Writer <plan> tag - Modular prompt architecture (segments/registry/builder) - StreamRouter for tagged stream splitting (<plan>/<story>/<choices>) Infrastructure: - Cloudflare Workers deployment (wrangler.jsonc, OpenNext adapter) - D1 database schema + Drizzle ORM (scaffolded, not yet active) - R2 storage helpers (scaffolded, not yet active) - Story persistence API routes + client-side persistence BYOK (Bring Your Own Key): - /api/llm/user-proxy with SSRF-protected LLM proxy (+ requireUser auth) - CORS-aware fetch in ai-client: auto-detect CORS failure, fallback to server proxy transparently via OpenAI SDK custom fetch - BYO config support added to classify-freeform and vision routes - SettingsModal CORS privacy notice (keys never logged/stored) SSE streaming: - engineClient.ts: fetchSSE helper for progressive scene events - startSession/requestScene accept optional emit callback - Fix SSE error event field name (error → message) in scene/start routes i18n integration: - Wire buildLanguageDirective into paradigm D's prompt builder - Update corsNotice i18n keys (zh-CN/en/ja) with CORS proxy privacy text - Preserve Session.language + LanguageSwitcher from i18n commit Co-authored-by: Kai ki <155355644+zbf1009@users.noreply.github.com> Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
30 lines
1.7 KiB
TypeScript
30 lines
1.7 KiB
TypeScript
import type { PromptSegment } from "../../types";
|
|
|
|
export const WRITER_DIALOGUE: PromptSegment = {
|
|
id: "writer-dialogue",
|
|
name: "对白准则",
|
|
type: "style-guideline",
|
|
agent: "writer",
|
|
zone: "stable",
|
|
order: 130,
|
|
enabled: true,
|
|
editable: true,
|
|
category: "对白",
|
|
content: `═══════════════════════════════════════════════════════════════════
|
|
对白准则（让角色的话有灵魂）
|
|
═══════════════════════════════════════════════════════════════════
|
|
# 对白格式：
|
|
- NPC 对白写成 \`角色名：「台词」\` 独占一段（全角冒号 + 直角引号），让系统能归属说话人
|
|
- 对白和描写分离、穿插交错——台词单独成段，它前面的动作/环境描写另起一段旁白，不要把大段描写和对白挤在同一段
|
|
|
|
# 对白润色：
|
|
- 确定角色的对话主题——主题可能是集中或发散的，但必然有其目的，契合角色的目的 / 阅历 / 性格
|
|
- 台词是生活化的、更具真实感的——角色可能语塞 / 词不达意 / 词穷 / 口是心非
|
|
- 安排渐进式的话题推进，以及情绪 / 态度的变化和反应
|
|
- 每个角色有自己的口癖、节奏、用词习惯——不要让所有角色说一样的话
|
|
|
|
# 角色表现准则：
|
|
- 角色务必有生动有趣的生活化表现，不会呆板、僵硬、机械化
|
|
- 无论角色人设如何，对白绝**不应**采用数据分析或学术报告式的口吻`,
|
|
};
|