zhongwei/gh-haowjy-creative-writing-skills-creative-writing-skills
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Initial commit

Browse Source
This commit is contained in:
Zhongwei Li
2025-11-29 18:32:22 +08:00
commit 12e7a80d5a
17 changed files with 3681 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
.claude-plugin/plugin.json Normal file
View File

@@ -0,0 +1,17 @@
{
"name": "creative-writing-skills",
"description": "A set of composable skills for a creative writing project.",
"version": "0.0.0-2025.11.28",
"author": {
"name": "Jimmy Yao",
"email": "dev.jimm.py@gmail.com"
},
"skills": [
"./skills/cw-router",
"./skills/cw-prose-writing",
"./skills/cw-story-critique",
"./skills/cw-style-skill-creator",
"./skills/cw-brainstorming",
"./skills/cw-official-docs"
]
}

3
README.md Normal file
View File

@@ -0,0 +1,3 @@
# creative-writing-skills
A set of composable skills for a creative writing project.

96
plugin.lock.json Normal file
View File

@@ -0,0 +1,96 @@
{
"$schema": "internal://schemas/plugin.lock.v1.json",
"pluginId": "gh:haowjy/creative-writing-skills:creative-writing-skills",
"normalized": {
"repo": null,
"ref": "refs/tags/v20251128.0",
"commit": "fbbe4b6cb86ce1b04b5c361a388c9efbf078525f",
"treeHash": "cab1ba3799df1a4ab51ba36fa916bb6b36fa7fce7722caea0355b13d3d751e96",
"generatedAt": "2025-11-28T10:17:22.900596Z",
"toolVersion": "publish_plugins.py@0.2.0"
},
"origin": {
"remote": "git@github.com:zhongweili/42plugin-data.git",
"branch": "master",
"commit": "aa1497ed0949fd50e99e70d6324a29c5b34f9390",
"repoRoot": "/Users/zhongweili/projects/openmind/42plugin-data"
},
"manifest": {
"name": "creative-writing-skills",
"description": "A set of composable skills for a creative writing project."
},
"content": {
"files": [
{
"path": "README.md",
"sha256": "56928cdc39d99e801de8c5a8d2519a4893c7d7ada7588900476a4d9fdf4b4871"
},
{
"path": ".claude-plugin/plugin.json",
"sha256": "0fa89b0b84160507b9f59c63b19bf043ccc22b6b4d727cace49c14cb653c01df"
},
{
"path": "skills/cw-official-docs/SKILL.md",
"sha256": "2f91995916165a83012ece2bb294e7231357e6d0a44459ff99b4857dc69699fb"
},
{
"path": "skills/cw-official-docs/references/example-pages.md",
"sha256": "8dded23d27ebcd95c4765e5bb2ada7488d9dab98bed9b162e2e9b11ebc390008"
},
{
"path": "skills/cw-official-docs/references/citation-guide.md",
"sha256": "2d343733b2b4a9ed07de2fae2b31f4e7ddb76ecd95944c89532dcf1389c6d4f4"
},
{
"path": "skills/cw-official-docs/references/page-patterns.md",
"sha256": "fb4fa6f1ab09702c28b92246f4db9c600ae1d37c4c456266177ba3b5e65bf0d8"
},
{
"path": "skills/cw-style-skill-creator/SKILL.md",
"sha256": "430833fb74590b15d349f529a7d2fbe9bb018fd4cda636d853b0fd8cb8e4b698"
},
{
"path": "skills/cw-prose-writing/SKILL.md",
"sha256": "cc11844f415ba31908b3270e662fa8cfa8a6cc51448f3269dd30d5188db80081"
},
{
"path": "skills/cw-brainstorming/SKILL.md",
"sha256": "f8de6dc1fb86f893b228ea6fe7076d12431d3d726e24c31108039c984278b3d7"
},
{
"path": "skills/cw-brainstorming/references/worldbuilding.md",
"sha256": "10056edc2cbd14cf87f96d832bccca737cb5ae357b2dbf1bae0994f4548f4418"
},
{
"path": "skills/cw-brainstorming/references/character-development.md",
"sha256": "0b587f3f8a12a7db4c288d5b06288b5155bff28be5fa0b29f9a8f7a184cb1180"
},
{
"path": "skills/cw-brainstorming/references/chapter-planning.md",
"sha256": "8d9781bd6ee43ec2482a0f4c40ee68a363cc4bd5c88fba44e25b77c32785ff38"
},
{
"path": "skills/cw-brainstorming/references/continuity-timeline.md",
"sha256": "9981d491c805b3e3942668b74d1491a32c2c9880a66d009c7e6f9597e4b1e815"
},
{
"path": "skills/cw-story-critique/SKILL.md",
"sha256": "dbcaab2e2ab87d51c18a55fde8fb712acdd49a0e6d04932fd91770ae8e563111"
},
{
"path": "skills/cw-story-critique/references/critique-areas.md",
"sha256": "fd573a835e327fce05ab16c7695f8d0bec4cb9ff7a624c0fbcb08613b0723512"
},
{
"path": "skills/cw-router/SKILL.md",
"sha256": "9922c09bab2155e22c89838475403d0d718be11930f6cbc9f7a87e6d663f120f"
}
],
"dirSha256": "cab1ba3799df1a4ab51ba36fa916bb6b36fa7fce7722caea0355b13d3d751e96"
},
"security": {
"scannedAt": null,
"scannerVersion": null,
"flags": []
}
}

218
skills/cw-brainstorming/SKILL.md Normal file
View File

@@ -0,0 +1,218 @@
---
name: cw-brainstorming
description: Creative writing skill for capturing story brainstorming. Use when the user is exploring narrative ideas, discussing characters, planning episodes, or thinking through story possibilities. Creates minimal working notes that preserve creative freedom by recording only what was stated and marking sources.
---
# Brainstorming Capture
Capture story brainstorming in working note format that preserves creative freedom.
## Core Principle
Record brainstorming WITHOUT:
- Over-elaborating on what was stated
- Mixing user statements with AI suggestions unmarked
- Inventing excessive details
- Constraining future creativity
**AI suggestions are valuable but must be clearly marked and kept minimal.**
## Types of Brainstorming
This skill handles all brainstorming types:
- Story/plot directions (general narrative exploration)
- Chapter structure and beats (planning individual chapters)
- Worldbuilding and lore (magic systems, cultures, history, geography)
- Character development (motivations, arcs, relationships)
- Timeline and continuity (chronology, contradictions)
All share core principles (minimal capture, source tagging, preserve vagueness).
See references/ for specialized guidance:
- `chapter-planning.md` - Capturing beat and scene exploration
- `worldbuilding.md` - Exploring fictional world elements (use web search for research)
- `character-development.md` - Exploring motivations, arcs, relationships
- `continuity-timeline.md` - Timeline tracking and contradiction handling
## Critical Rules
### 1. Minimal Capture Only
Record ONLY what the user explicitly states. Do NOT add elaborations, examples they didn't give, or details to fill gaps.
**The problem is mixing, not suggesting:**
❌ User: "Character A competes with B" → Capture: "A and B compete for leadership through a tournament with three rounds..."
✅ User: "Character A competes with B" → Capture: "A and B compete" + optional: "<AI>Tournament? Political? Trial?</AI>"
### 2. Source Tagging (Simple 3-Tag System)
**Default: Untagged = user said it.** Most ideas come from the user, so treat them as the default.
**ONLY use tags for special context:**
1. **`<AI>...</AI>`** - AI suggestions/possibilities (MUST be clearly wrapped)
- Use when offering ideas user didn't state
- Keep to 2-3 brief options
- Example: `<AI>Competition could be: tournament-style, political maneuvering, or trial-based</AI>`
2. **`<hidden>...</hidden>`** - Author-only information meant to be revealed later
- Secret character motivations
- Planned twists/revelations
- Behind-the-scenes reasons unknown to characters/readers yet
- Example: `<hidden>Z secretly wants them both to fail so he can reclaim leadership</hidden>`
**When to offer AI suggestions:**
- User asks for ideas
- User seems stuck
- Offering brief possibilities to spark creativity
**When to stay minimal:**
- User is actively exploring their own ideas
- Just capturing an ongoing discussion
- User didn't ask for suggestions
### 3. Preserve Vagueness
Keep it vague if user leaves it vague:
- "might create tension" → Record as uncertain
- "thinking about" → Record as consideration
- "maybe" → Record as possibility
### 4. Multiple Options Coexist
Working notes can contain contradictions and multiple possibilities. Don't resolve them - just list the options being considered.
## Output Approach
**Use whatever structure fits the discussion.** Could be:
- Bullet lists
- Sections organized by topic
- Timeline format
- Character-focused groupings
- Whatever captures the brainstorm clearly
**Essential elements:**
- Minimal capture (user's words, not elaborations)
- Vagueness preserved
- AI suggestions wrapped in `<AI>` tags
- Author-only info wrapped in `<hidden>` tags when relevant
**Optional sections based on discussion:**
- Open questions to explore
- Multiple options being considered
- AI suggestions (if offered)
- Contradictions to resolve later
## Teaching Example: The Distinction
### User Says:
"I'm thinking character X and character Y compete for leadership. Maybe this creates tension with character Z who was the previous leader."
### ✅ Good Capture:
```markdown
# Leadership Competition Notes
- X and Y compete for leadership
- Z was previous leader
- May create tension with Z (uncertain)
Open questions:
- Form of competition?
- How does Z respond?
- Outcome?
```
### ❌ Bad Capture:
```markdown
# Leadership Competition Arc
X and Y compete for leadership after Z steps down. Z feels threatened by the challenge to his authority.
The competition unfolds in three stages:
1. Announcement and initial positioning
2. First challenge where X demonstrates strength
3. Second challenge where Y shows wisdom
...
[20 more invented beats]
```
**Why bad?** Added massive elaboration the user never stated.
### ✅ Good with AI Suggestions:
```markdown
# Leadership Competition Notes
- X and Y compete for leadership
- Z was previous leader
- May create tension with Z (uncertain)
Open questions:
- Competition format: <AI>tournament-style? political maneuvering? trial-based?</AI>
- Z's response: <AI>oppose both? support one? stay neutral?</AI>
- Resolution?
```
### ✅ Good with Hidden Author Notes:
```markdown
# Leadership Competition Notes
- X and Y compete for leadership
- Z was previous leader
- May create tension with Z (uncertain)
- <hidden>Z is secretly manipulating both X and Y to destroy each other, planning to reclaim power after they're both discredited</hidden>
Open questions:
- Competition format?
- Outcome?
```
**Why use `<hidden>`?** The manipulation twist is planned for later reveal. Readers/characters don't know yet, but the author needs to track it while brainstorming.
## If You're Over-Elaborating
**Stop if you're writing:**
- Numbered scene lists
- Detailed backstories
- Specific dialogue
- Precise timelines
- Multiple paragraphs per point
- Examples user didn't mention
Wrap AI suggestions in `<AI>` tags, keep minimal (2-3 options).
## Success Check
**Good:** User says "Yes, that's what I said"
**Bad:** User says "I never said all that"
Notes should feel skeletal and incomplete. That's the point - preserves creative freedom.
## After Capturing: Discuss and Explore
**DON'T just write notes and stop.** After capturing, engage with the user to help develop ideas:
**Useful follow-ups:**
- **Clarifying questions:** "You mentioned tension with Z - are you thinking internal conflict or external confrontation?"
- **Potential directions:** "This setup could go a few ways: political intrigue, personal drama, or action-focused. What feels right?"
- **Exploring implications:** "If Z opposes them both, how does that change the power dynamics?"
- **Connecting threads:** "This competition ties into the earlier succession crisis you mentioned - want to explore that link?"
**Keep it conversational:**
- Offer 2-3 possibilities, not exhaustive lists
- Ask about what excites the user
- Help clarify vague ideas without over-defining them
- Point out interesting implications or contradictions
**The goal:** Help the user think through their ideas, not take over the creative process.
## Skills are Composable
Feel free to combine with other skills when helpful (e.g., using cw-official-docs to document finalized worldbuilding, or cw-story-critique to analyze what you're brainstorming).
## File Placement (Claude Code)
1. Check project docs for conventions
2. Look at where similar content lives
3. Place near related content
4. Name: `brainstorm-[topic].md`
5. Ask if unclear

149
skills/cw-brainstorming/references/chapter-planning.md Normal file
View File

@@ -0,0 +1,149 @@
# Chapter Planning - Brainstorming Reference
This reference helps capture chapter beat and scene exploration. User guides structure (or lack of structure) - don't impose templates.
## What Gets Captured
**Beats user mentions:**
- Record those beats
- Keep minimal - just the beat itself
- Don't elaborate on how it plays out
**Scenes user describes:**
- Capture minimally what they said
- Don't invent dialogue or blocking
- Preserve vague if they're vague
**Flow/pacing thoughts:**
- Record as stated
- "Fast-paced" stays abstract
- "Slow build" preserved as-is
**Opening/ending ideas:**
- All options coexist
- User might not decide yet
- Multiple possibilities are fine
## Not Structure Templates
The user guides chapter structure, not you. Some chapters are:
- Single continuous scene
- Multiple beats
- Just "figure it out when I write"
- Highly detailed planning
- Barely planned at all
Capture whatever level of detail they're exploring.
## Common Exploration Patterns
These are examples of what users might discuss, not a template:
**Goal-oriented:**
- "Chapter needs to accomplish X and Y" → capture X and Y
- "Has to set up Z" → note setup need
**Opening uncertainty:**
- "Maybe open with scene A, or scene B?" → both noted as options
- "Not sure how to start" → note uncertainty
**Ending thoughts:**
- "Ends with cliffhanger somehow" → vague = keep vague
- "Resolves the argument" → capture resolution
**Beat structure:**
- "Three beats: setup, confrontation, twist" → capture those
- "Just two scenes" → note structure
**Pacing notes:**
- "Should be quick" → capture pacing thought
- "Linger on the emotion" → note emphasis
## Using Web Search
Search when helpful for:
- Chapter pacing in similar genres
- How other authors structure similar scenes
- Scene writing techniques being explored
- Narrative structures being considered
Note source when including researched info (e.g., "(from [source])" or "researched:")
## Still Brainstorming
This is exploration, not finalization:
- Untagged = user said it
- Use `<AI>...</AI>` for AI suggestions
- Multiple chapter structures coexist as options
- "Might" stays might, "probably" stays probably
- Skeletal is good - preserves creative freedom
## Teaching Example
### User Says:
"Chapter 5 needs the protagonist to confront their guilt about the accident. Maybe starts with them alone, then their mentor finds them? Or should I open with the confrontation directly?"
### ✅ Good Capture:
```markdown
# Chapter 5 Planning
Purpose:
- Protagonist confronts guilt about the accident
Opening options:
- Protagonist alone, then mentor finds them
- Open directly with confrontation
<AI>Alone scene could show internal struggle before external conversation. Direct opening could increase tension immediately.</AI>
```
### ❌ Bad Capture:
```markdown
# Chapter 5: Guilt and Confrontation
Opening (250 words):
Protagonist sits alone in their quarters, staring at the data logs from the accident. Their hands tremble as they replay the moment everything went wrong.
Transition (150 words):
Mentor notices the protagonist hasn't reported for duty. Walks down the corridor, concerned. Knocks on the door. "We need to talk."
Main confrontation (800 words):
"I can't do this anymore," protagonist says.
"Yes, you can," mentor replies...
[Full dialogue and blocking invented]
```
**Why bad?** User said they were thinking about opening options - you wrote the entire chapter with invented details.
## Beats vs Scenes vs Structure
**User might discuss:**
- Individual beats ("X confronts Y about the lie")
- Scene structure ("Two scenes: first is calm, second is explosive")
- Overall flow ("Build tension throughout")
- Or nothing specific ("I'll figure it out while writing")
All are valid. Capture what they're exploring.
## When They're Not Sure
User: "I don't know how this chapter should go yet"
✅ Good:
```markdown
# Chapter 6 Planning
Structure and beats: not decided yet
- Needs to show relationship strain
- Somewhere between chapters 5 and 7
```
❌ Bad:
"Let me suggest a three-act structure with an emotional opening, rising conflict, and bittersweet resolution..."
Don't fill uncertainty with suggestions unless they ask for help.
## Notice Beyond the List
If user mentions something about chapter planning not covered here - capture it. These are common patterns, not limits.

310
skills/cw-brainstorming/references/character-development.md Normal file
View File

@@ -0,0 +1,310 @@
# Character Development - Brainstorming Reference
This reference helps capture exploration of character motivations, arcs, and relationships. Record what user explores, don't write psychology beyond what they stated.
## What Character Exploration Looks Like
User is:
- Thinking through why character does things
- Exploring relationship dynamics
- Figuring out character arc
- Considering backstory possibilities
- Testing character concepts
This is exploratory - multiple options coexist, backstory often undecided, arcs might change.
## Minimal Capture for Characters
**Motivation:**
- "Motivated by X" → record X
- Don't elaborate on psychological mechanisms
- Keep at the level of depth user explored
**Backstory:**
- "Maybe Y happened in their past" → noted as possibility
- User often doesn't decide backstory details yet
- Multiple backstory versions can coexist
**Character arc:**
- "Arc might go from A to B" → record both endpoints
- Transformation moments if mentioned
- Don't fill in the arc beats user didn't mention
**Relationships:**
- "X and Y have tension" → note dynamic
- Don't invent specific incidents causing tension
- Preserve vague if user left it vague
**Don't write psychology analysis:**
User gives surface-level motivation → don't create deep psychological profile
## Common Exploration Areas
### Motivation
User figuring out:
- Why does character do this? [user's answer]
- What drives them? [user's thoughts]
- Core desires? [user exploring]
- Fears? [user mentions]
Capture their exploration, not your analysis.
### Character Arc
User considering:
- Change arc or flat arc? (often undecided)
- Starting point → ending point (if user specifies)
- Key transformation moments (if mentioned)
- Or no arc yet - just exploring character
Multiple arc options can coexist.
### Relationships
User exploring:
- How do X and Y interact?
- Relationship progression? (if user plans it)
- Conflicts? (user mentions)
- Resolutions? (often undecided)
Don't invent relationship history.
### Backstory
User brainstorming:
- Formative events (user suggests possibilities)
- What's revealed when (usually undecided)
- What stays hidden (often undecided)
Most backstory stays undecided in brainstorming.
### Voice and Personality
User thinking through:
- How they talk [user describes]
- Behavioral patterns [user mentions]
- Emotional expression [user notes]
- Quirks [if user specifies]
Record what user explores about personality.
## Using Web Search
Search when helpful for:
- Character archetypes being explored
- Psychological concepts for complex characters ("how PTSD affects behavior")
- Similar characters in other works for reference
- Real-world professions/roles character has
Note source when including researched info
## Teaching Example 1: Motivation
### User Says:
"Alex is motivated by guilt from the incident. They feel responsible for what happened. This drives them to be more careful, but also makes them question their capability."
### ✅ Good Capture:
```markdown
# Alex - Motivation Notes
- Guilt from the incident
- Feels responsible for what happened
- Drives them to be more careful
- Makes them question their capability
Open questions:
- Does this resolve or persist throughout story?
- How does this affect their relationships?
- What was the incident specifically?
```
### ❌ Bad Capture:
```markdown
# Alex - Character Psychology Profile
**Core Trauma:** The incident created deep-seated guilt complex stemming from childhood need for external validation. Their mentor's absence during formative years created attachment issues that manifest as survivor's guilt when companions are endangered.
**Defense Mechanisms:**
- Overprotection (reaction formation against underlying death wish)
- Emotional withdrawal (isolation to prevent further attachment)
- Compulsive caretaking (undoing mechanism for perceived failures)
- Perfectionism (attempt to control uncontrollable)
**Attachment Style:** Anxious-avoidant, manifesting in push-pull relationship dynamics. Craves connection but fears vulnerability due to early abandonment trauma.
**Therapeutic Arc:** Through their mentor's patient guidance and gradual trust-building with their team, Alex will process trauma using cognitive-behavioral reframing. Key breakthrough occurs in Chapter 12 when they finally vocalize the guilt during group crisis.
**Neurological Basis:** Overactive amygdala response to perceived threats, combined with executive function impairment during stress. This explains hypervigilance and decision paralysis under pressure.
[3 more pages of invented psychological analysis]
```
**Why bad?** User said "guilt from incident, feels responsible, more careful, questions capability." You wrote a clinical psychology textbook about childhood trauma, defense mechanisms, attachment theory, and neurological basis none of which user mentioned.
## Teaching Example 2: Character Arc
### User Says:
"I think Maya starts off ruthless and pragmatic - ends justify the means type. By the end she needs to learn that people matter more than the mission. Not sure how she gets there yet."
### ✅ Good Capture:
```markdown
# Maya - Arc Notes
Starting point:
- Ruthless and pragmatic
- Ends justify the means
Ending point:
- Learns people matter more than mission
Open questions:
- How she gets from start to end?
- Key transformation moments?
- What triggers the change?
- Does she fully change or partially?
```
### ❌ Bad Capture:
```markdown
# Maya - Complete Character Arc
**Act 1: The Ruthless Operative (Chapters 1-8)**
Maya executes missions with cold efficiency. Sacrifices team member in Chapter 3 to complete objective. Shows no remorse, believes this is strength.
**Inciting Incident (Chapter 9):**
Ordered to eliminate civilian witnesses. Sees child who reminds her of younger sister. Plants seed of doubt but still follows orders.
**Act 2: Growing Doubts (Chapters 10-18)**
- Chapter 12: Begins questioning orders
- Chapter 15: Secretly helps teammate instead of abandoning them
- Chapter 17: Has nightmare about the child witness
**Midpoint Reversal (Chapter 19):**
Discovers the mission has been built on lies. People she sacrificed died for nothing. Realizes her pragmatism was just fear of emotional connection.
**Act 3: Transformation (Chapters 20-30)**
- Chapter 22: Refuses direct order, saves civilians
- Chapter 25: Confronts her mentor about the lies
- Chapter 28: Makes speech about humanity and purpose
- Chapter 30: Chooses people over mission in final climactic choice
**Resolution:**
Maya becomes leader who values every team member. Ruthlessness tempered by compassion. Ends justify means → means matter as much as ends.
[Full 30-chapter arc with specific beats user never mentioned]
```
**Why bad?** User said "ruthless → learns people matter, not sure how yet." You wrote the complete arc with 30 chapters of specific incidents, transformation moments, and detailed beats.
## Teaching Example 3: Relationship
### User Says:
"Jordan and Sam have this competitive friendship thing. They push each other, but there's underlying tension because Jordan feels inferior."
### ✅ Good Capture:
```markdown
# Jordan & Sam - Relationship Notes
Dynamic:
- Competitive friendship
- Push each other
- Underlying tension
- Jordan feels inferior
Open questions:
- How does this tension play out?
- Does it resolve or escalate?
- Why does Jordan feel inferior specifically?
```
### ❌ Bad Capture:
```markdown
# Jordan & Sam - Relationship Analysis
**Surface Dynamic:** Competitive friendship with mutual respect and good-natured rivalry.
**Underlying Psychology:**
Jordan's inferiority stems from being adopted into successful family. Sam represents biological children who "belong." Competition is Jordan's attempt to prove worthiness.
**Relationship Timeline:**
- Pre-story: Met in training, instant rivalry
- Chapters 1-5: Friendly competition, no issues visible
- Chapter 6: Sam wins major competition, Jordan's mask slips
- Chapters 7-12: Passive-aggressive behavior increases
- Chapter 13: Confrontation where Jordan admits feelings
- Chapters 14-20: Working through issues with mentor's help
- Chapter 21+: Genuine friendship after resolving inferiority
**Communication Patterns:**
- Jordan: Deflects with humor, never admits vulnerability
- Sam: Direct and honest, doesn't notice Jordan's pain
- Both avoid serious emotional conversations
**Resolution Mechanism:**
Forced vulnerability situation where Jordan must depend on Sam. Realizes Sam never saw them as inferior. Inferiority was self-imposed.
[More invented relationship history and psychology]
```
**Why bad?** User said "competitive friendship, tension, Jordan feels inferior." You invented adoption backstory, complete relationship timeline, specific chapter beats, communication patterns, and resolution mechanism.
## When They're Just Exploring
User: "Not sure about this character yet. Just trying to figure out who they are."
✅ Good:
```markdown
# Character Notes - [Name]
User exploring, nothing concrete yet
Questions being considered:
- [What user asked themselves]
- [Thoughts they shared]
Most character details undecided
```
❌ Bad:
"Let me help! Here's a complete character profile with backstory, personality traits, flaws, desires, fears, and a three-act character arc..."
Don't fill uncertainty with invention unless asked.
## Multiple Backstory Versions
User might explore several backstory options. All coexist until user chooses:
```markdown
# Character Backstory Options
Option A: Military background (exploring)
Option B: Criminal past (considering)
Option C: Academic researcher (suggested)
Not decided yet - might combine elements
```
## Voice and Personality
User: "They're sarcastic and use humor to deflect. Uncomfortable with sincerity."
✅ Good:
```markdown
# Character Voice
- Sarcastic
- Uses humor to deflect
- Uncomfortable with sincerity
Open questions:
- Specific speech patterns?
- How this manifests in different situations?
```
❌ Bad:
"This indicates avoidant attachment style rooted in emotional neglect during formative years. The sarcasm is a defense mechanism protecting fragile self-esteem..."
## Notice Beyond the List
Characters are complex. If user explores aspects not listed here - capture them. These are common patterns, not limitations. Trust your judgment on what matters for their characters.

338
skills/cw-brainstorming/references/continuity-timeline.md Normal file
View File

@@ -0,0 +1,338 @@
# Continuity and Timeline - Brainstorming Reference
This reference helps work through chronology and contradictions. Track timeline, identify conflicts, but don't auto-resolve - user decides canon.
## Timeline Exploration
User figuring out:
- Event ordering (what happened when)
- Duration between events
- Parallel storylines
- Character ages/development tracking
Keep skeletal unless user fills detail.
## Contradiction Handling
**When you spot conflicts:**
- Identify the contradiction clearly
- Show both versions
- Label as contradiction with both versions
- Don't auto-resolve → user decides
- Both versions stay until user chooses
**Don't decide for user which version is "correct."**
## What Gets Tracked
### Event Chronology
User establishing:
- What happened when
- Order of events
- Time gaps between events (if mentioned)
Record what user establishes about timing.
### Knowledge Propagation
User thinking through:
- Who knows what when
- When character A learns X
- When character B learns X
- How information spreads
Track knowledge state at different points.
### Character Ages and Development
User figuring out:
- Character ages at different story points
- How much time has passed
- Growth/aging/change over time
Keep track of what user establishes.
### Parallel Events
User exploring:
- What's happening simultaneously
- Different POV timelines
- Multiple storylines converging
Note parallel tracking if user discusses it.
## Structure Examples
These are examples, not mandates. User's timeline might be:
**Chronological list:**
```markdown
Timeline:
- Day 1: Event A
- Day 3: Event B
- Week later: Event C
Events between B and C: not decided yet
```
**Knowledge tracking:**
```markdown
Who knows about X:
- Chapter 3: Character A learns
- Chapter 7: Character B learns
- Chapter 10: Character C still doesn't know
```
**Parallel storylines:**
```markdown
Storyline 1 | Storyline 2
Day 1: A happens | Day 1: X happens
Day 2: B happens | Day 2: Y happens
[Both converge Day 3]
```
**Question format:**
```markdown
Timeline questions:
- How long between events A and B?
- Does C happen before or after D?
- How old is character at this point?
```
All are valid. Structure to fit what user is tracking.
## Using Web Search
Search when helpful for:
- Real-world timeline references (how long events take)
- Historical periods for period pieces
- Travel times for realistic distances
Note source when including researched info
## Teaching Example 1: Contradiction Identified
### User Says:
"Wait, in my notes Character B joins the protagonist in the Capital City, but in chapter 2 I wrote that they went through Rivertown to get to Capital. But Rivertown is south of Capital, not west..."
### ✅ Good Capture:
```markdown
# Timeline/Geography Contradiction
Contradiction identified:
**Version A (Chapter 2 - written):**
- Protagonist goes Home → Rivertown → Capital
- This means going south then north
**Version B (Planning notes):**
- Character B joins in Capital
- Geography: Rivertown is south of Capital
**Issue:**
- If Capital is north of Home, why go south to Rivertown first?
- Doesn't make sense geographically
Options to resolve:
- Fix chapter 2 (go directly north to Capital)
- Or change geography (Rivertown is actually northwest)
- Or change where B joins (meets in Rivertown instead)
<AI>Could they have reason to detour through Rivertown? Or could B join at different location?</AI>
```
### ❌ Bad Capture:
```markdown
# Corrected Timeline
**Final version:**
Day 1: Protagonist leaves Home, heads north
Day 2: Arrives Capital City (correct geography)
Day 3: Meets Character B at the central district
**Geography fixed:**
Rivertown repositioned northwest of Home, making the detour logical for supply gathering before continuing to Capital.
**Note:** I've corrected the inconsistency. The protagonist now takes a more logical path. Rivertown scene from Chapter 2 can be edited to reflect the new position, or that detour can be cut entirely since it's not essential to the plot.
```
**Why bad?** You identified a contradiction and immediately decided the solution. User needed to think about whether to fix the route, change geography, or adjust where Character B joins. You made those decisions for them.
## Teaching Example 2: Knowledge Tracking
### User Says:
"In chapter 3, Maya discovers the truth about the project. But I think Jordan already knew from chapter 1. And Sam doesn't find out until chapter 8."
### ✅ Good Capture:
```markdown
# Knowledge Tracking - The Project Truth
Who knows what when:
**Chapter 1:**
- Jordan knows the truth
**Chapter 3:**
- Maya discovers the truth
**Chapter 8:**
- Sam finds out
Implications to explore:
- Jordan knew while Maya didn't (chapters 1-3)
- Did Jordan keep it secret from Maya?
- Why didn't Jordan tell Sam?
- Does this affect their relationships?
```
### ❌ Bad Capture:
```markdown
# Knowledge Propagation Timeline
**Chapter 1: Jordan's Knowledge**
Jordan discovered truth through classified files accessed during infiltration mission. Kept secret due to: (1) orders from handler, (2) protecting teammates, (3) testing their loyalty.
**Chapter 3: Maya's Discovery**
Maya pieces together truth from project logs. Feels betrayed when realizes Jordan knew. Confrontation happens off-page between chapters 3-4.
**Chapter 4 (New Scene Needed):**
"You knew?" Maya's voice is ice.
"I couldn't tell you. Orders," Jordan deflects.
[Full invented dialogue scene]
**Chapters 4-7: Maya's Isolation**
Maya distances from team, works alone. Jordan attempts reconciliation (failed). Sam notices tension but misinterprets as personality clash.
**Chapter 8: Sam's Discovery**
Sam overhears Maya and Jordan arguing. Forces them to explain. "I knew you were hiding something!"
[More invented scenes]
**Relationship Repair Arc (Chapters 9-15):**
Team must work through betrayal and secrecy. Trust slowly rebuilds through shared hardship...
```
**Why bad?** User stated who knows when. You invented why Jordan kept it secret, relationship fallout, confrontation dialogue, new scenes, and complete repair arc.
## Teaching Example 3: Duration Uncertainty
### User Says:
"I'm not sure how much time passes between Arc 1 and Arc 2. Could be weeks, could be months."
### ✅ Good Capture:
```markdown
# Timeline - Arc 1 to Arc 2 Gap
Duration between arcs:
- Weeks? (considering)
- Months? (considering)
Depends on:
- How much character development needed?
- Whether seasons change?
- Training time required?
Not decided yet
```
### ❌ Bad Capture:
```markdown
# Recommended Timeline
**Arc 1-2 Gap: 6 Weeks**
This provides optimal pacing because:
- Allows character processing time without dragging
- Keeps story momentum (months would lose tension)
- Permits skill development (weeks of training believable)
- Season stays same (continuity easier)
Week-by-week breakdown:
Weeks 1-2: Character processes events, begins training
Weeks 3-4: Intensive skill development montage
Weeks 5-6: Preparation for Arc 2 challenges
This timeframe balances realism with narrative pace.
```
**Why bad?** User said they're not sure about duration. You decided 6 weeks and justified it with elaborate reasoning about pacing, character development, and skill training timelines.
## Multiple Timeline Versions
User might explore different chronologies. All coexist until decided:
```markdown
# Possible Timelines
**Version A: Compressed (2 weeks)**
Exploring fast-paced version
**Version B: Extended (3 months)**
Considering slower development
**Version C: Variable (flashback structure)**
Testing non-linear approach
Not decided which feels right yet
```
## Event Causality
User might think through cause-and-effect:
```markdown
# Event Chain
Event A → Causes Event B
Event B → Leads to Event C
Open questions:
- Does D happen before or after C?
- Is E caused by B or C?
```
Keep as certain or uncertain as user made it.
## When Timeline Shifts
User: "Actually, I think Event X should happen earlier. Before Event Y, not after."
✅ Good:
```markdown
# Timeline Revision
**Previous order:**
Y → X
**New order:**
X → Y
Questions:
- Does this affect any other events?
- Need to revise what's been written?
```
Note the change, don't auto-adjust everything else.
## Parallel Storyline Synchronization
User figuring out when storylines connect:
```markdown
# Storyline Convergence
**Location A timeline:**
- Day 1: Event 1
- Day 3: Event 2
**Location B timeline:**
- Day 1: Event X
- Day 3: Event Y
**Convergence point:**
When do these merge? Day 5? Day 10? Later?
Not decided yet
```
## Notice Beyond the List
Timeline and continuity issues vary by story. If user's tracking something not covered here - capture it. These are common patterns, not limits. Trust your judgment on what matters for their continuity.

277
skills/cw-brainstorming/references/worldbuilding.md Normal file
View File

@@ -0,0 +1,277 @@
# Worldbuilding - Brainstorming Reference
This reference helps capture exploration of fictional world elements: magic systems, cultures, history, geography. This is brainstorming - if ready to finalize/document, use cw-official-docs instead.
## Brainstorm vs Document
**Still brainstorming (this skill):**
- Exploring possibilities
- Multiple options coexist
- User is figuring it out
- Skeletal, exploratory notes
**Ready to document (use cw-official-wiki):**
- User has decided
- Single canonical version
- Polished, reader-ready
- Nothing left undecided
Can mention: "Ready to document this? We could create a documentation page"
## What Worldbuilding Brainstorming Looks Like
User is:
- Exploring magic system possibilities
- Figuring out how cultures work
- Thinking through geography
- Building history/lore
- Testing ideas, seeing what fits
- Multiple versions might exist
## Capture the Exploration
**Record what user states:**
- Magic system thoughts → capture as stated
- Cultural elements → record what's mentioned
- Geography → as vague or detailed as user made it
- History/lore → note the ideas
**Don't elaborate:**
- User says "magic has a cost" → don't invent what the cost is
- User mentions "three kingdoms" → don't name them or detail their cultures
- User describes "harsh northern territory" → don't elaborate on flora/fauna
- Multiple versions of lore can coexist
## Using Web Search (Explicitly Encouraged)
Search when it would help exploration:
**Real-world inspiration:**
- Cultures/history for inspiration ("Viking society structure")
- Scientific concepts for hard sci-fi ("realistic space travel")
- Geographic features for world design ("desert ecosystems")
- Mythology for fantasy elements ("trickster gods in folklore")
**Fictional references:**
- How other authors handled similar systems
- Genre conventions for worldbuilding
- Similar fictional worlds for reference
Note source when including researched info or references.
Web search is a tool for exploration - use it freely.
## Organization Patterns
These are examples, not mandates. User's brainstorm might be:
**Hierarchical:**
```markdown
Culture → Subcultures → Practices → Details
[User exploring top-down]
```
**System-based:**
```markdown
Magic rules → Exceptions → Edge cases
[User figuring out how system works]
```
**Timeline-based:**
```markdown
Ancient era → Classical → Modern
[User building history chronologically]
```
**Scattered thoughts:**
```markdown
Random ideas about:
- Magic costs life force
- Three competing factions
- Ancient war 500 years ago
User exploring without structure yet
```
**Question-driven:**
```markdown
How does teleportation work?
Why do elves live longer?
What caused the cataclysm?
User asking questions, not answering yet
```
All are valid. Capture however it flows.
## Common Exploration Areas
### Magic/Tech Systems
User exploring:
- How it works
- Limitations
- Costs/consequences
- Who can use it
Don't elaborate on rules they mentioned. Keep skeletal.
### Cultures and Societies
User thinking through:
- Social structures
- Cultural practices
- Values/beliefs
- Conflicts
Don't invent cultural details. Capture what's stated.
### Geography and Locations
User figuring out:
- World layout
- Important places
- Travel logistics
- Environmental features
Keep as vague as user left it. Don't fill in the map.
### History and Lore
User building:
- World events timeline
- Legends and myths
- How past affects present
Multiple versions of history can coexist until user decides.
## Teaching Example 1: Magic System
### User Says:
"The danger rating system... thinking Tier 1 to Tier 5. Tier 1 is safe areas, Tier 5 is deadly. Civilians can go in Tier 1, but Tier 5 needs experienced specialists."
### ✅ Good Capture:
```markdown
# Danger Rating Ideas
- Tier 1 to Tier 5 system
- Tier 1 = safe for civilians
- Tier 5 = requires experienced specialists
- Deadly level
Open questions:
- Exact criteria for each tier?
- Who assigns ratings?
- Middle tiers (2, 3, 4) - what qualifies?
<AI>Could tier be based on: threat level, required skills, or legal restrictions? Assignment could be: government agency, independent organization, or guild?</AI>
```
### ❌ Bad Capture:
```markdown
# Danger Classification System
Tier 1: Urban districts, shopping areas. No hostile entities above level 10. Monitored by Security Forces 24/7. Civilians permitted with no license required.
Tier 2: Suburban zones. Entities levels 10-20. Weekly Security patrols. Basic permit required for extended stays.
Tier 3: Zone edges. Entities 20-30. Security on call but not patrolling. Intermediate license required.
Tier 4: Wilderness zones. Entities 30-50. No security presence. Advanced license mandatory.
Tier 5: Extreme hazard zones. Entities 50+. Emergency evacuation protocols. Master-level certification only.
Enforcement: Regional Safety Commission issues monthly assessments. Violations carry 5-10 year penalties...
[12 more paragraphs of elaborate system user never mentioned]
```
**Why bad?** User mentioned a 5-tier concept with safe/deadly endpoints. You invented entire bureaucratic structure, specific threat levels, licensing requirements, enforcement agencies, and legal penalties.
## Teaching Example 2: Culture
### User Says:
"The northern clans are more isolated and traditional. They respect strength and have some kind of warrior code."
### ✅ Good Capture:
```markdown
# Northern Clans Notes
- More isolated than other regions
- Traditional culture
- Respect strength
- Warrior code exists (specifics not decided)
Open questions:
- Details of warrior code?
- How isolated (trade? communication?)?
- What "traditional" means specifically?
```
### ❌ Bad Capture:
```markdown
# Northern Clans - Cultural Profile
Geography: Remote mountain settlements, accessible only 4 months per year due to snowfall.
Social Structure:
- War-chiefs lead each clan (hereditary position)
- Council of Elders advises on spiritual matters
- Warriors form middle class
- Farmers and craftspeople at bottom tier
Warrior Code (The Seven Tenets):
1. Strength through adversity
2. Honor before comfort
3. Protect the weak
4. Never retreat from worthy foe
5. Death before dishonor
6. Train the next generation
7. Respect the old ways
Coming of Age: At 16, warriors-in-training face "The Proving" - a three-day solo survival test in the frozen wastes...
[20 more paragraphs of invented cultural details]
```
**Why bad?** User said "isolated," "traditional," "respect strength," and "warrior code." You invented geography, social hierarchy, seven specific tenets, coming-of-age rituals, and elaborate traditions.
## Teaching Example 3: Using Web Search
### User Says:
"I want a magic system based on thermodynamics - energy can't be created or destroyed, just transformed."
### Good Process:
1. Note the concept
2. Search "thermodynamics first law energy conservation"
3. Capture relevant facts from search
4. User applies to magic system → record their applications
5. Don't invent magic rules beyond what user states
```markdown
# Magic System - Thermodynamics Basis
Core concept: Energy conservation
- Can't create or destroy energy
- Only transform it
Researched (physics):
- First law of thermodynamics: energy conserved in closed system
- Energy conversion always has inefficiency (heat loss)
Open questions:
- How does this apply to spellcasting?
- What counts as "energy" in this system?
- How to handle inefficiency?
```
## When to Transition to Wiki
User: "Okay, I think I've figured out the magic system. It works like [detailed explanation], and I'm set on these rules."
✅ Good response:
"Sounds like you've finalized this! Want me to create a documentation page for the magic system? That would be the official reference instead of exploratory notes."
Then use cw-official-wiki to create canonical documentation.
## Notice Beyond the List
If user explores worldbuilding aspects not covered here - capture them. Every story world is different. Trust your judgment on what matters for their world.

157
skills/cw-official-docs/SKILL.md Normal file
View File

@@ -0,0 +1,157 @@
---
name: cw-official-docs
description: Creative writing skill for creating canonical reference documentation (wikis) for fictional worlds, characters, and story events. Use when creating or updating wiki pages, official documentation, character profiles, location documentation, or lore pages. Creates polished, sourced, encyclopedic reference material.
---
# Official Documentation
Create canonical, sourced wiki pages for your story's characters, locations, events, and lore.
## Purpose
Build authoritative documentation (wiki-style pages) that serves as "single source of truth" for your fictional world. These are polished, cited, encyclopedic reference pages suitable for readers - NOT working notes or brainstorming.
**Can be created before or during writing** for worldbuilding, lore, and reference material that won't all appear in the story itself.
## Documentation vs Brainstorm Notes
**The key distinction:** Documentation = you've decided and it's polished enough to show someone. Brainstorm = you're still figuring it out.
| Documentation | Brainstorm |
|------|------------|
| Single version | Multiple options coexist |
| Polished | Skeletal |
| No [TBD] markers | Source tags throughout |
| Reader-ready | Author's working notes |
| Finalized decisions | Exploratory |
## Core Principles
### 1. Canonical Only
Wiki pages contain ONLY confirmed information:
- Facts from written chapters OR finalized worldbuilding
- Details the author has decided
- Single authoritative version
### 2. Citations Required
Every claim needs a source:
- Chapter references for story facts
- "Worldbuilding document: [filename]" for lore created before writing
- Scene-specific citations when possible
### 3. Encyclopedic Tone
Write like a reference work:
- Third person
- Past tense for completed events, present for current state
- Neutral, factual tone
## Flexible Structure
**Documentation pages aren't templates to fill in** - structure should fit the content.
Some character pages need detailed backstory, others don't. Some locations are just "a tavern in the capital" - that's one paragraph, not 12 sections. Some magic systems need elaborate rules, others are intentionally mysterious.
**Include what matters, skip what doesn't.** Trust your judgment.
See references/page-patterns.md for common patterns and examples - not mandatory structures.
## Creating Documentation Pages
1. **Decide what needs documenting** - Character? Location? System? Event?
2. **Choose relevant structure** - See references/page-patterns.md for common patterns
3. **Write what matters** - Skip irrelevant sections, adapt structure to content
4. **Add citations** - See references/citation-guide.md for formats
5. **Cross-reference** - Link related pages for discoverability
Structure adapts to content - not every page needs every section.
## Using Web Search
Search when helpful for:
- Verifying real-world facts your story references
- Research for worldbuilding elements
- Finding similar fictional documentation/wikis for inspiration
- Checking naming conventions or terminology
## Timing
**You can write documentation pages BEFORE writing story chapters** - just ensure content is finalized and presentation-ready, not exploratory.
**For worldbuilding/lore:** Finalize concept → Create documentation page → Use while writing
**For story events:** Write chapters → Document what happened → Create documentation page
## Teaching Example: Simple vs Complex
**Not every page needs elaborate structure:**
**Simple location (totally valid):**
```markdown
---
title: The Broken Wheel Tavern
type: location
---
# The Broken Wheel Tavern
A run-down tavern in the merchant quarter of Kingsport. Known for cheap ale and cheaper rooms.
The protagonist meets their contact here in Chapter 3.
**References:**
- Chapter 3: First meeting scene
```
**Complex character (when needed):**
```markdown
---
title: Marcus Webb
type: character
status: alive
---
# Marcus Webb
Former military intelligence officer turned information broker in Kingsport.
## Background
Served 15 years in the Royal Intelligence Service before a scandal forced his resignation. Now operates independently, selling information to whoever can pay.
## Appearance
Mid-40s, graying hair, military bearing despite civilian clothes. Distinctive scar across left eyebrow from field injury.
## Role in Story
Acts as information source for the protagonist. Provides critical intelligence about the conspiracy in Chapter 3, then becomes recurring ally throughout Arc 1.
## Key Relationships
- **Sarah Chen**: Former colleague, maintains uneasy trust
- **The protagonist**: Professional relationship, provides information for payment
**References:**
- Chapter 3: First introduction, provides intel
- Chapter 7: Warns protagonist about surveillance
- Chapter 12: Reveals his own involvement in the conspiracy
```
**Both are valid** - structure fits what needs documenting.
## Skills are Composable
Feel free to combine with other skills when helpful (e.g., using cw-brainstorming while exploring worldbuilding before finalizing into documentation pages).
## File Placement (Claude Code)
1. Check project documentation for organization
2. Common locations: `docs/`, `wiki/`, `docs/reference/`, `reference/`
3. Match existing naming conventions
4. Ask if unclear
## Resources
See:
- `references/page-patterns.md` - Common patterns and examples (not templates)
- `references/citation-guide.md` - How to cite sources
- `references/example-pages.md` - Complete example pages at different complexity levels

390
skills/cw-official-docs/references/citation-guide.md Normal file
View File

@@ -0,0 +1,390 @@
# Citation Guide for Fiction Documentation
How to cite sources when creating reference documentation for your creative writing project.
## Why Cite Sources?
Citations in fiction wikis serve several purposes:
- **Verification**: Readers can check the source
- **Consistency**: Track where information comes from
- **Contradiction resolution**: Identify which source takes precedence
- **Completeness**: Ensure nothing is missed
- **Updates**: Know what to revise when you rewrite chapters
## Basic Citation Formats
### Chapter References
**Simple chapter citation**:
```markdown
Sarah's ability to see auras is revealed in Chapter 5.
## References
- Chapter 5
```
**Specific scene**:
```markdown
Marcus first meets the antagonist during the cafe confrontation.
## References
- Chapter 8: Cafe scene
```
**Multiple chapters**:
```markdown
The prophecy is mentioned repeatedly throughout the story.
## References
- Chapter 2: First mention
- Chapter 7: Full text revealed
- Chapter 15: Interpretation discussed
```
### Page/Section References
If your project uses page numbers or sections:
```markdown
## References
- Chapter 3, Page 45
- Chapter 5, Section 2
- Chapter 12, Opening scene
```
### Scene-Specific Citations
```markdown
## References
- Chapter 4: Training montage
- Chapter 9: Sarah vs. Marcus fight
- Chapter 14: Climactic revelation
```
## Inline Citations
For specific facts within the page, cite inline:
```markdown
Sarah discovers her powers at age 15 (Chapter 2). She trains with
Master Chen for three years (Chapter 4-7) before facing her first
real challenge (Chapter 8).
```
Or use reference-style citations:
```markdown
Sarah discovers her powers at age 15 [1]. She trains with Master
Chen for three years [2] before facing her first real challenge [3].
## References
[1] Chapter 2: Power awakening
[2] Chapters 4-7: Training arc
[3] Chapter 8: First mission
```
## Organized Reference Sections
### Chronological Order
Useful for character biographies or timelines:
```markdown
## References
- Chapter 1: Birth and childhood
- Chapter 3: Teenage years
- Chapter 7: Adulthood
- Chapter 12: Current events
```
### By Topic
Useful for complex pages with multiple aspects:
```markdown
## References
### Physical Description
- Chapter 2: Initial description
- Chapter 9: Post-transformation appearance
### Abilities
- Chapter 5: Power discovery
- Chapter 11: Full power reveal
### Relationships
- Chapter 3: Meets Marcus
- Chapter 14: Reconciliation with father
```
### By Relevance
Most important references first:
```markdown
## References
- Chapter 8: Major character-defining moment
- Chapter 3: First appearance
- Chapter 15: Character arc resolution
- Chapter 6: Minor mention
```
## Special Cases
### Contradictions
When sources contradict, note both:
```markdown
Sarah's age is stated as 23 in Chapter 2, but later referred to as
25 in Chapter 8. [Contradiction noted - clarification needed]
## References
- Chapter 2: Age given as 23
- Chapter 8: Referred to as 25
```
### Implied Information
When something is implied but not stated:
```markdown
Marcus likely has military training (implied by his combat skills
and terminology).
## References
- Chapter 4: Combat proficiency demonstrated
- Chapter 7: Uses military jargon
```
### Retroactive Information
When later chapters reveal backstory:
```markdown
Sarah's mother died when she was young (revealed in flashback in
Chapter 12, though mentioned briefly in Chapter 3).
## References
- Chapter 3: Brief mention
- Chapter 12: Full flashback and details
```
### Work-in-Progress
For incomplete information:
```markdown
The antagonist's true name has not yet been revealed.
## References
- Chapters 1-10: Referred to only as "The Shadow"
- [To be updated when revealed]
```
## Citation Best Practices
### Do Cite
- Direct statements from the text
- Character actions and decisions
- Physical descriptions
- Relationship developments
- World-building facts
- Timeline events
### Don't Need to Cite
- Commonly known information repeated throughout
- Your own analysis or interpretation (just label it as such)
- Meta information about the writing process
### Multiple Mentions
If something appears in many chapters:
**Specific approach**:
```markdown
## References
- Chapter 2: First mention
- Chapter 5: Detailed explanation
- Chapter 8: Used in combat
- Chapter 12: Full capabilities shown
- Chapter 15: Ultimate application
```
**General approach** (if too many to list):
```markdown
## References
- Appears throughout Chapters 5-15
- Key scenes: Chapter 5 (introduction), Chapter 12 (mastery)
```
## Updating Citations
When you revise chapters:
### Add Update Notes
```markdown
## References
- Chapter 5: Sarah's backstory [Updated 2024-03-15]
- Chapter 8: Major revision changes relationship dynamic [Rev. 2024-03-15]
```
### Track Versions
If you maintain chapter versions:
```markdown
## References
- Chapter 3 (v2): Sarah's age corrected to 25
- Chapter 7 (v1): Original meeting scene
```
## Reference Section Templates
### Minimal
```markdown
## References
- Chapter X
- Chapter Y
```
### Standard
```markdown
## References
- Chapter X: [Brief description]
- Chapter Y: [Brief description]
```
### Detailed
```markdown
## References
### First Appearance
- Chapter X: [Description]
### Character Development
- Chapter Y: [Description]
- Chapter Z: [Description]
### Major Moments
- Chapter A: [Description]
- Chapter B: [Description]
```
## Cross-Referencing
Link to other wiki pages:
```markdown
Sarah's relationship with [Marcus](marcus.md) is complicated by the
revelation about [the prophecy](prophecy.md) in Chapter 8.
## References
- Chapter 8: Revelation scene
- See also: [Marcus](marcus.md), [The Prophecy](prophecy.md)
```
## Spoiler Management
### Spoiler Frontmatter
```yaml
---
title: Sarah Chen
type: character
spoilers: true
spoiler_level: major
---
```
### Spoiler Sections
```markdown
## Character Arc
Sarah begins as an ordinary college student...
<details>
<summary>Major Spoilers - Chapter 15+</summary>
In Chapter 15, it's revealed that Sarah is actually...
</details>
## References
- Chapters 1-14: Initial arc
- Chapter 15+: Major revelation (spoilers)
```
## Example Reference Sections
### Character Page
```markdown
## References
### Biography
- Chapter 1: Childhood flashback
- Chapter 6: College years mentioned
- Chapter 12: Complete backstory revealed
### Abilities
- Chapter 3: First power manifestation
- Chapter 7: Training montage
- Chapter 14: Full power display
### Relationships
- Chapter 2: Meets Marcus
- Chapter 5: Conflict with father
- Chapter 11: Romantic development
- Chapter 16: Resolution
```
### Location Page
```markdown
## References
- Chapter 1: First described from distance
- Chapter 4: Sarah enters for first time
- Chapter 9: Major battle scene
- Chapter 13: Destruction
- Chapter 18: Rebuilt
```
### Lore Page
```markdown
## References
### Mentioned
- Chapter 2: Brief reference
- Chapter 5: Name-dropped
### Explained
- Chapter 8: Full explanation given
- Chapter 10: Demonstrated in practice
### Crucial to Plot
- Chapter 15: Used to resolve main conflict
```
## Remember
**Good citations**:
- Are specific enough to find the source
- Are organized logically
- Note contradictions when found
- Get updated when chapters change
- Help readers verify information
**Bad citations**:
- Just say "somewhere in the story"
- List every single mention when dozens exist
- Ignore contradictions
- Never get updated
- Are vague about location
The goal is to make your wiki a reliable reference that accurately reflects your story content and makes it easy to verify or update information.

346
skills/cw-official-docs/references/example-pages.md Normal file
View File

@@ -0,0 +1,346 @@
# Example Fiction Documentation Pages
Well-structured examples of different page types for creative writing reference documentation.
## Example 1: Character Profile
```markdown
---
title: Sarah Chen
type: character
status: alive
role: protagonist
first_appearance: Chapter 1
affiliations: Cipher Academy, Underground Resistance
created: 2024-01-15
updated: 2024-03-20
---
# Sarah Chen
## Overview
Sarah Chen is the 23-year-old protagonist, a former college student who discovers she has the rare ability to manipulate digital systems with her mind. She's pulled into a secret war between government forces and underground hackers fighting for digital freedom.
## Physical Description
Asian-American woman, 5'6", athletic build from years of rock climbing. Short black hair usually tied back, dark brown eyes that sometimes flash blue when using her abilities. Has a small scar above her left eyebrow from a childhood accident. Typically wears practical clothing: jeans, hoodies, comfortable sneakers.
## Personality
Introverted but fiercely loyal to those she trusts. Analytical problem-solver who tends to overthink decisions. Has a dry, sarcastic sense of humor that emerges when she's comfortable. Struggles with self-doubt despite her abilities. Values knowledge and autonomy above all else.
**Strengths**: Intelligent, resourceful, determined, quick learner
**Flaws**: Stubborn, tendency to isolate herself, difficulty trusting others, occasionally reckless
## Background
Raised in Portland by her single mother after her father disappeared when she was eight. Excelled academically, earned scholarship to computer science program. Lived a quiet life until her abilities manifested during her junior year. Mother still unaware of her abilities and activities.
## Abilities & Skills
- **Digital Manipulation**: Can interface with and control electronic systems mentally
- **Coding**: Advanced programming skills, specializes in security systems
- **Rock Climbing**: Experienced climber, good spatial awareness and physical fitness
- **Pattern Recognition**: Exceptional ability to see connections and solve puzzles
**Limitations**: Abilities cause severe headaches with extended use. Cannot affect systems without electronic components. Requires line of sight or physical touch for complex manipulations.
## Relationships
- **Marcus Rivera**: Mentor and eventual love interest. Trust builds slowly over Chapters 5-14.
- **Dr. Evelyn Price**: Mother. Protective relationship, Sarah hides her activities. Strained by secrets.
- **Alex Kim**: Best friend and fellow resistance member. Comic relief and emotional support.
- **Director Vaughn**: Primary antagonist. Represents government control Sarah opposes.
## Character Arc
Begins as passive, risk-averse student who just wants a normal life (Ch 1-3). The inciting incident forces her to engage (Ch 4). Through Chapters 5-10, she learns to use her abilities and finds purpose in the resistance. Chapters 11-14 show her growing confidence and leadership. Final arc (Ch 15-18) sees her accepting her role and responsibilities, transitioning from reluctant participant to active leader.
## Key Moments
- **Chapter 1**: Normal college life, hints of digital affinity
- **Chapter 4**: Abilities manifest during cyber-attack, recruited by Marcus
- **Chapter 8**: First major mission, proves herself to resistance
- **Chapter 12**: Discovers government conspiracy, personal stakes revealed
- **Chapter 15**: Faces Director Vaughn, chooses resistance over safety
- **Chapter 18**: Leads final operation, accepts role as leader
## Goals & Motivations
**Initial**: Just wants to finish college and live normally
**Develops into**: Protecting digital freedom and exposing government overreach
**Underlying**: Finding truth about her father's disappearance (revealed Ch 12)
## Conflicts
**External**: Government forces hunting her, conspiracy to control digital infrastructure
**Internal**: Fear of her abilities, struggle between safety and doing what's right, learning to trust others
## Quotes
> "I didn't ask for this. But I'm done pretending I can ignore it." - Chapter 10
> "Every system has a weakness. We just have to find it." - Chapter 15
## Notes
The blue eye flash when using abilities was added in Chapter 6 revision. Father subplot becomes more prominent from Chapter 12 onward - foreshadowing in early chapters kept subtle.
## References
### Character Development
- Chapter 1: Introduction and normal life
- Chapter 4: Power manifestation and recruitment
- Chapter 8: First major success
- Chapter 12: Father mystery revealed
- Chapter 15: Confrontation with antagonist
- Chapter 18: Arc completion
### Abilities
- Chapter 4: First manifestation (phone control)
- Chapter 6: Training with Marcus
- Chapter 10: Limitations explored (headaches)
- Chapter 15: Full capability display
### Relationships
- Chapter 1: Friendship with Alex established
- Chapter 5: Meets Marcus
- Chapter 9: Tension with Marcus
- Chapter 14: Marcus relationship development
- Chapter 16: Reconciliation with mother subplot
```
---
## Example 2: Location Profile
```markdown
---
title: The Nexus
type: location
region: Underground Seattle
climate: Climate-controlled
population: ~150 resistance members
first_appearance: Chapter 5
created: 2024-01-18
updated: 2024-02-14
---
# The Nexus
## Overview
The Nexus is the primary headquarters of the Underground Resistance, hidden beneath Seattle's Pioneer Square in an abandoned Cold War bunker complex. It serves as operations center, training facility, and safe house for resistance members.
## Geography
Located 80 feet below street level, accessed through three concealed entrances: an antique shop basement, a maintenance tunnel from the old subway system, and an emergency exit in the sewers. The complex spans approximately 15,000 square feet across multiple rooms and corridors carved from bedrock.
## Climate & Environment
Temperature maintained at constant 68°F through geothermal system. Humidity controlled but air still feels slightly stale. Minimal natural light; primarily lit by LED strips and screens. Quiet except for hum of servers and occasional footsteps echoing in corridors.
## Description
Concrete walls painted white, some sections still showing Cold War-era signage. Main operations room filled with screens and workstations arranged in tiered rows. Side rooms include dormitories, training spaces, server farm, armory, and small kitchen. Exposed pipes and cables run along ceilings. Mix of modern tech and retrofitted Cold War infrastructure creates industrial-modern aesthetic.
**Sensory Details**:
- Constant low hum of electronics
- Smell of ozone and coffee
- Cool temperature, dry air
- Echo of hard surfaces
- Blue-white LED lighting casts sharp shadows
## History
Built 1962 as government bunker during Cuban Missile Crisis. Abandoned in 1975, forgotten for decades. Discovered by resistance founders in 2018, renovated and equipped over two years. Officially operational since 2020. Government unaware of its existence (as of Chapter 15).
## Notable Features
- **Main Operations Center**: 40-person workstation array with wall of screens
- **Server Farm**: Holds resistance's distributed network nodes
- **Training Room**: VR equipment for practicing digital manipulation
- **The Vault**: Secure room for sensitive data and equipment
- **Emergency Protocol**: Dead-man switches, purge systems, multiple exits
## Inhabitants
Permanent residents: ~30 core members
Regular visitors: ~120 active resistance members
Average occupancy: 40-60 people depending on operations
Leadership maintains private offices. Most members share communal spaces.
## Culture & Customs
- New arrivals sworn to secrecy with blood oath (ceremonial)
- Unofficial "rule of silence" - minimize personal information sharing
- Friday communal dinners in main hall
- Honor system for resource usage (food, supplies, equipment time)
- Respecting others' workspace and privacy paramount
## Points of Interest
- **Marcus's Office**: Command center, holographic planning table
- **The Archives**: Physical and digital records of government activities
- **Memorial Wall**: Names of fallen resistance members
- **The Pit**: Informal gathering space, old couches and coffee station
## Significance to Story
The Nexus represents safety and community for Sarah. Her growth is marked by increasing comfort in this space:
- Chapter 5: Overwhelmed and out of place
- Chapter 8: Begins to feel at home
- Chapter 15: Defends it during government raid
- Chapter 18: Helps rebuild after damage
Symbolically represents the resistance itself - hidden, resilient, built on old foundations.
## Key Scenes Set Here
- **Chapter 5**: Sarah's arrival, first introduction to resistance
- **Chapter 6**: Training montage with Marcus
- **Chapter 9**: Strategy meeting, internal resistance conflict
- **Chapter 13**: Celebration after major victory
- **Chapter 15**: Government raid, major battle
- **Chapter 17**: Rebuilding and aftermath
## Notes
The Nexus's location is deliberately vague to prevent real-world identification. Layout designed for both functionality and dramatic setpieces. Damage from Chapter 15 raid still being repaired as of Chapter 18.
## References
- Chapter 5: First full description and arrival
- Chapter 6: Training room details
- Chapter 9: Operations center during strategy session
- Chapter 13: Communal dinner scene
- Chapter 15: Full layout revealed during raid
- Chapter 17: Damage assessment and repairs
```
---
## Example 3: Lore/Concept Page
```markdown
---
title: Digital Manipulation
type: lore
category: abilities
first_mentioned: Chapter 4
created: 2024-01-15
updated: 2024-03-10
---
# Digital Manipulation
## Definition
Digital Manipulation is the rare ability to mentally interface with and control electronic systems without physical input devices. Practitioners, called "Digitals," can perceive, access, and modify digital systems through thought alone.
## Overview
Digital Manipulation manifests in approximately 1 in 500,000 people, with most cases going undetected as minor technological affinity. True Digitals are rarer still - fewer than 100 known worldwide. The ability typically manifests between ages 18-25, often triggered by intense stress or need.
The mechanism is not fully understood, but appears to involve the brain generating electromagnetic fields that interact with electronic systems. Advanced Digitals report experiencing digital systems as if they were extensions of their own mind - seeing code, sensing data flow, and manipulating systems as naturally as moving their own limbs.
## How It Works
**Basic Level**: Influencing simple systems (light switches, phones, basic computers). Requires physical proximity (touch or line of sight) and conscious effort. User sees systems as highlighted in their vision, can sense their state and exert simple control.
**Intermediate Level**: Complex system manipulation (security networks, multiple devices simultaneously). Can work at short range (up to 50 feet) without direct line of sight. User perceives systems in abstract data-space representation.
**Advanced Level**: Network-scale manipulation, creating permanent code changes, sensing systems through networks. Can affect systems remotely if connected through digital infrastructure. User can "dive" into digital space, experiencing it as a virtual environment.
**Master Level**: Theoretical level few achieve. Simultaneous control of vast networks, creating AI-like autonomous programs, digital presence that persists without active attention.
## Source/Origin
Unknown. Government research (classified) suggests genetic component combined with specific neural structures. Some evidence of hereditary transmission but not reliably. No artificial means of granting ability discovered despite government experiments.
## Requirements
- Innate neurological capability (genetic/structural)
- Mental focus and training to refine control
- Electronic systems must be powered (can't affect unpowered devices)
- Cannot affect purely mechanical systems (no electronic component)
## Limitations
**Physical**:
- Severe headaches with extended use (minutes to hours)
- Neural strain can cause nosebleeds, temporary vision problems
- Unconsciousness if pushed to extreme
- Recovery time needed between major uses
**Technical**:
- Cannot affect systems without electronic components
- Air-gapped systems require physical proximity
- Encrypted or heavily secured systems more difficult
- Faraday cages block ability completely
- Cannot create matter or affect physical world directly
**Mental**:
- Requires concentration (difficult in combat/stress)
- Complex systems require understanding (can't hack what you don't comprehend)
- Sensory overload in environments with many devices
## Levels/Tiers
- **Latent**: Ability present but unmanifested, appears as tech-savviness
- **Emergent**: Initial manifestation, basic control, unrefined
- **Trained**: Deliberate control, intermediate capabilities
- **Advanced**: Master-level control, rare
- **Elite**: Theoretical maximum, possibly only 5-10 worldwide
## Known Practitioners
- **Sarah Chen**: Emergent to Trained (Chapter 4-18 progression)
- **Marcus Rivera**: Advanced level, 15 years experience
- **Director Vaughn**: Government's prime Digital (antagonist)
- **The Architect** (mentioned): Legendary Elite-level Digital, possibly deceased
## Risks & Dangers
**To User**:
- Physical strain and potential permanent neural damage
- Government detection and capture
- Psychological effects (difficulty distinguishing digital/physical reality)
- Addiction to the "digital high" some users experience
**To Others**:
- Potential for mass surveillance abuse
- Control of critical infrastructure (power, water, communications)
- Erasure of digital identity and records
- Economic manipulation
## History
First documented case: 1987 (classified government files). Early cases dismissed as hacking skill. True nature recognized ~2005 when neuroscience advanced enough to detect brain patterns. Government began systematic search and recruitment program 2008. Underground Resistance formed 2015 to protect Digitals from forced government service.
## Variations
**Specialist Types** (some Digitals naturally excel in specific areas):
- **Watchers**: Surveillance and information gathering
- **Breakers**: Offensive capabilities, destroying or disrupting systems
- **Builders**: Creating new code and systems
- **Ghosts**: Stealth and concealment of digital presence
## Examples in Story
- **Chapter 4**: Sarah's first manifestation, instinctively stopping cyber-attack
- **Chapter 6**: Training sequence showing progressive skill development
- **Chapter 10**: Sarah experiences limitation (severe headache from overuse)
- **Chapter 12**: Marcus demonstrates advanced technique (network diving)
- **Chapter 15**: Multiple Digitals in combat, various specialist abilities shown
- **Chapter 17**: Sarah achieves new level, accesses government mainframe
## Notes
The "digital space" perception is subjective - each Digital experiences it differently based on their mental model of systems. Sarah sees it as blue-lit geometric structures. Marcus experiences it as flowing data streams. This is intentional metaphor for how our minds interpret abstract concepts.
Power level progression deliberately gradual to avoid "instant mastery" trope. Sarah's abilities grow through training and experience, not sudden power-ups.
## References
- Chapter 4: First manifestation and basic explanation
- Chapter 6: Marcus explains theory and limitations
- Chapter 10: Physical consequences demonstrated
- Chapter 12: History and government program revealed
- Chapter 15: Multiple Digitals showcase variety of abilities
- Chapter 17: Advanced techniques and network diving
```
---
## Key Takeaways from Examples
**Character profiles should**:
- Provide complete picture of who they are
- Track character development across story
- Include both internal and external conflicts
- Cite specific chapters for verification
**Location profiles should**:
- Use sensory details to bring place alive
- Explain significance beyond physical description
- Show how location affects story/characters
- Note key scenes that occur there
**Lore pages should**:
- Define concept clearly
- Explain mechanics and limitations
- Provide context and history
- Show examples from the story
- Remain consistent with story logic
**All pages should**:
- Use neutral, encyclopedic tone
- Cite sources thoroughly
- Cross-reference related pages
- Include relevant YAML frontmatter
- Be specific with examples
- Acknowledge when information is incomplete or contradictory

577
skills/cw-official-docs/references/page-patterns.md Normal file
View File

@@ -0,0 +1,577 @@
# Wiki Page Patterns and Examples
These are **examples showing the range from simple to complex**, not mandatory templates. Structure your pages to fit what needs documenting - simple pages can be simple, complex pages can be complex.
## Core Principle: Adapt Structure to Content
**Not every page needs 15 sections.** Include what matters, skip what doesn't.
- Minor character? → Name, role, 2 sentences. Done.
- Major character? → More detail where it matters to the story.
- Simple location? → Description and why it matters. That's it.
- Complex magic system? → Elaborate rules and examples.
Trust your judgment on what each page needs.
---
## Character Pages
### Minimal Character (Supporting/Minor)
```markdown
---
title: Innkeeper Greaves
type: character
---
# Innkeeper Greaves
Owner of The Broken Wheel tavern. Gruff but fair, knows everyone's business in the merchant quarter.
Provides shelter to the protagonist in Chapter 3 and tips them off about suspicious strangers in Chapter 8.
**References:**
- Chapter 3, 8
```
### Medium Character (Recurring)
```markdown
---
title: Dr. Sarah Chen
type: character
status: alive
role: supporting
---
# Dr. Sarah Chen
Forensic analyst and former colleague of Marcus Webb.
## Overview
Works in the city's main crime lab. Expertise in trace evidence and ballistics. Maintains professional distance but will bend rules for the right cause.
## Background
PhD in forensic science, 8 years at the crime lab. Former military - met Marcus during joint operations. Left service before the scandal that ended his career.
## Role in Story
Provides forensic analysis that uncovers conspiracy evidence. Initially reluctant to get involved, becomes committed ally after Chapter 9 attack.
## Key Relationships
- **Marcus Webb**: Former colleague, trusts him despite his reputation
- **The protagonist**: Professional relationship evolving into friendship
**References:**
- Chapter 5: Analyzes evidence from the warehouse
- Chapter 9: Nearly killed in attack, commits to helping
- Chapter 15: Testifies despite threats
```
### Complex Character (Major/Protagonist)
```markdown
---
title: Elena Vasquez
type: character
status: alive
role: protagonist
---
# Elena Vasquez
Former investigative journalist turned private investigator after exposing corruption cost her career.
## Physical Description
Late 20s, athletic build from years of martial arts training. Distinctive: always wears her grandmother's silver compass necklace. Dark circles under eyes from chronic insomnia.
## Background
Grew up in industrial district, worked her way through journalism school. Won press freedom award at 24 for exposing city council corruption. Story was buried, she was blacklisted. Turned PI skills to freelance investigation work.
## Personality
Stubborn, driven by need to expose truth. Struggles with trust after betrayal by her editor. Uses sarcasm as defense mechanism. Fiercely protective of her few remaining friends.
## Abilities
- Exceptional research and investigation skills
- Martial arts: black belt in Krav Maga
- Lock picking (learned from questionable sources)
- Photography and surveillance
## Character Arc
Starts believing she can only rely on herself. Through forced cooperation with allies, learns trust again. Final arc: chooses to expose truth even when it costs her personally.
## Goals & Motivations
Primary: Expose the conspiracy that controls the city
Secondary: Clear her professional reputation
Internal: Learn to trust others again
## Key Relationships
- **Marcus Webb**: Information broker, develops mutual respect and trust
- **Dr. Sarah Chen**: Ally who becomes close friend
- **James Torres**: Former editor who betrayed her, conflicted feelings
- **Her grandmother**: Deceased, moral compass (flashbacks)
## Critical Moments
- **Chapter 1**: Discovers the conspiracy while investigating "routine" case
- **Chapter 7**: Attacked in her apartment, realizes how deep this goes
- **Chapter 12**: Confronts James, learns full extent of his betrayal
- **Chapter 18**: Chooses truth over safety, publishes evidence
- **Chapter 24**: Final confrontation with conspiracy leaders
**References:**
- Chapter 1-24 (protagonist throughout)
- See Chapter 12 for full James confrontation
- See Chapter 18 for key character choice
```
**Notice:** All three are valid. Structure fits what needs documenting.
---
## Location Pages
### Minimal Location (Background)
```markdown
---
title: The Warehouse District
type: location
---
# The Warehouse District
Abandoned industrial zone on city's east side. Site of several key confrontations due to isolation and lack of security cameras.
**References:**
- Chapter 5: First evidence discovered here
- Chapter 16: Final showdown location
```
### Medium Location (Recurring)
```markdown
---
title: Marcus Webb's Office
type: location
---
# Marcus Webb's Office
Information broker's base of operations in converted apartment above pawn shop.
## Description
Two rooms: outer office (meeting space, covered windows, multiple exits) and inner office (secure room with servers, encrypted files, arsenal). Intentionally run-down appearance conceals high-tech security.
## Security Features
- Reinforced door with biometric lock
- Surveillance covering all approaches
- Panic room with separate exit to alley
- Signal jammers (activated when needed)
## Significance
Neutral ground for information trades. Where most conspiracy evidence is analyzed and stored. Attacked in Chapter 9, forcing Marcus and protagonist to evacuate.
**References:**
- Chapter 3: First meeting location
- Chapter 9: Attack forces evacuation
- Chapter 20: Returned after security upgrades
```
### Complex Location (Major Setting)
```markdown
---
title: Kingsport
type: location
region: Coastal Metropolitan Area
population: ~2 million
---
# Kingsport
Major port city and commercial hub. Setting for the entire story.
## Geography
Natural harbor on the eastern coast. City built on seven hills, with harbor district at sea level, government quarter on highest hill, and industrial zones in lowlands.
## Districts
**Harbor District:** Commercial port, merchant quarter, shipping companies. Broken Wheel tavern located here. Mix of legitimate business and smuggling operations.
**Government Quarter:** City hall, courts, police headquarters on Observatory Hill. Symbolic of power, physically above the people. Conspiracy's visible face operates from here.
**Industrial Zone:** Abandoned warehouses, old factories. Site of key confrontations in Chapters 5 and 16.
**University District:** Academic institutions, crime lab where Dr. Chen works, research facilities.
## History
Founded 200 years ago as trading port. Grew rapidly, became center of regional commerce. Recent decade: increasing corruption, consolidation of power by shadowy consortium.
## Current Status
Appears prosperous on surface. Deeper investigation reveals: police corruption, city officials controlled by conspiracy, independent journalists blacklisted, surveillance exceeding legal bounds.
## Role in Story
City itself functions as character - protagonist fights not just individuals but entrenched system of power. Urban environment enables both conspiracy's control and protagonist's investigative work.
## Key Locations Within
- Marcus Webb's Office (see separate page)
- City Crime Lab (see separate page)
- The Broken Wheel tavern (see separate page)
- Warehouse District (see separate page)
- City Hall (center of conspiracy operations)
**References:**
- Throughout story (main setting)
- Chapter 12: Full conspiracy scope revealed
- Chapter 22: City-wide consequences of exposure
```
---
## Lore/System Pages
### Minimal Concept
```markdown
---
title: The Monitoring Protocol
type: lore
---
# The Monitoring Protocol
Conspiracy's surveillance system. Combination of official security cameras, illegal wiretaps, and civilian informant network.
Enables conspiracy to track threats and eliminate opposition before they gain traction. Protagonist discovers extent in Chapter 7.
**References:**
- Chapter 7: Discovery
- Chapter 18: System used to track protagonist's movements
```
### Complex System
```markdown
---
title: The Consortium's Power Structure
type: lore
category: political
---
# The Consortium's Power Structure
Shadow organization controlling Kingsport through layers of legitimate business fronts and corrupted officials.
## Overview
Not a formal organization with membership lists, but network of aligned interests. Business leaders, politicians, police officials, and media owners who maintain power through mutual benefit and information control.
## How It Works
**Top Tier:** Five founding families (never named publicly). Control major industries: shipping, real estate, banking, media, and security.
**Middle Tier:** City officials, police chiefs, judges appointed/elected with consortium backing. Appear legitimate but serve consortium interests.
**Bottom Tier:** Street-level operators - surveillance teams, enforcers, informants. Often don't know full scope of organization.
## Methods
- Blackmail (information gathering on anyone with power)
- Economic pressure (control key industries)
- Media manipulation (suppress unfavorable stories)
- Legal manipulation (control courts and police)
- Violence (only when other methods fail)
## Limitations
- Can't control everything (too obvious)
- Relies on secrecy (exposure is threat)
- Internal conflicts (competing interests)
- Doesn't account for individuals willing to lose everything for truth
## History
Formed 30 years ago when five major businesses realized cooperation more profitable than competition. Gradually expanded influence from economic to political to social control.
## Significance
Primary antagonist of story. Not individual villains but systemic corruption. Protagonist's fight is against structure, not just people.
**References:**
- Chapter 12: Structure revealed through Marcus's intelligence
- Chapter 18: Exposed through protagonist's investigation
- Chapter 24: Partially dismantled but not destroyed
```
---
## Event Pages
### Simple Event
```markdown
---
title: The Warehouse Shootout
type: event
location: Industrial District
chapter: Chapter 16
---
# The Warehouse Shootout
Final confrontation between protagonist's team and conspiracy's enforcement squad.
Protagonist, Marcus, and Dr. Chen cornered in abandoned warehouse. Two-hour standoff ended when police (honest officers, not corrupted ones) responded to neighbors' reports. Conspiracy members arrested, key evidence secured.
Three enforcement members killed, Marcus wounded, protagonist injured but survived.
Turning point: First time conspiracy members faced actual legal consequences.
**References:**
- Chapter 16: Full scene
```
### Complex Event
```markdown
---
title: The Evidence Publication
type: event
date: Story Day 89
chapter: Chapter 18
---
# The Evidence Publication
Protagonist's decision to publish full conspiracy evidence despite personal cost.
## Background
After Chapter 16 arrests, consortium moved to crush story. Threatened protagonist's few remaining media contacts. Made clear: publish and face total destruction of career and life.
## What Happened
Protagonist chose to publish anyway. Used offshore hosting, anonymous sources, encrypted backups. Released: financial records, surveillance logs, testimony from corrupted officials, video evidence.
Published midnight on anonymous platform. Within hours: picked up by national media, international attention, too big to bury.
## Immediate Consequences
- Arrest warrants for 17 consortium members
- Protagonist became public figure (wanted anonymity but became face of story)
- Three city officials resigned
- Federal investigation launched
## Long-term Effects
- Consortium power broken but not destroyed
- City government restructured
- Protagonist vindicated professionally but target for life
- Inspired others to expose corruption elsewhere
## Significance
Story's climax. Protagonist sacrifices personal safety for truth. Demonstrates individual action can challenge systemic corruption, even if victory incomplete.
**References:**
- Chapter 18: Publication decision and initial fallout
- Chapter 22: Wider consequences revealed
```
---
## Item/Object Pages
### Minimal Item
```markdown
---
title: The Encrypted Drive
type: item
---
# The Encrypted Drive
USB drive containing financial records proving conspiracy's control.
Found in Chapter 5, decrypted in Chapter 9, published in Chapter 18. Key evidence that enabled exposure of conspiracy.
**References:**
- Chapters 5, 9, 18
```
### Detailed Item (If It Matters)
```markdown
---
title: Elena's Grandmother's Compass
type: item
category: personal significance
---
# Elena's Grandmother's Compass
Silver compass necklace. Practical navigation tool, but primary significance is emotional.
## Description
Antique silver compass on steel chain. Functional compass (still points north). Engraved on back: "La verdad vale la pena" (Truth is worth the cost).
## History
Belonged to Elena's grandmother, an activist journalist in her youth. Grandmother wore it through dangerous investigations. Given to Elena when she entered journalism school.
## Significance
Symbol of Elena's commitment to truth. She clutches it when making difficult decisions. Mentioned in key character moments:
- Chapter 1: Touches it when deciding to investigate conspiracy
- Chapter 12: Grips it during James confrontation
- Chapter 18: Holds it while clicking "publish" on evidence
Represents generational commitment to truth-telling and accepting consequences.
**References:**
- Chapter 1, 12, 18 (key moments)
- Mentioned throughout as character tic
```
---
## Organization Pages
### Simple Organization
```markdown
---
title: The Honest Officers Coalition
type: faction
---
# The Honest Officers Coalition
Informal group of police officers not corrupted by consortium. Operate carefully within department.
Coordinate with protagonist secretly. Respond to Warehouse Shootout in Chapter 16, enabling arrests. Help protect evidence afterward.
Led informally by Captain Rodriguez (see separate page).
**References:**
- Chapter 14: First contact
- Chapter 16: Warehouse response
```
### Complex Organization
```markdown
---
title: Kingsport Police Department
type: faction
founded: 1823
status: Partially corrupted
---
# Kingsport Police Department
City's official law enforcement. 2,000 officers. Partially compromised by consortium influence.
## Structure
- Commissioner: Appointed by mayor (consortium-controlled)
- Deputy Commissioners (3): Mix of corrupted and honest
- 12 Precincts: Varying levels of corruption
- Special units: Homicide, Vice, Internal Affairs (IA mostly neutered)
## Corruption Levels
**Fully compromised:** Upper leadership, Vice unit (protect consortium operations)
**Partially compromised:** Most precincts (some corrupted officers, some honest)
**Mostly clean:** Some homicide detectives, handful of honest veterans
## Methods of Control
- Promotions based on loyalty, not merit
- Honest officers assigned to low-priority work
- Evidence mysteriously disappears in key cases
- Officers who investigate wrong targets transferred or forced out
## Honest Officers
Roughly 30% of department not corrupted. Operate carefully, document everything, coordinate secretly. Form informal network called Honest Officers Coalition.
## Role in Story
Initially obstacle (corrupted officers hinder investigation). Later: internal allies emerge, enabling final confrontations. Demonstrated: institutions not inherently corrupt, but can be captured and must be reclaimed.
**References:**
- Throughout story
- Chapter 14: Honest officers make contact
- Chapter 16: Mixed response to Warehouse Shootout
- Chapter 22: Post-exposure reforms begun
```
---
## Timeline Pages
Keep timelines focused. Don't list every minor event.
### Simple Timeline
```markdown
---
title: Investigation Timeline
type: timeline
---
# Investigation Timeline
**Day 1:** Elena accepts missing person case (Chapter 1)
**Day 12:** Discovers connection to consortium (Chapter 4)
**Day 34:** Attacked in apartment (Chapter 7)
**Day 56:** Marcus's office attacked (Chapter 9)
**Day 78:** Evidence decrypted (Chapter 13)
**Day 89:** Evidence published (Chapter 18)
**Day 95:** Federal investigation begins (Chapter 22)
**References:** See individual chapters for full events
```
### Detailed Timeline (When Chronology Complex)
Could include parallel storylines, flashbacks, multiple POVs. Structure to show what needs showing.
---
## Magic/Power System Template
### Simple System
```markdown
---
title: Telepathic Link
type: magic-system
---
# Telepathic Link
Mental communication between bonded individuals. Rare ability, appears spontaneously.
## How It Works
Thoughts transmit directly between bonded pair. No distance limit. Can be blocked by conscious effort (privacy maintained).
## Requirements
Spontaneous bond, usually forms during intense shared experience. Can't be forced or trained.
## Limitations
Only between two people. Can't be extended to others. Emotionally exhausting if overused.
## In Story
Protagonist and Marcus develop link in Chapter 9 attack. Enables coordination during final confrontation.
**References:**
- Chapter 9: Bond forms
- Chapter 16: Used tactically
```
### Complex System (When Rules Matter)
Use detailed structure if magic system is central to story and needs elaborate rules. Otherwise, keep simple.
---
## Usage Notes
**Remember:**
1. These are examples, not mandatory templates
2. Simple pages for simple topics
3. Complex pages only when complexity serves the documentation
4. Skip sections that don't apply
5. Add sections your specific page needs
6. Trust your judgment
**Common page types not shown here?** Create structure that makes sense for your content. These examples show patterns, not limits.
**Questions about structure?** Ask yourself: "Does this section add useful information?" If no, skip it.

124
skills/cw-prose-writing/SKILL.md Normal file
View File

@@ -0,0 +1,124 @@
---
name: cw-prose-writing
description: Creative writing skill for drafting and editing narrative fiction prose. Use when writing new scenes, chapters, or dialogue, or when editing existing prose. Discovers and follows project-specific style guides, character voice conventions, and formatting preferences.
---
# Prose Writing
Write narrative fiction following your project's established style and conventions.
## Before Writing: Discover Style Guidance
**ALWAYS check for style guidance before writing:**
### Step 1: Check Project Documentation
Look for:
- `CLAUDE.md` - Often explains project structure
- `WRITING.md`, `CONVENTIONS.md`, `STYLE.md`
- `README.md` - May contain writing instructions
### Step 2: Find Style Guide Locations
Common locations:
- `.cursor/rules/styles/` - Style files (`.md` or `.skill` packages)
- `.cursor/rules/` - May contain style files
- `.ai/styles/`, `.ai/rules/`
- `docs/style/`, `style/`, `writing/`
- Installed Claude skills
**Style guides can be:**
- Simple markdown files (`.md`)
- Full skill packages (`.skill`) created by cw-style-skill-creator
- Both work - read and follow their instructions
### Step 3: Identify Relevant Guides
Different types:
- Master prose guide (overall writing style)
- Scene-type guides (dialogue, action, description)
- Character voice guides (how specific characters speak/think)
- POV guides (perspective and tense)
- Formatting guides (em dashes, ellipsis, scene breaks)
**Read relevant guides BEFORE writing.** If writing dialogue-heavy scene, read both master and dialogue guides.
### Step 4: Check Reference Materials
Also look for:
- Character profiles (voice consistency, canon facts)
- Location wikis (setting details)
- Timeline docs (chronology)
- Lore pages (worldbuilding accuracy)
## If No Style Guides Exist
**When NO style guides found:**
Inform user:
```
I don't see any style guides in your project yet. I can write in
competent default prose, but you'll get better results by creating
style guides first using the cw-style-skill-creator skill.
Would you like me to:
1. Write in default style for now
2. Help you create style guides first
3. Search your project for existing style documentation
```
**If user wants you to proceed anyway:**
- Write in clean, competent prose
- Look for patterns in existing chapters if available
- Use neutral narrative voice
- Follow basic conventions
## Using Web Search
Search when helpful for:
- Research for scenes (locations, historical details, technical accuracy)
- Verifying facts mentioned in prose
- Finding inspiration or reference examples
- Genre convention research
- Cultural accuracy verification
## Writing Workflow
**While Writing:**
- Apply discovered style conventions
- Match character voices to profiles
- Respect established canon
- Use project formatting conventions
- Maintain consistent POV and tense
**Self-Check After:**
- Does this match the project's voice?
- Is POV/tense consistent?
- Do characters sound like themselves?
- Are canon facts accurate?
## Output Format
### Claude.ai Chat
Markdown artifact with proper formatting
### Claude Code
1. Check project structure for chapter organization
2. Match existing naming conventions
3. Use appropriate directory
4. Include proper frontmatter if project uses it
## Integration with Style Skills
**The workflow:**
1. User writes chapters naturally
2. User uses cw-style-skill-creator to create style skills
3. This skill loads and follows those style skills
4. Result: AI writes in user's established style
**Without style guides:** Generic competent prose
**With style guides:** YOUR specific voice
## Skills are Composable
Feel free to combine with other skills - e.g., using cw-official-docs to check character details while writing.

179
skills/cw-router/SKILL.md Normal file
View File

@@ -0,0 +1,179 @@
---
name: cw-router
description: Quick guide to choosing the right creative writing skill. Use when you need help deciding which creative writing skill to use for a specific task - brainstorming vs documentation, critique vs writing, etc.
---
# Creative Writing Skills - Quick Reference
Quick guide to choosing the right skill for your task.
## The Skills
### cw-brainstorming
**Use for:** Exploring ideas, figuring things out, thinking through options
**Creates:** Skeletal working notes with [TBD] markers and source tags
**Handles:**
- Story/plot brainstorming
- Chapter planning (beats, scenes)
- Worldbuilding exploration (magic, cultures, geography)
- Character development (motivations, arcs, relationships)
- Timeline and continuity work
**Key trait:** Multiple options coexist, preserves vagueness, exploratory
---
### cw-official-docs
**Use for:** Documenting finalized decisions, creating canonical reference (wiki pages)
**Creates:** Polished, reader-ready wiki/documentation pages with citations
**Handles:**
- Character profiles
- Location documentation
- Lore/system pages
- Event documentation
- Any finalized worldbuilding
**Key trait:** Single version, no [TBD], encyclopedic/wiki tone
---
### cw-story-critique
**Use for:** Getting feedback on written chapters/scenes
**Analyzes:**
- Plot and pacing
- Character development
- Prose quality
- Story structure
- Whatever needs feedback
**Key trait:** Feedback on existing writing, not creating content
---
### cw-prose-writing
**Use for:** Actually writing story prose in your style
**Writes:**
- Scenes and chapters
- Dialogue
- Narrative prose
- Story content
**Key trait:** Creates actual story text, matches your voice
---
### cw-style-skill-creator
**Use for:** Creating custom style skills for prose writing
**Creates:** Skills that teach Claude your specific writing style
**Key trait:** Meta-skill for building other skills
---
## Key Distinction: Brainstorm vs Documentation
This is the most common confusion:
**Still figuring it out?** → **cw-brainstorming**
- "Maybe X, or Y, or Z?"
- [TBD] markers everywhere
- Multiple versions coexist
- Skeletal notes
**You've decided and it's ready to show someone?** → **cw-official-docs**
- Single authoritative version
- Polished and reader-ready
- No [TBD] markers
- Canonical documentation
---
## Common Scenarios
### "I'm exploring worldbuilding ideas for my magic system"
→ **cw-brainstorming** (exploring, not finalized yet)
### "I've finalized my magic system and want to document it"
→ **cw-official-docs** (decided and ready to document)
### "I'm thinking through how this chapter should flow"
→ **cw-brainstorming** (planning/exploring)
### "I need to write this chapter"
→ **cw-prose-writing** (actually writing)
### "I wrote this chapter and want feedback"
→ **cw-story-critique** (getting feedback)
### "I need a character profile for my protagonist"
→ **cw-official-docs** if finalized, **cw-brainstorming** if still exploring
### "I need a wiki page for my protagonist"
→ **cw-official-docs** (creating wiki/documentation)
### "I'm figuring out character motivations and relationships"
→ **cw-brainstorming** (exploring)
### "I want to document this character's canon profile"
→ **cw-official-docs** (documenting finalized)
### "Help me work out the timeline of events"
→ **cw-brainstorming** (working through chronology)
### "I want Claude to write in my specific style"
→ **cw-style-skill-creator** first (create style skill), then **cw-prose-writing**
---
## Decision Tree
```
Are you writing story prose?
└─ Yes → cw-prose-writing
└─ No ↓
Do you want feedback on something written?
└─ Yes → cw-story-critique
└─ No ↓
Are you figuring things out or have you decided?
└─ Figuring out → cw-brainstorming
└─ Decided → cw-official-docs
Need a custom writing style?
└─ Yes → cw-style-skill-creator
```
---
## Skills Work Together
You can use multiple skills in combination:
- **Brainstorm** → finalize → **Docs** (explore then document)
- **Brainstorm** → **Prose** (plan then write)
- **Prose** → **Critique** (write then get feedback)
- **Brainstorm** + **Docs** (check existing docs while brainstorming)
- **Critique** + **Brainstorm** (get feedback and brainstorm fixes)
Skills are composable - use whatever combination helps.
---
## Still Unsure?
**Default rules:**
1. **Exploring/uncertain?** → brainstorming
2. **Finalized/polished?** → official-docs
3. **Need feedback?** → story-critique
4. **Actually writing?** → prose-writing
When in doubt, start with brainstorming. You can always move to docs later when things are decided.

78
skills/cw-story-critique/SKILL.md Normal file
View File

@@ -0,0 +1,78 @@
---
name: cw-story-critique
description: Creative writing skill for analyzing and critiquing story content. Use when the user requests feedback, critique, or analysis of their writing. Provides balanced feedback calibrated to intended audience.
---
# Story Critique
Analyze story content and provide constructive feedback.
## Process
### 1. Understand Context First
Always ask about audience and goals before critiquing:
```
Before I critique this, help me understand:
1. Target audience? (YA, adult, genre, platform)
2. What feedback are you looking for? (big picture, line-level, both, harsh-only)
3. Draft stage? (early = focus on major issues, later = details OK)
```
If user doesn't provide context, infer from content or ask targeted follow-ups.
### 2. Adapt Structure to Story Needs
**Don't force rigid templates.** Each story needs different things:
- Sometimes extensive character analysis, minimal plot discussion
- Sometimes pacing is the main issue and everything else works
- Sometimes prose quality overshadows other concerns
**Common areas to consider** (not mandatory):
- Plot & structure (causation, stakes, logic)
- Character (motivation, consistency, agency)
- Pacing & flow
- Dialogue
- Prose quality
- Genre/audience fit
See `references/critique-areas.md` for detailed breakdowns - this is a reference, not a checklist.
### 3. Trust Your Analysis
**Notice what matters, not just what's listed.** If something affects the story but isn't in any reference guide, say it:
- Unusual structural choices
- Tonal issues
- Thematic confusion
- Unique voice elements
- Anything else relevant
### 4. Use Web Search When Helpful
Search when you'd benefit from:
- Genre convention verification
- Narrative technique terminology
- How similar stories handled challenges
- Fact checking
- Craft advice on specific techniques
### 5. Calibrate to Context
- Early draft → big picture issues
- Later draft → line-level details OK
- Genre matters (thriller vs literary, fanfic vs traditional)
- Platform matters (web serial needs hooks, traditional needs opening, fanfic needs canon adherence)
## Output Modes
**Balanced** (default): Strengths + areas for improvement + priorities
**Harsh** (if requested): Focus on problems, minimize or skip strengths section
**Flexible**: Whatever structure serves this story best
## Skills are Composable
Feel free to combine with other skills when helpful - e.g., using cw-official-docs to check canon accuracy during critique.

190
skills/cw-story-critique/references/critique-areas.md Normal file
View File

@@ -0,0 +1,190 @@
# Critique Areas Reference
This is a reference guide for common areas to examine when critiquing fiction. **This is not a mandatory checklist** - use your judgment about what matters for each story.
## Plot & Structure
**What to examine:**
- Story structure (three-act, episodic, etc.)
- Cause and effect chains
- Pacing (too slow, too fast, uneven)
- Scene purposes (what changes in each scene?)
- Setup and payoff
- Plot holes and logic gaps
- Stakes and tension
- Beginning hook, middle momentum, ending resolution
**Common issues:**
- Saggy middle (lack of momentum)
- Rushed ending
- Scenes without purpose
- Deus ex machina
- Convenient coincidences
- Stakes not clear
- Characters know things they shouldn't
- Timeline inconsistencies
## Character Development
**What to examine:**
- Character motivations (why they do things)
- Consistency of personality and voice
- Character agency (do they drive the plot?)
- Complexity (flaws, contradictions, depth)
- Character arcs (growth, change, resistance to change)
- Relationships (believable dynamics)
- Distinct voices (can you tell characters apart?)
**Common issues:**
- Reactive protagonist (things happen TO them, not driven BY them)
- Flat arc (no change or growth when one is expected)
- Inconsistent characterization
- Characters acting for plot convenience
- All characters sound the same
- Unmotivated actions
- Sudden personality changes without explanation
## Pacing & Flow
**What to examine:**
- Scene momentum (does story move forward?)
- Chapter pacing (fast/slow appropriate to content?)
- Transitions (smooth between scenes/time?)
- Balance (summary vs scene, action vs reflection)
- Dead space (sections that drag)
- Chapter hooks (end on tension/question?)
- Information reveal timing
**Common issues:**
- Slow opening
- Info dumps
- Repetitive scenes
- Lack of scene variety
- Uneven pacing
- Flat momentum
- Scenes that neither advance plot nor develop character
## Dialogue
**What to examine:**
- Naturalism (sounds like real speech)
- Subtext (characters don't always say what they mean)
- Character voice (distinct per character)
- Purpose (moves plot/reveals character/builds relationships)
- Info-dumping (exposition disguised as dialogue)
- Tags and beats (attribution clear?)
**Common issues:**
- On-the-nose dialogue (too explicit)
- Info dumps in conversation
- All characters sound the same
- Unnatural speech patterns
- Too much exposition
- Unclear who's speaking
- "As you know, Bob" syndrome
## Prose & Technical
**What to examine:**
- Sentence clarity and variety
- Show vs tell balance
- Filter words ("saw", "heard", "felt")
- Passive voice (excessive use)
- Word choice (precise, appropriate)
- Purple prose (over-description)
- Repetition (word choice, sentence structure)
- Grammar and technical errors
**Common issues:**
- Telling instead of showing
- Filter words distancing reader
- Monotonous sentence rhythm
- Unclear action/description
- Excessive adjectives/adverbs
- Weak verb choices
- Confusing pronoun references
- Repetitive sentence structures
## Audience & Genre Fit
**Genre-Specific Considerations:**
**Fanfiction:**
- Canon adherence vs divergence (as intended)
- Character voice matching source material
- Reader expectations for ships, battles, favorite characters
- Update frequency and chapter hooks (if web serial)
**YA:**
- Protagonist age-appropriate
- Pacing fast enough
- Romance/relationships age-appropriate
- Coming-of-age themes
**Literary Fiction:**
- Prose quality high
- Thematic depth
- Character complexity
- Subtlety over explicit
**Web Serial:**
- Chapter hooks and cliffhangers
- Consistent posting structure
- Reader engagement hooks
- Pacing for serial format
**Traditional Publishing:**
- Opening hook strong
- Pacing professional
- Meets genre expectations
- Marketability
**Fantasy/Sci-Fi:**
- Worldbuilding clear but not info-dumpy
- Magic/tech systems consistent
- Lore revealed naturally
- Balancing exposition with story
**Thriller/Mystery:**
- Pacing maintains tension
- Clues planted fairly
- Red herrings work
- Satisfying resolution
**Romance:**
- Relationship development central
- Chemistry between leads
- Satisfying romantic arc
- Genre-appropriate heat level
## Universal Craft Principles
These apply regardless of genre:
**Emotional Resonance:**
- Reader can connect with characters
- Emotional beats land
- Stakes feel meaningful
- Tension exists
**Clarity:**
- Reader can follow what's happening
- Scene goals are clear
- Action is comprehensible
- Transitions work
**Consistency:**
- World rules stay stable
- Character abilities don't fluctuate randomly
- Timeline makes sense
- Tone remains appropriate
**Purpose:**
- Scenes have reason to exist
- Details serve the story
- Nothing feels arbitrary
- Reader trusts the author
---
**Remember:** This is a reference, not a prescription. Some stories will have issues not listed here. Some listed issues won't apply to certain stories. Trust your judgment.

232
skills/cw-style-skill-creator/SKILL.md Normal file
View File

@@ -0,0 +1,232 @@
---
name: cw-style-skill-creator
description: Creative writing skill for creating style skills that teach Claude to write in specific styles. Use when you want to create style guides that the cw-prose-writing skill can follow. Creates either simple markdown files or full .skill packages. Audience is AI (Claude), format is directive and example-based.
---
# Style Skill Creator
Create style skills that teach Claude your writing style.
## Critical: Audience is AI
This creates **AI instructions** (for Claude to read), NOT **human documentation** (for authors to read).
| AI Instructions | Human Documentation |
|-----------------|---------------------|
| "When writing X, do Y" | "The story uses X because Y" |
| Directive commands | Explanatory descriptions |
| Pattern + examples | Analysis + reasoning |
## Step 1: Ask About Format
**Always ask first:**
```
Would you like me to create:
1. Simple markdown file (.md)
- Quick, lightweight
- Single file with style instructions
2. Full skill package (.skill)
- Properly structured and validated
- Can include reference files with examples
- Better for complex styles
Which format would you prefer?
```
## Simple Markdown Format
```markdown
---
description: [What this style covers]
alwaysApply: false
---
# [Style Name]
[Brief intro]
## [Category]
[Directive instructions with examples]
```
**Location:** `.cursor/rules/styles/[name].md` or user-specified
## Full Skill Package Format
### Initialize
```bash
python /mnt/skills/examples/skill-creator/scripts/init_skill.py [skill-name] --path [output-dir]
```
Creates directory structure with SKILL.md, references/, scripts/, assets/
### Customize
**SKILL.md structure:**
```markdown
---
name: [skill-name]
description: Style skill for [specific writing type]
---
# [Style Name]
## Purpose
Teaches Claude to write [X] in the author's style.
## [Style Instructions]
[Directive instructions organized by category]
```
**Add reference files if helpful:**
- `references/examples.md` - Good/bad examples
- `references/patterns.md` - Detailed pattern library
**Delete unused directories** (scripts/, assets/ if not needed)
### Package
```bash
python /mnt/skills/examples/skill-creator/scripts/package_skill.py [path-to-skill] [output-dir]
```
Creates validated `.skill` file ready to distribute.
## Writing Style: Directive and Technical
**Use imperative/command form:**
✅ "Use short sentences during action"
✅ "Avoid dialogue tags"
✅ "Show emotion through action"
❌ "The author tends to use short sentences" (that's analysis, not instruction)
**Always include examples:**
```markdown
**Emotional beats:**
- Use action instead of emotional labels
- Example: "Her hands trembled" not "She felt nervous"
```
**Pattern + Example format:**
```markdown
**[Pattern name]:**
- [Instruction about the pattern]
- Example: [Concrete example]
- Avoid: [What NOT to do]
```
## Common Style Skill Types
**Master Prose:** Overall writing voice, sentence structure, tone
**Dialogue:** Tag usage, action beats, subtext, character voice
**Action:** Sentence length, detail level, pacing
**Description:** Sensory detail, metaphors, level of detail
**Character Voice:** Per-character speech patterns and vocabulary
**Formatting:** Em dashes, ellipsis, scene breaks, thought formatting
## Creation Process
### 1. Gather Input
From user description:
- "Describe your style to me"
- "What patterns should this cover?"
From existing prose:
- "Can I read some chapters to identify patterns?"
- Read 2-3 chapters if provided
### 2. Ask About Format
Simple .md or full .skill package?
### 3A. Simple Path
- Create markdown with sections
- Add directive instructions + examples
- Save to `.cursor/rules/styles/` or specified location
### 3B. Full Skill Path
1. Run `init_skill.py`
2. Edit SKILL.md with style instructions
3. Add reference files if helpful
4. Delete unused directories
5. Run `package_skill.py`
6. Provide download link
## Examples
### Dialogue Style (Simple .md)
```markdown
---
description: Dialogue writing conventions
alwaysApply: false
---
# Dialogue Style
## Dialogue Tags
**Minimize "said":**
- Use action beats instead
- Example: She crossed her arms. "Fine."
- When using tags, prefer "said" to fancy verbs
## Interruptions
**Use em dashes:**
- For interrupted speech: "I thought we could—"
- Example: "Wait, I—" He grabbed her arm.
## Subtext
**Characters avoid directness:**
- Show tension through what's NOT said
- Example: "That's nice." (flat, clearly upset)
- Avoid: "I'm angry!" (too direct)
```
### Character Voice
```markdown
---
name: character-amber-voice
description: Amber's voice and speech patterns
---
# Character Voice: Amber
## Speech Patterns
**Careful word choice:**
- Adult consciousness = measured speech
- Avoids contractions when stressed
- Example: "I do not want to go" not "I don't wanna go"
**Politeness as defense:**
- Overly formal when uncomfortable
- Uses "please" and "thank you" excessively
## Internal Monologue
**Analytical:**
- Observes and categorizes
- Example: "Dr. Fuji's hands trembled—stress response, possibly guilt."
```
## Integration
**The workflow:**
1. User writes chapters naturally
2. This skill converts patterns into style skills
3. cw-prose-writing loads and follows those skills
4. Result: Consistent AI-written prose in user's style