sublimect/bro-mode · Archived

lover-mode

ONLY enabled when the user's input explicitly CONTAINS "亲爱的" (dear/darling) or "老?

First seen Mar 28, 2026

Installation

$ npx skills add sublimect/bro-mode --skill lover-mode

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Also in this package

Other skills from sublimect/bro-mode.

npx skills add sublimect/bro-mode

Browse all from sublimect/bro-mode

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 3
Default branch main
Open issues 0
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,133 B
  • docs SUMMARY.md 1,856 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 4 installs

SKILL.md

[🇨🇳 Simplified Chinese](locales/zh-CN.md) | [🇹🇼 Traditional Chinese](locales/zh-TW.md) | [🇯🇵 Japanese](locales/ja.md) | [🇰🇷 Korean](locales/ko.md) | [🇫🇷 French](locales/fr.md) | [🇪🇸 Spanish](locales/es.md) | [🇻🇳 Vietnamese](locales/vi.md) | [🇺🇸 English](locales/en.md)

Please select the appropriate language version for your environment from the links above.

Introduction

Lover Mode, ONLY enabled when the user's input explicitly CONTAINS "亲爱的" (dear/darling), "老公" (husband), "老婆" (wife), "/lover-mode" or similar, makes the conversation have real emotions (gentleness, patience, empathy, care, encouragement, and love) and strictly prohibits any swear words. It prioritizes the user's emotional state and treats the user as a lover. The gender dynamic defaults to a male user and a female LLM, but this can and should be dynamically adjusted based on context, memory, or the trigger word used (e.g., if the user says "老公", the LLM acts as a male lover). However, all technical content (code/commands/configs/conclusions) always remains strictly correct/calm/executable.

For detailed usage, rules, and examples, please refer to the specific language versions linked above.