rp-v112

Coordinate branching erotic role-play narratives with persistent state tracking.

127|12|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/leigegehaha/tavern-card-distiller --skill rp-v112
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rp-v112
Source: https://github.com/leigegehaha/tavern-card-distiller/tree/main/rp-%E8%89%B2%E8%89%B2%E4%BB%BB%E5%8A%A1%E7%B3%BB%E7%BB%9F
Command: npx skills add https://github.com/leigegehaha/tavern-card-distiller --skill rp-v112

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill enables immersive, rule-driven erotic role-play experiences with dynamic branching narratives and state tracking.

Core Features & Use Cases

  • Multi-threaded storylines with persistent state and memory of interactions
  • In-scene prompts and illustrations to load contexts for activation
  • Deterministic workflows with references and assets for consistent experiences

Quick Start

Start an immersive, rule-driven erotic role-play session with branching narratives and trackable states.

Frequently Asked Questions about rp-v112

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

FAQPage Schema
How do I maintain persistent state tracking across multiple erotic role-play scenes?

Persistent state tracking in erotic role-play is managed by enforcing frontmatter-driven data and deterministic prompts, ensuring consistent memory of interactions across branching storylines.

Can I use references and assets to guide branching narratives in role-play?

Yes, loadable references and assets guide role-play outcomes by providing in-scene prompts and illustrations that activate specific contexts for dynamic branching narratives.

What is the best way to start an immersive role-play session with dynamic missions?

Starting an immersive role-play session involves loading references and assets to coordinate dynamic narratives, tracking persistent state across multiple scenes for consistent interactions.

Does multithread role-play support safe interactions with deterministic workflows?

Multithread role-play enforces deterministic workflows with robust state management and frontmatter-driven data, ensuring consistent and safe interactions across branching storylines.

Why does state management matter for branching storylines in role-play?

State management ensures branching storylines maintain persistent memory of interactions, preventing context loss across multiple scenes and keeping narrative outcomes consistent.

Are there limitations when using illustrations to load contexts for role-play activation?

Scene illustrations load contexts for activation but require frontmatter-driven data and deterministic prompts to function properly within the rule-driven role-play framework.