story-setup: Infrastructure Deployment for Online Novel Writing Toolset

Phase 1: Detect Project Status

1. Check if the current directory has been deployed (

   .story-deployed

   exists)
   • If exists → Use AskUserQuestion to confirm whether to redeploy
2. Check if there is a book title directory (a directory containing the

   追踪/

   subdirectory, or a user-defined structure)
   • If exists → Identify as a long-form project and display current project information
   • If not exists → Identify as a new project or short-form project
3. Check if

   .claude/settings.local.json

   exists
   • If exists → Read existing configuration for subsequent merging
   • If not exists → Create a new file later
4. Check if

   .active-book

   file exists
   • If exists → Display current active book title
   • If not exists → Skip

Phase 2: Deploy Infrastructure

2.1 Deploy CLAUDE.md

• Read

  skills/story-setup/references/templates/CLAUDE.md.tmpl

• Replace placeholders (see "Template Placeholders" section below)
• Write to the project root directory

  CLAUDE.md

  (if already exists, handle according to "CLAUDE.md Merging Strategy")

2.2 Deploy Hooks

• Read all

  .sh

  files under

  skills/story-setup/references/templates/hooks/

• Copy to the user's project

  .claude/hooks/

  directory
• Ensure scripts have execution permissions (chmod +x)

2.3 Deploy Rules

• Read all

  .md

  files under

  skills/story-setup/references/templates/rules/

• Copy to the user's project

  .claude/rules/

  directory

2.4 Deploy Agents

• Read all

  .md

  files under

  skills/story-setup/references/templates/agents/

• Copy to the user's project

  .claude/agents/

  directory

2.5 Deploy Session State Template

• Read

  skills/story-setup/references/templates/上下文.md.tmpl

• If there is a book title directory, copy it to

  {Book Title}/追踪/

2.6 Merge Hooks Registration to settings.local.json

• Read

  skills/story-setup/references/templates/settings-hooks.json

• Read the user's project

  .claude/settings.local.json

  (if exists)
• Merge hooks configuration (handle according to "settings-hooks.json Merging Algorithm")
• Write to

  .claude/settings.local.json

2.7 Create Deployment Marker

• Create

  .story-deployed

  file (sentinel file)
• Write two lines: First line

  deployed_at: <date -u +"%Y-%m-%dT%H:%M:%SZ">

  , second line

  agents_version: 2

• This file is used by session-start.sh and writing skills to detect deployment status and avoid repeated prompts
• If

  .story-deployed

  exists but has no

  agents_version

  or version is 1, prompt the user to re-run story-setup to update Agent

Phase 3: Verify Installation

1. Verify hooks registration:
   • Check if the hooks field in

     .claude/settings.local.json

     is correct
   • Check if scripts under

     .claude/hooks/

     exist and have execution permissions
2. Verify rules path:
   • Check if rule files under

     .claude/rules/

     exist and contain

     paths

     frontmatter
3. Verify agents:
   • Check if agent definition files under

     .claude/agents/

     exist
4. Verify deployment marker:
   • Check if

     .story-deployed

     exists and contains a timestamp
5. Output installation report:
   • List all deployed files
   • List notes (e.g., existing configurations have been merged)
   • Prompt the user to start using

     /story-long-write

     or

     /story-short-write

Template Placeholders

{Project Name}

{Book Title}

{Project Name}

CLAUDE.md Merging Strategy

1. Read the user's existing CLAUDE.md and split into a section map by

   ##

   headings
2. Read the template CLAUDE.md.tmpl and split it the same way
3. Standard sections in the template (Skill Routing Table, File Structure, Collaboration Rules, Context Recovery, Language) overwrite the user's sections with the same name
4. Unique sections of the user (custom content) remain unchanged
5. For unknown conflicts, use AskUserQuestion to let the user choose which version to keep

settings-hooks.json Merging Algorithm

1. Read the user's existing

   .claude/settings.local.json

   (if exists) and extract the hooks part
2. Read the

   settings-hooks.json

   template and extract the hooks to be registered
3. For each hook event (SessionStart, PreToolUse, etc.):
   • Existing hook commands from the user → Keep, do not add duplicates
   • New hook commands from the template → Append to the hooks array of the corresponding event
   • Other unique configurations from the user (permissions, env, etc.) → Fully retain
4. Write the merged complete settings.local.json

Redeployment

• .story-deployed

  does not exist → Fresh installation, execute all steps in Phase 2

• .story-deployed

  exists and

  agents_version: 2

  → Prompt that deployment is already done, use AskUserQuestion to confirm whether to redeploy

• .story-deployed

  exists but has no

  agents_version

  or version < 2 → Prompt that an update is needed, re-execute Phase 2 to overwrite agents/hooks/rules, and use merging strategy for CLAUDE.md and settings.local.json

Reference Materials