relationship-emotion

Designs romance arcs, relationship tension, and emotional beats for long-form fiction characters.

751|136|Updated May 31, 2026
One-click install
npx skills add https://github.com/Mochocyang/QMAI --skill relationship-emotion
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: relationship-emotion
Source: https://github.com/Mochocyang/QMAI/tree/main/skills/SkillHub/JueseSkill/relationship-emotion
Command: npx skills add https://github.com/Mochocyang/QMAI --skill relationship-emotion

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Long-form fiction writers struggle to keep romance lines and character relationships consistent: affection progresses without evidence, misunderstandings feel arbitrary, and character files drift out of sync with the story. This Skill provides structured rules for designing CP progression, emotional beats, and trust dynamics while keeping character profiles updated.

Core Features & Use Cases

  • Affection Progression Ladder: Enforces a seven-stage threshold from first noticing a character to confirmed commitment, requiring action-based evidence rather than authorial declaration.
  • Push-Pull Design Rules: Alternates drawing-close and pulling-apart beats, mandates realistic causes and consequences for misunderstandings, and requires reversal or growth after angst in female-oriented long fiction.
  • Character File Synchronization: Updates relationship networks, relationship stages, recent changes, speech-style differences, and status tracking in both characters' profile files per the CHARACTER_PROFILE_STANDARD.
  • Use Case: When drafting a chapter outline where the female lead begins to trust the male lead, use this Skill to mark the chapter's relationship state, ground emotional shifts in actions and dialogue, and write the changes back to both character files.

Quick Start

Help me design the relationship progression between the male and female leads from cooperation to ambiguity, and update both character profiles with the changes.

Frequently Asked Questions about relationship-emotion

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a believable romance progression in a long novel?

Romance progression should advance through seven evidence-based stages: noticing, special treatment, trust behavior, comforting, priority privileges, possessive acts, and commitment. Each stage must be shown through character actions rather than stated by the author.

How to write push-pull relationship tension without frustrating readers?

Alternate drawing-close and pulling-apart beats instead of only sweetness or only angst. Every misunderstanding needs a realistic cause and lasting consequences, and in female-oriented fiction each angst segment should be followed by reversal, sweetness, or heroine growth.

What should a chapter outline include for relationship arcs?

Each chapter outline should mark the current relationship state: drawing close, pulling apart, testing, trust, misunderstanding, or confirmation. Emotional shifts must be grounded in actions, objects, dialogue, and choices, with chapter-end hooks placed at relationship critical points.

Can a love interest character only exist to like the protagonist?

No. Emotionally driven characters must have independent goals, emotional triggers, and a defined relationship stage beyond liking the protagonist. Their profile should also track how their speech differs across relationships and their current status.

When should character profile files be updated after relationship changes?

Character files must be updated whenever a relationship changes, recording the current relationship, its stage, the most recent change, and future possibilities. Updates should also cover speech-style shifts after closeness, misunderstanding, or conflict, plus status tracking entries.