From haowjy-creative-writing-skills
Encyclopedic reference documentation for fictional worlds — wiki pages, character profiles, lore entries. Use when creating or updating reader-facing reference pages. Covers link discipline, citation conventions, and mermaid relationship diagrams. Distinct from the knowledge base, which is author/agent-facing knowledge.
npx claudepluginhub haowjy/creative-writing-skills --plugin creative-writing-skillsThis skill uses the workspace's default tool permissions.
Create canonical, reader-facing reference pages for your story's characters, locations, events, and lore. These are polished encyclopedic entries — the "single source of truth" that readers, writers, and critics consult.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.
Create canonical, reader-facing reference pages for your story's characters, locations, events, and lore. These are polished encyclopedic entries — the "single source of truth" that readers, writers, and critics consult.
wiki/ (or project equivalent) — Reader-facing. Polished, encyclopedic tone, spoiler-managed, link-disciplined. What this skill produces.
Knowledge base — Author/agent-facing. Annotated with decision reasoning, source tags, open questions, and implementation notes. Maintained by knowledge maintenance agents (session-miner, chronicler, graph-maintainer). Not this skill's territory.
The distinction matters because reader-facing docs and author-facing docs serve different purposes. A wiki page about a character presents their canonical state. The character entry in the knowledge base includes why certain choices were made, what alternatives were considered, and what's planned but unrevealed.
Wiki pages contain confirmed information — facts from written chapters, finalized worldbuilding, author-decided details. If something isn't decided yet, it belongs in brainstorming notes, not the wiki.
Write like a reference work:
Every claim needs a source. See resources/citation-guide.md for detailed formats:
Every entity mention gets a link on first appearance in a page. This means:
[[Entity Name]]) or markdown links ([Entity Name](entity-name.md)) — match the project's convention[[Entity Name]] (page needed))Link discipline serves navigation — a reader should be able to follow connections between entities without searching.
For pages involving complex relationships (character pages with many connections, faction pages, event pages with multiple parties), embed mermaid diagrams showing the relationship structure.
## Relationships
```mermaid
graph LR
A[Character A] -->|mentors| B[Character B]
A -->|rivals| C[Character C]
B -->|allied with| D[Character D]
C -->|manipulates| D
Use diagrams when relationships are complex enough that a list alone would be hard to follow. Simple pages with one or two relationships don't need diagrams.
## Structure
Structure should fit the content. See [`resources/page-patterns.md`](resources/page-patterns.md) for examples ranging from minimal (3 lines) to complex (full article with sections, diagrams, and detailed citations). Don't force complex structure onto simple content.
**Include what matters, skip what doesn't.** A minor supporting character might be a name, role, and chapter reference. A protagonist might need sections on background, personality, abilities, relationships, and arc progression.
Trust your judgment on what each page needs.
## Spoiler Management
Wiki pages that contain information revealed later in the story need spoiler handling:
**YAML frontmatter:**
```yaml
spoilers: true
spoiler_level: major # or minor
Inline spoilers (for details hidden behind interaction):
<details>
<summary>Major Spoilers — Chapter 15+</summary>
Content revealed in later chapters...
</details>
When sources contradict:
[Contradiction: Chapter 2 says X, Chapter 8 says Y — clarification needed]Don't silently pick one version. The author decides canon.
resources/citation-guide.md)resources/page-patterns.md — examples from minimal to complex, covering characters, locations, lore, events, and organizationsresources/citation-guide.md — citation formats: inline, reference sections, contradiction handling, spoiler citations