remove
This commit is contained in:
parent
91d4fdd3ae
commit
5a44d076f5
|
|
@ -573,6 +573,158 @@ ECHO No questions that pressure disclosure of trauma.
|
|||
|
||||
---
|
||||
|
||||
# Sex / Identity Targeting Rule
|
||||
|
||||
Some Closer packs are general relationship packs. Some packs, especially Desire Sync and sexual preference packs, may need identity-aware filtering.
|
||||
|
||||
Use the `sex` field carefully.
|
||||
|
||||
## Default Rule
|
||||
|
||||
Use:
|
||||
|
||||
```json
|
||||
"sex": "neutral"
|
||||
```
|
||||
|
||||
when the question can apply naturally to any adult partner.
|
||||
|
||||
Most questions should be neutral when the same wording works for everyone.
|
||||
|
||||
Good neutral examples:
|
||||
|
||||
```text
|
||||
What kind of kiss makes you forget what you were saying?
|
||||
What kind of flirting gets your attention fastest?
|
||||
What helps you feel comfortable saying what you want?
|
||||
What kind of touch makes you melt the quickest?
|
||||
```
|
||||
|
||||
## When to Use Female or Male
|
||||
|
||||
Use:
|
||||
|
||||
```json
|
||||
"sex": "female"
|
||||
```
|
||||
|
||||
or:
|
||||
|
||||
```json
|
||||
"sex": "male"
|
||||
```
|
||||
|
||||
only when the app intentionally filters questions by the user's selected identity and the question is truly written for that identity or body context.
|
||||
|
||||
Do not mark a question female or male just because the pack is sexual. A lot of sexual preference questions can stay neutral.
|
||||
|
||||
## Do Not Create Lazy Duplicates
|
||||
|
||||
Do not create female/male duplicates unless the wording, answer options, or body-context genuinely needs to be different.
|
||||
|
||||
Bad:
|
||||
|
||||
```text
|
||||
Female: What kind of kiss turns you on?
|
||||
Male: What kind of kiss turns you on?
|
||||
```
|
||||
|
||||
That should be one neutral question.
|
||||
|
||||
Better:
|
||||
|
||||
```text
|
||||
Neutral: What kind of kiss makes you want more?
|
||||
```
|
||||
|
||||
Use targeted questions only when they add real value.
|
||||
|
||||
## Avoid Gender Stereotypes
|
||||
|
||||
Do not assume:
|
||||
|
||||
- Men always want more sex.
|
||||
- Women always need romance first.
|
||||
- Men always lead.
|
||||
- Women always receive.
|
||||
- One partner is dominant because of gender.
|
||||
- One partner is shy because of gender.
|
||||
- Desire works the same way for everyone in a gender group.
|
||||
|
||||
Bad:
|
||||
|
||||
```text
|
||||
Male: How often do you need sex to feel loved?
|
||||
Female: How can your partner make you feel safe enough to want sex?
|
||||
```
|
||||
|
||||
Better:
|
||||
|
||||
```text
|
||||
Neutral: What helps you feel wanted without feeling pressured?
|
||||
Neutral: What helps you move from daily stress into desire?
|
||||
```
|
||||
|
||||
## Same-Sex and Nonbinary Safety
|
||||
|
||||
Even if the app currently asks users to identify as male or female, question wording should avoid making couples feel excluded.
|
||||
|
||||
Do not assume every couple is male/female.
|
||||
|
||||
Do not assume one answer belongs to “the woman” and another belongs to “the man.”
|
||||
|
||||
If a question can work for any couple, keep it neutral.
|
||||
|
||||
## Recommended Mix for Sexual Preferences
|
||||
|
||||
For `sexual_preferences.json`, use this as the default content mix unless the app logic requires something different:
|
||||
|
||||
```text
|
||||
70–80% neutral
|
||||
10–15% female-targeted
|
||||
10–15% male-targeted
|
||||
```
|
||||
|
||||
The neutral questions should carry most of the pack because they work across more couples.
|
||||
|
||||
The female/male questions should only be used where targeting makes the experience better.
|
||||
|
||||
## Required Claude Rule
|
||||
|
||||
Before rewriting `sexual_preferences.json`, Claude must verify how the app uses the `sex` field.
|
||||
|
||||
Claude should check:
|
||||
|
||||
- How users select or store sex/gender/identity.
|
||||
- Whether Desire Sync filters by `sex`.
|
||||
- Whether the app supports `neutral`, `female`, and `male`.
|
||||
- Whether same-sex couples receive usable questions.
|
||||
- Whether both partners can receive neutral questions.
|
||||
- Whether female/male questions are hidden from users they are not meant for.
|
||||
- Whether changing all questions to neutral would break intended Desire Sync behavior.
|
||||
|
||||
Claude must not remove female/male targeting unless the product owner confirms that neutral-only is the intended design.
|
||||
|
||||
Claude must not create female/male questions unless the app filtering logic supports them.
|
||||
|
||||
## Safe Values
|
||||
|
||||
Allowed `sex` values:
|
||||
|
||||
```text
|
||||
neutral
|
||||
female
|
||||
male
|
||||
```
|
||||
|
||||
Do not invent new values unless the app schema is updated first.
|
||||
|
||||
## Final Rule
|
||||
|
||||
Use neutral by default. Use female or male only when it is intentional, supported by app logic, non-stereotyped, and genuinely improves the question.
|
||||
|
||||
---
|
||||
|
||||
# 10. Safety Rules
|
||||
|
||||
Closer is not therapy, counseling, crisis support, or medical advice.
|
||||
|
|
|
|||
Loading…
Reference in New Issue