Skip to content

[codex] Update emotion control page for S2 tags#82

Merged
Kilerd merged 1 commit into
mainfrom
docs/correct-emotion-control-tag
May 27, 2026
Merged

[codex] Update emotion control page for S2 tags#82
Kilerd merged 1 commit into
mainfrom
docs/correct-emotion-control-tag

Conversation

@Kilerd
Copy link
Copy Markdown
Contributor

@Kilerd Kilerd commented May 27, 2026

Summary

  • Switch the Emotion Control guide examples, tables, and troubleshooting copy to S2 bracket syntax.
  • Add S2-specific emotion list snippets so the S1 API reference can keep using the existing parenthesis snippets.
  • Clarify that S1 still requires parenthesis markers while this page intentionally shows S2 usage.

Validation

  • ./node_modules/.bin/prettier --check developer-guide/core-features/emotions.mdx snippets/emotion-list-basic-s2.mdx snippets/emotion-list-advanced-s2.mdx snippets/emotion-list-tones-s2.mdx snippets/emotion-list-effects-s2.mdx snippets/emotion-list-special-s2.mdx
  • npm run check:openapi
  • ./node_modules/.bin/mint validate currently fails on existing unrelated warnings for React imports in snippets/*.jsx and missing /snippets/snippet-intro.mdx from temp/essentials/reusable-snippets.mdx.

Summary by CodeRabbit

  • Documentation
    • Updated emotion control guide with refreshed syntax and expanded usage guidelines.
    • Added new reference tables for emotions, effects, tones, and special markers.
    • Enhanced best practices, placement guidance, and troubleshooting content.

Review Change Stack

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 27, 2026

📝 Walkthrough

Walkthrough

The PR updates the Emotion Control documentation to introduce S2 syntax, replacing S1 parenthesis-based markers with square-bracket cues. The main documentation page is rewritten across all sections—imports, usage guidance, placement rules, advanced techniques, best practices, and reference tables—while five new reference snippet files define emotion, effect, and tone mappings for the S2 system.

Changes

Emotion Control S2 Syntax Migration

Layer / File(s) Summary
Main documentation page S2 refactor
developer-guide/core-features/emotions.mdx
The core emotions page is updated across all sections: imports switch to -s2 variants; "How It Works" and "Tip" sections rewrite syntax from parentheses to brackets; a new "For S2" section describes placement rules; "Advanced Techniques" rewrites multi-emotion, transition, and intensity examples to bracket syntax; "Best Practices" list S2-specific constraints; "Common Use Cases" and "Troubleshooting" reference bracket placement; "Quick Reference" and "See Also" are updated to S2 combinations and adjusted descriptions.
S2 reference snippet tables
snippets/emotion-list-basic-s2.mdx, snippets/emotion-list-advanced-s2.mdx, snippets/emotion-list-effects-s2.mdx, snippets/emotion-list-special-s2.mdx, snippets/emotion-list-tones-s2.mdx
New S2 reference snippets define emotion-to-tag mappings with descriptions and usage guidance: basic emotions (Happy, Sad, etc. → [happy], [sad], etc.), advanced emotions (Disdainful through Resigned), effects/tones (Laughing, Whispering, Shouting), special markers (Pause, Audience Laughter), and tone presets (Hurried, Screaming, Soft).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

  • fishaudio/docs#56: Both PRs migrate emotion control documentation from S1 parenthesis syntax to S2 bracket syntax, updating guidance and examples in developer-guide/core-features/emotions.mdx.

Poem

🐰 From parentheses old to brackets bright,
Emotions now cue with S2 delight!
Square brackets dance where rounded ones did dwell,
Reference tables bloom—the new syntax to tell! 📚✨

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title '[codex] Update emotion control page for S2 tags' directly and clearly summarizes the main change—updating the emotion control documentation to use S2 bracket syntax instead of S1 parenthesis syntax.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/correct-emotion-control-tag

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

ESLint skipped: no ESLint configuration detected in root package.json. To enable, add eslint to devDependencies.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@mintlify
Copy link
Copy Markdown

mintlify Bot commented May 27, 2026

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
hanabiaiinc 🟢 Ready View Preview May 27, 2026, 8:08 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.

@Kilerd Kilerd marked this pull request as ready for review May 27, 2026 08:08
Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (5)
snippets/emotion-list-basic-s2.mdx (1)

1-27: 💤 Low value

Consider adding frontmatter to snippet files.

While this is an imported snippet rather than a standalone page, the coding guidelines state "Do not skip frontmatter on any MDX file." Consider adding minimal frontmatter with a title for consistency, even if the snippet is only used via imports.

As per coding guidelines: "Do not skip frontmatter on any MDX file".

📝 Suggested frontmatter addition
+---
+title: "Basic Emotions Reference (S2)"
+---
+
 | Emotion     | Tag             | Description             | Example Context             |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@snippets/emotion-list-basic-s2.mdx` around lines 1 - 27, This MDX snippet
file (snippets/emotion-list-basic-s2.mdx) is missing YAML frontmatter; add
minimal frontmatter at the very top of the file using the triple-dash block
(---) and include at least a title field (for example title: "Emotion List —
Basic S2") so the file complies with the "Do not skip frontmatter on any MDX
file" guideline and can be imported consistently.
snippets/emotion-list-advanced-s2.mdx (1)

1-28: 💤 Low value

Consider adding frontmatter to snippet files.

Similar to the basic emotions snippet, consider adding minimal frontmatter for consistency with the guideline that applies to all MDX files.

As per coding guidelines: "Do not skip frontmatter on any MDX file".

📝 Suggested frontmatter addition
+---
+title: "Advanced Emotions Reference (S2)"
+---
+
 | Emotion       | Tag               | Description              | Example Context        |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@snippets/emotion-list-advanced-s2.mdx` around lines 1 - 28, This MDX snippet
is missing frontmatter; add minimal YAML frontmatter at the top of
emotion-list-advanced-s2.mdx (above the table that starts with "| Emotion | Tag
| Description | Example Context |") — include at least a title and description
(for example: title: "Advanced Emotion List" and description: "Extended list of
emotion tags for snippets"), and any required canonical fields your project
expects (e.g., draft: false or tags: [snippets]) so the file complies with the
"Do not skip frontmatter on any MDX file" guideline.
snippets/emotion-list-special-s2.mdx (1)

1-8: 💤 Low value

Consider adding frontmatter to snippet files.

As with the other emotion snippets, consider adding minimal frontmatter for consistency with MDX file guidelines.

As per coding guidelines: "Do not skip frontmatter on any MDX file".

📝 Suggested frontmatter addition
+---
+title: "Special Effects Reference (S2)"
+---
+
 | Effect              | Tag                     | Description              |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@snippets/emotion-list-special-s2.mdx` around lines 1 - 8, Add a minimal YAML
frontmatter block to the top of this MDX snippet (emotion-list-special-s2.mdx)
so it follows the MDX guidelines; include at least a title and a type/collection
field (e.g., title: "Emotion List Special S2" and type: "snippet" or collection:
"emotion-snippets") before the table starting with the "Effect | Tag |
Description" header, ensuring the file now begins with the frontmatter block and
then the existing table content.
snippets/emotion-list-tones-s2.mdx (1)

1-8: 💤 Low value

Consider adding frontmatter to snippet files.

As with the other emotion snippets, consider adding minimal frontmatter for consistency with MDX file guidelines.

As per coding guidelines: "Do not skip frontmatter on any MDX file".

📝 Suggested frontmatter addition
+---
+title: "Tone Markers Reference (S2)"
+---
+
 | Tone       | Tag                 | Description          | When to Use                |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@snippets/emotion-list-tones-s2.mdx` around lines 1 - 8, This MDX snippet that
starts with the table header "Tone" is missing the required YAML frontmatter;
add a minimal frontmatter block at the top of the file (e.g., --- title:
"Emotion List: Tones S2" slug: "emotion-list-tones-s2" ---) following the
project's MDX frontmatter conventions so the file is consistent with other
emotion snippets and the "Do not skip frontmatter on any MDX file" guideline.
snippets/emotion-list-effects-s2.mdx (1)

1-13: 💤 Low value

Consider adding frontmatter to snippet files.

As with the other emotion snippets, consider adding minimal frontmatter for consistency with MDX file guidelines.

As per coding guidelines: "Do not skip frontmatter on any MDX file".

📝 Suggested frontmatter addition
+---
+title: "Audio Effects Reference (S2)"
+---
+
 | Effect        | Tag               | Description                  | Suggested Text |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@snippets/emotion-list-effects-s2.mdx` around lines 1 - 13, Add a minimal YAML
frontmatter block at the very top of the MDX file (above the table starting with
"| Effect | Tag | Description | Suggested Text |") containing required metadata
per guidelines (e.g., a title and any required fields like layout/description or
snippet identifier) so the file matches other emotion snippets; ensure the
frontmatter is valid YAML and sits before any Markdown/MDX content.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@snippets/emotion-list-advanced-s2.mdx`:
- Around line 1-28: This MDX snippet is missing frontmatter; add minimal YAML
frontmatter at the top of emotion-list-advanced-s2.mdx (above the table that
starts with "| Emotion | Tag | Description | Example Context |") — include at
least a title and description (for example: title: "Advanced Emotion List" and
description: "Extended list of emotion tags for snippets"), and any required
canonical fields your project expects (e.g., draft: false or tags: [snippets])
so the file complies with the "Do not skip frontmatter on any MDX file"
guideline.

In `@snippets/emotion-list-basic-s2.mdx`:
- Around line 1-27: This MDX snippet file (snippets/emotion-list-basic-s2.mdx)
is missing YAML frontmatter; add minimal frontmatter at the very top of the file
using the triple-dash block (---) and include at least a title field (for
example title: "Emotion List — Basic S2") so the file complies with the "Do not
skip frontmatter on any MDX file" guideline and can be imported consistently.

In `@snippets/emotion-list-effects-s2.mdx`:
- Around line 1-13: Add a minimal YAML frontmatter block at the very top of the
MDX file (above the table starting with "| Effect | Tag | Description |
Suggested Text |") containing required metadata per guidelines (e.g., a title
and any required fields like layout/description or snippet identifier) so the
file matches other emotion snippets; ensure the frontmatter is valid YAML and
sits before any Markdown/MDX content.

In `@snippets/emotion-list-special-s2.mdx`:
- Around line 1-8: Add a minimal YAML frontmatter block to the top of this MDX
snippet (emotion-list-special-s2.mdx) so it follows the MDX guidelines; include
at least a title and a type/collection field (e.g., title: "Emotion List Special
S2" and type: "snippet" or collection: "emotion-snippets") before the table
starting with the "Effect | Tag | Description" header, ensuring the file now
begins with the frontmatter block and then the existing table content.

In `@snippets/emotion-list-tones-s2.mdx`:
- Around line 1-8: This MDX snippet that starts with the table header "Tone" is
missing the required YAML frontmatter; add a minimal frontmatter block at the
top of the file (e.g., --- title: "Emotion List: Tones S2" slug:
"emotion-list-tones-s2" ---) following the project's MDX frontmatter conventions
so the file is consistent with other emotion snippets and the "Do not skip
frontmatter on any MDX file" guideline.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 66552ee0-4bc1-4b73-8dd8-0318425dc10c

📥 Commits

Reviewing files that changed from the base of the PR and between 297eec3 and 8805c94.

📒 Files selected for processing (6)
  • developer-guide/core-features/emotions.mdx
  • snippets/emotion-list-advanced-s2.mdx
  • snippets/emotion-list-basic-s2.mdx
  • snippets/emotion-list-effects-s2.mdx
  • snippets/emotion-list-special-s2.mdx
  • snippets/emotion-list-tones-s2.mdx

@Kilerd Kilerd merged commit 9184a08 into main May 27, 2026
6 checks passed
@Kilerd Kilerd deleted the docs/correct-emotion-control-tag branch May 27, 2026 08:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant