Initial commit

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

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

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.

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

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.