natural-dialogue-techniques

wordflowlab/novel-writer-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/wordflowlab/novel-writer-skills --skill natural-dialogue-techniques
0 commentsdiscussion
summary

每个角色都应该有独特的声音:

skill.md

自然对话写作技巧

核心原则

通过语言展现角色

每个角色都应该有独特的声音:

  1. 用词选择

    • 受过教育的 vs 随意的
    • 正式的 vs 俚语
    • 技术术语 vs 日常语言
    • 角色背景决定词汇
  2. 句子结构

    • 短/断断续续 vs 长/流畅
    • 完整句子 vs 片段
    • 简单结构 vs 复杂从句
    • 反映思维方式
  3. 言语模式

    • 打断、停顿、重复
    • 口头禅和填充词
    • 独特的措辞习惯
    • 文化和地域特色
  4. 不说什么

    • 回避的话题
    • 说谎的模式
    • 沉默的时刻
    • 未说出口的含义

潜台词胜过直白

角色的意思 vs 说的话:

❌ 直白对话(说教式)

"我对你生气,因为你昨晚对我撒谎了关于你去哪里。"

✅ 富含潜台词的对话

"你的商务会议开得怎么样?"
"很好。"
"我确定是这样。"

为什么更好

  • 让读者参与推理
  • 创造张力和不适
  • 更真实(人们避免直接冲突)
  • 展示角色动态

潜台词的层次

表面层:字面意义 情感层:真实感受 关系层:权力和亲密度 主题层:更大的故事意义

打断和重叠

真实对话不是有序的:

使用打断

"听着,我知道你认为——"
"你不知道我在想什么。"
"——但如果你让我说完——"
砰的一声,远处的门关上了。
"算了。" 她转身离开。

何时使用打断

  • 情绪高涨时
  • 急迫或恐慌
  • 权力斗争
  • 展示关系动态

思维打断言语

"我只是想说——" 他的脸闪过什么。"没事。不重要。"

效果

  • 展示内在冲突
  • 创造神秘感
  • 暗示隐藏信息
  • 角色自我审查

常见错误

❌ 信息倾倒

问题:角色说话只是为了传达信息给读者

坏例子

"如你所知,鲍勃,我们从 2015 年高中时就是朋友,
当时我们都加入了篮球队,然后我们一起去了斯坦福,
在那里学习工程学..."

好例子

"还记得你三年级那个压哨球吗?"
鲍勃笑了。"教练还在谈论它。"

解决方法

  • 在行动中揭示信息
  • 角色只说他们会说的话
  • 使用简短的暗示而非完整历史
  • 让读者拼凑背景

❌ 每个人听起来都一样

问题:所有角色使用相同的词汇和言语模式

解决方法:为每个主要角色创建"声音表"

声音表示例

角色 句子长度 词汇 怪癖 避免什么
张医生 中长,复杂 正式,医学术语 解释过度 俚语
李学生 短,片段 随意,网络语言 "就是说"、"懂吧" 承认不知道
王老板 简短,命令式 商业,直接 很少浪费词 解释自己

❌ 随意言语中的完美语法

太正式

"我要去商店。你想让我为你买些什么吗?"

自然

"去商店。要我带点啥吗?"

口语化技巧

  • 缩略(想要 → 想,去 → 咱)
  • 省略词语(我去商店 → 去商店)
  • 片段句子
  • 口头填充词(嗯、呃、那个)

❌ 用对话进行叙述

问题:角色说出应该是叙述的内容

坏例子

"我站起来,走向门,打开它。是送货员。"

这不是对话

  • 人们不会叙述自己的行动
  • 这是作者偷懒
  • 使用实际叙述或展示

高级技巧

对话作为行动

使用言语标签展示角色状态:

"随便吧。" 她嘀咕道。(被击败)
"随便吧!" 她厉声说道。(生气)
"随便吧..." 她的声音渐渐消失。(不确定)

超越"说"

  • 低语、嘀咕、咆哮(音量)
  • 厉声、尖叫、吼叫(强度)
  • 讥讽、嘲笑、低语(语调)
  • 但不要过度使用 - "说"通常就够了

沉默作为对话

有时不说什么很重要:

"你爱我吗?"
他看着自己的鞋子。

沉默的力量

  • 说出言语无法说出的
  • 创造紧张
  • 展示不适或痛苦
  • 让读者填补

动作打破对话

不要让角色成为说话的头:

"这不是我想要的。" 她把杯子推开。"不是这样的。"

他在房间里踱步。"那你想要什么?"

"我——" 她的手握紧了桌边。"我不知道。"

效果

  • 打破单调
  • 展示身体语言
  • 添加视觉元素
  • 创造节奏变化

对话目的

每段对话应该至少做到以下一项:

  1. 揭示角色

    • 展示性格
    • 揭示动机
    • 显示关系
    • 表明成长
  2. 推进情节

    • 提供重要信息
    • 做出决定
    • 创造冲突
    • 解决问题
  3. 建立氛围

    • 设定基调
    • 创造紧张
    • 提供幽默
    • 深化情感
  4. 展示冲突

    • 目标对立
    • 误解
    • 权力斗争
    • 隐藏的议程

如果对话不做这些:删除它

特殊场景的对话

争吵/冲突

有效技巧

  • 短句,快速来回
  • 打断频繁
  • 言语变得更尖锐
  • 可能说出后悔的话
  • 升级然后冷静(或爆发)
"你总是这样。"
"这样怎样?"
"假装——"
"我没有假装任何事!"
"——假装你在乎!"

浪漫/亲密

有效技巧

  • 柔和的语调
  • 不完整的句子(情绪)
  • 身体亲近描述
  • 潜台词丰富
  • 脆弱性
"我只是..." 他的拇指擦过她的下巴。"我不想搞砸这个。"

"那就别搞砸。" 她对他微笑。"简单。"

"简单。" 他笑了。"对。"

悬疑/紧张

有效技巧

  • 低语或简短的话
  • 不完整的想法
  • 打断(外部威胁)
  • 加载停顿
  • 说不出的恐惧
"你听到那个了吗?"

静默。然后:远处的脚步声。

"我们需要——"

一根树枝折断。两人都僵住了。

与 Novel-Writer 命令集成

/specify

  • 为主要角色定义独特的声音
  • 识别关键对话场景
  • 计划主要通过对话揭示什么

/plan 期间

  • 绘制高紧张度对话场景
  • 计划信息通过对话揭示
  • 设计角色声音弧(他们如何改变说话方式)

/write

  • 自动应用角色声音一致性
  • 检查信息倾倒
  • 建议潜台词机会
  • 根据角色档案验证对话

/analyze 期间

  • 检查角色声音一致性
  • 识别直白/说教对话
  • 验证每段对话都有目的
  • 建议可以加强的领域

对话写作检查清单

  • 每个角色都有独特的声音
  • 对话推进情节或揭示角色
  • 使用潜台词而非直白
  • 包括自然的打断和重叠
  • 随意言语听起来随意
  • 没有信息倾倒
  • 动作打破大块对话
  • 沉默在适当的地方使用
  • 言语标签多样但不分散注意力
  • 每段对话都有明确目的

修订技巧

大声朗读

  • 听起来自然吗?
  • 你会被绕口令绊倒吗?
  • 节奏流畅吗?

掩盖法

  • 遮住言语标签
  • 你能从对话中分辨出是谁说的吗?
  • 如果不能,角色声音不够独特

目的测试

  • 这段对话达到什么目的?
  • 没有它会失去什么?
  • 可以更短、更锋利吗?

记住:伟大的对话感觉轻松但经过精心设计。它揭示的比说的更多,推进故事同时保持真实,并且每个字都有目的。少即是多 - 削减到精髓。

how to use natural-dialogue-techniques

How to use natural-dialogue-techniques on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add natural-dialogue-techniques
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/wordflowlab/novel-writer-skills --skill natural-dialogue-techniques

The skills CLI fetches natural-dialogue-techniques from GitHub repository wordflowlab/novel-writer-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/natural-dialogue-techniques

Reload or restart Cursor to activate natural-dialogue-techniques. Access the skill through slash commands (e.g., /natural-dialogue-techniques) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.562 reviews
  • Neel Sethi· Dec 20, 2024

    Registry listing for natural-dialogue-techniques matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Harper Nasser· Dec 8, 2024

    Keeps context tight: natural-dialogue-techniques is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Mateo Tandon· Dec 4, 2024

    I recommend natural-dialogue-techniques for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Amina Mehta· Nov 27, 2024

    Registry listing for natural-dialogue-techniques matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Sofia Chen· Nov 23, 2024

    Useful defaults in natural-dialogue-techniques — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Aisha Desai· Nov 11, 2024

    Keeps context tight: natural-dialogue-techniques is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Amina Bhatia· Oct 18, 2024

    Useful defaults in natural-dialogue-techniques — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Aisha Dixit· Oct 14, 2024

    Registry listing for natural-dialogue-techniques matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Alexander Robinson· Oct 2, 2024

    I recommend natural-dialogue-techniques for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Mateo Johnson· Sep 21, 2024

    Solid pick for teams standardizing on skills: natural-dialogue-techniques is focused, and the summary matches what you get after install.

showing 1-10 of 62

1 / 7