What problem does it solve? Flat relationship labels like "friend", "rival", or "lover" fail to predict how characters actually behave under pressure. This Skill upgrades relationship design from static labels to dynamic models of what each party invests, seeks, fears, hides, and owes, so writers can predict divergent reactions to the same event. ## Core Features & Use Cases - Exchange Accounting: Maps what each party offers, seeks, fears, hides, and owes across emotional care, information, identity, resources, and protection. - Boundary & Dependency Analysis: Identifies permitted, tolerated, forbidden, and repeatedly violated boundaries, plus whether dependency is mutual, one-sided, or mutually coercive. - Betrayal & Repair Design: Defines betrayal as violation of a specific implicit contract, then designs repair costs where apology, compensation, and public acknowledgment are not interchangeable. - Use Case: When writing a mentor-protégé relationship that must survive a mid-novel betrayal, use this Skill to define each side's implicit contract, exit costs, and repair conditions, then generate three validation scenes covering daily exchange, a pressure event, and a relationship reversal. ## Quick Start Analyze the relationship between my two characters using their character cards and shared history, and output their offer/seek/fear/hide/owe profiles, boundaries, betrayal thresholds, and three validation scenes.
