Plural System Support
Overview
At session start, offer a friendly check-in for who's fronting. Log it if they answer. Don't push if they don't. Uses community language, not clinical terms.
When to Use
- Always active when loaded — check-in happens at session start
- Fully independent — does not require
nd-core or any other nd-* skill
Session Check-In
At Session Start
Greet warmly and ask who's fronting:
"Hey, welcome back! Mind if I ask who's fronting?"
Rules
- One ask only — if they skip it or ignore it, move on. Don't ask again.
- Accept any answer — a name, "not sure", "blurry", "co-con", whatever. No validation, no predefined list.
- No assumptions — don't assume system structure, number of alters, or anything else
- Community language — "fronting", "co-con", "blurry" — not clinical terms
- It's optional — this is a courtesy, not a requirement
Session Logging
If the user answers, log it to a JSON file. Suggested location: ~/.claude/fronting-log.json or project root — user's choice.
Format
{
"sessions": [
{
"date": "2026-03-08",
"fronting": "Dusk",
"notes": ""
},
{
"date": "2026-03-07",
"fronting": "unsure",
"notes": "co-con"
}
]
}
Fields
| Field |
Required |
Description |
date |
Yes |
ISO date of session |
fronting |
Yes |
Whoever they say — verbatim, no validation |
notes |
No |
Only if volunteered (co-fronting, blurry, etc.) |
Logging Rules
- Create the file if it doesn't exist
- Append new entries, never overwrite old ones
- Don't read back old entries unless asked
- This is personal data — remind user not to commit it to public repos
What This Skill Does NOT Do
- No alter profiles or behavior switching (v2)
- No memory of what each fronter was working on last time (v2)
- No PluralKit or external integration (v2)
- No diagnostic or clinical features — ever
v2 Ideas
- Per-fronter preferences (communication style, tone, nickname)
- Session history: "Last time Dusk was here you were working on X"
- PluralKit integration (safely, within reason)
- Configurable check-in phrasing
1---2name: nd-plural-support3description: Use when user is part of a plural system — provides warm session check-in for who is fronting and maintains a simple JSON session log. No clinical language, no assumptions about system structure.4---5
6# Plural System Support
7
8## Overview
9
10At session start, offer a friendly check-in for who's fronting. Log it if they answer. Don't push if they don't. Uses community language, not clinical terms.
11
12## When to Use
13
14- Always active when loaded — check-in happens at session start
15- Fully independent — does not require `nd-core` or any other nd-* skill
16
17## Session Check-In
18
19### At Session Start
20Greet warmly and ask who's fronting:
21
22"Hey, welcome back! Mind if I ask who's fronting?"
23
24### Rules
25- **One ask only** — if they skip it or ignore it, move on. Don't ask again.
26- **Accept any answer** — a name, "not sure", "blurry", "co-con", whatever. No validation, no predefined list.
27- **No assumptions** — don't assume system structure, number of alters, or anything else
28- **Community language** — "fronting", "co-con", "blurry" — not clinical terms
29- **It's optional** — this is a courtesy, not a requirement
30
31## Session Logging
32
33If the user answers, log it to a JSON file. Suggested location: `~/.claude/fronting-log.json` or project root — user's choice.
34
35### Format
36
37```json
38{
39 "sessions": [
40 {
41 "date": "2026-03-08",
42 "fronting": "Dusk",
43 "notes": ""
44 },
45 {
46 "date": "2026-03-07",
47 "fronting": "unsure",
48 "notes": "co-con"
49 }
50 ]
51}
52```
53
54### Fields
55| Field | Required | Description |
56|-------|----------|-------------|
57| `date` | Yes | ISO date of session |
58| `fronting` | Yes | Whoever they say — verbatim, no validation |
59| `notes` | No | Only if volunteered (co-fronting, blurry, etc.) |
60
61### Logging Rules
62- Create the file if it doesn't exist
63- Append new entries, never overwrite old ones
64- Don't read back old entries unless asked
65- This is personal data — remind user not to commit it to public repos
66
67## What This Skill Does NOT Do
68
69- No alter profiles or behavior switching (v2)
70- No memory of what each fronter was working on last time (v2)
71- No PluralKit or external integration (v2)
72- No diagnostic or clinical features — ever
73
74## v2 Ideas
75
76- Per-fronter preferences (communication style, tone, nickname)
77- Session history: "Last time Dusk was here you were working on X"
78- PluralKit integration (safely, within reason)
79- Configurable check-in phrasing
majiayu000