Loading...
Loading...
Automatically detects story settings (genres, time periods, themes) based on keywords and activates corresponding knowledge bases - works silently in the background to provide relevant writing guidance without user intervention
npx skill4agent add wordflowlab/novel-writer-skills setting-detectorTrigger words: 言情、爱情、恋爱、浪漫、感情线、关系弧、CP、甜文、虐文、
HE、BE、双洁、破镜重圆、先婚后爱、契约关系
Activate: templates/knowledge-base/genres/romance.mdTrigger words: 悬疑、推理、侦探、破案、谜团、线索、真相、凶手、犯罪、
密室、诡计、不在场证明、推理小说
Activate: templates/knowledge-base/genres/mystery.mdTrigger words: 历史、古代、朝代、考据、时代背景、历史小说、古言、
穿越、重生古代、架空历史、宫斗、宅斗
Activate: templates/knowledge-base/genres/historical.mdTrigger words: 复仇、报仇、打脸、爽文、逆袭、反击、重生复仇、
穿越复仇、系统、金手指、女主爽文、男主爽文
Activate: templates/knowledge-base/genres/revenge.mdTrigger words: 武侠、江湖、武功、侠客、门派、武学、剑客、
轻功、内功、武林、江湖恩仇、侠义
Activate: templates/knowledge-base/genres/wuxia.mdTrigger words: 1920、民国、军阀、北洋、穿越民国、二十年代、
民国时期、军阀混战
Activate: templates/knowledge-base/references/china-1920s/User: "I want to write a romance novel"
↓
[Detected keyword: "言情"]
↓
✓ Auto-loaded: romance.md
↓
AI Response: "Great! Let me help you create a romance novel.
According to romance genre conventions, we need to clarify several core elements...
(Automatically applies knowledge from romance.md)"User: "I want to write a romance revenge novel set in the 1920s"
↓
[Detected keywords: "1920", "言情", "复仇"]
↓
✓ Auto-loaded: romance.md
✓ Auto-loaded: revenge.md
✓ Auto-loaded: references/china-1920s/
↓
📚 Activated Knowledge Bases:
- genres/romance.md (Romance Novel Conventions)
- genres/revenge.md (Revenge Power Fantasy Techniques)
- references/china-1920s/ (1920s China Background)
↓
AI Response: "Excellent combination! This is romantic suspense + revenge + Republican-era background.
Based on the integration of these three genres, it is recommended...
(Applies content from all three knowledge bases simultaneously)"/constitution phase:
→ Activated: romance.md
→ Reminder: Romance novels require HEA/HFN ending commitment
/specify phase:
→ Activated: romance.md + revenge.md
→ Suggestion: Define relationship arc + revenge target
/plan phase:
→ Activated: All knowledge bases
→ Applied: Emotional rhythm points + slap-in-the-face rhythm + 1920s details
/write phase:
→ Activated: All knowledge bases
→ Real-time: Dialogue techniques + scene description + era atmosphere
/analyze phase:
→ Activated: All knowledge bases
→ Check: Romance conventions + revenge rationality + historical accuracy50 independent Skills × 40 lines per SKILL.md = 2000 tokens
Loads all Skills in every conversation1 detector Skill (this file): ~100 tokens
On-demand knowledge base loading:
- romance.md: ~520 tokens
- revenge.md: ~480 tokens
- china-1920s/: ~650 tokens
Total: 100 + 520 + 480 + 650 = ~1750 tokens
(Only loads relevant knowledge bases)"What knowledge bases are currently activated?"📚 Currently Activated Knowledge Bases:
✓ genres/romance.md - Romance Novel Creation Conventions
✓ genres/revenge.md - Revenge Power Fantasy Slap-in-the-Face Techniques
✓ references/china-1920s/ - 1920s China Reference Materials
Token consumption: Approximately 1650 tokens"Please load the romance and mystery knowledge bases"
"This story requires 1920s China reference materials"
"Activate the wuxia knowledge base""Deactivate the revenge knowledge base, this story does not involve revenge"/constitution【Automatically inserted into constitution】
## Genre-Specific Principles (Automatically added by setting-detector)
### Core Principles of Romance Novels
1. Relationship arc is the main plot
2. HEA/HFN ending is mandatory
3. Chemistry is authentic and believable
### Core Principles of Revenge Power Fantasy
1. Hatred must be deep and specific
2. Slap-in-the-face rhythm is progressive
3. Moral balance: Deserved punishment/specify【Automatic Prompt】
💡 Based on activated knowledge bases, it is recommended to define the following in the specifications:
【From romance.md】
- Relationship arc setting
- Emotional rhythm point planning
- HEA/HFN ending type
【From revenge.md】
- Source of hatred (specific crime)
- Golden finger setting
- Slap-in-the-face rhythm planning
【From china-1920s】
- Specific year (1920-1929)
- Geographical location (Beijing/Shanghai/Other)
- Social class setting/plan【Automatically Applied】
## Chapter Plan (Integrates 3 Knowledge Bases)
Chapters 1-5: Encounter and Establishment of Hatred
- [romance] Initial meeting scene (meet-cute)
- [revenge] Display deep hatred from past life/previous experience
- [1920s] Create atmosphere of the Republican era
Chapters 6-10: Relationship Heating Up and Minor Slap-in-the-Face
- [romance] Ambiguous period: Physical contact, emotional accumulation
- [revenge] First slap-in-the-face: Surprise of the enemy
- [1920s] Display clothing, etiquette, and social rules
.../write【Automatic Reminder Before Writing】
📋 Knowledge Bases Applied in This Chapter:
✓ romance.md - Dialogue Spark Techniques
→ Flirtatious dialogue: Challenge rather than comply
→ Body language: Eye contact, touch, distance
✓ revenge.md - Slap-in-the-Face Scene Satisfaction
→ Expectation → Reversal → Astonishment → Dominance
✓ 1920s - Era Details
→ Addresses: 大人、老爷、小姐
→ Scenes: Teahouses, foreign firms, concessions/analyze【Automatic Analysis】
## Genre Compliance Analysis
### Romance Novel Check (Based on romance.md)
- [x] Relationship arc is the main plot
- [x] Contains essential emotional rhythm points
- [ ] ⚠️ Missing first kiss scene (suggested in Chapter 15)
- [x] HEA ending commitment is clear
### Revenge Power Fantasy Check (Based on revenge.md)
- [x] Hatred is deep and specific
- [x] Slap-in-the-face frequency is reasonable (once every 5 chapters)
- [x] Protagonist's strength improvement is reasonable
### Historical Accuracy Check (Based on 1920s)
- [x] Era background is correct
- [ ] ⚠️ "Mobile phone" appears in Chapter 8 (inconsistent with the era)
- [x] Address system is correct| Category | Completed | Planned |
|---|---|---|
| Genre Knowledge | 5 | 10+ |
| Reference Materials | 1 | 20+ |
templates/knowledge-base/templates/knowledge-base/README.md# 1. Create file
touch templates/knowledge-base/genres/fantasy.md
# 2. Update README.md keyword mapping
fantasy:
keywords: [奇幻, 魔法, 世界构建, 魔法系统]
auto_load: genres/fantasy.md
# 3. Done! Next time user says "奇幻" it will automatically activate"I want to write a revenge story set in the Republican era after time travel"
↓
Identified: "民国" → 1920s China
"复仇" → revenge
"The female protagonist wants to take revenge after rebirth"
↓
Identified: "重生" + "报仇" → revenge (rebirth revenge)1st message: "I want to write a novel"
→ No knowledge bases activated (waiting for more information)
2nd message: "The protagonist is a detective"
→ Activates mystery.md
3rd message: "There's also a romantic subplot"
→ Additionally activates romance.md
→ Currently activated: mystery + romance (romantic suspense)User: "This is a wuxia novel, set in the jianghu, with martial arts"
↓
3 wuxia keywords detected, but only activates wuxia.md once"This is not a romance novel, please deactivate the romance knowledge base"
"This is a sci-fi novel, please activate the sci-fi knowledge base" (if available)Recommended practice:
User: "I want to write a revenge romance novel set in the Republican era"
Not recommended:
User: "I want to write a novel"
AI: "Okay"
User: "The protagonist's surname is Li"
AI: "Hmm"
(Only mentions the genre after 20 rounds of dialogue)"Are the currently activated knowledge bases still suitable?"✓ Good combinations:
- romance + mystery (romantic suspense)
- historical + romance (ancient romance)
- revenge + romance (revenge + romance)
⚠️ Difficult combinations:
- horror + romance (horror romance? Readers may not adapt)
- mystery + wuxia (detective wuxia, requires special design)
It's not impossible, but requires careful integration."1920s" → china-1920s
"Ancient times" → Specify a specific dynasty (e.g., "Tang Dynasty", "Ming Dynasty")1. User input → Extract keywords
2. Keywords → Map to knowledge bases (based on README.md)
3. Deduplication → Avoid repeated activation
4. Loading → Read corresponding .md files
5. Application → Continuously apply knowledge in subsequent dialoguesActivation status check: At the start of each conversation
Knowledge base content: Loaded on demand, cached in dialogue context
Update strategy: Re-read only when explicitly neededsetting-detector → Decides which knowledge to load
consistency-checker → Checks consistency based on activated knowledge bases
workflow-guide → Provides specific process guidance based on genre
genre-specific skills → Provides in-depth genre-specific techniques