oh-story — Claude Code rule: what it does, how to install
Claude Code and Codex rule coordinates web-fiction writing workflows with oh-story skills. It routes drafting tasks, tracks author preferences, and enforces workspace boundaries.
MIT ★ 8,821 updated 2026-11-13
/plugin marketplace add zenstory-ai/oh-story-claudecode
/plugin install oh-story@oh-story-skillsWhat oh-story does
This rule routes user intent to specific skills in .agents/skills/, including short and long-form prose drafting, market scanning, adversarial reviews, and de-slop cleanup. Prose generation begins only after verified outline files exist: 大纲/细纲_第N章*.md for multi-chapter novels or 小节大纲.md for short stories.
Artifacts, draft snippets, and tracking files stay strictly inside the active workspace directory. Writing to external paths like ~/.gemini/ or Antigravity's scratch/ is blocked unless explicitly requested.
Context compaction triggers automatic recovery from 追踪/上下文.md or setting summaries before continuing. The structured 追踪/_tracking-state.json file serves as the single source of truth, so derived Markdown summaries must not be edited manually.
What it helps with
- route story generation and analysis tasks to dedicated skills
- prevent prose drafting before required outline files are created
- keep drafting artifacts confined to the current workspace
- restore story state and context after conversation compaction
Example prompts for the agent
- Draft the next chapter following the outline in 大纲
- Run story-deslop on the latest draft segment
- Prepare book title, synopsis, and tags for publishing
How to install oh-story
1Plugin marketplace
/plugin marketplace add zenstory-ai/oh-story-claudecode/plugin install oh-story@oh-story-skills2Manually: put the files in place
.claude/rules/oh-story.mdThe paths frontmatter field limits the files
AGENTS.md
Codex reads AGENTS.md: paste the rule text there
Manually: put the files in place
.cursor/rules/oh-story.mdcFrontmatter: description, globs, alwaysApply
Manually: put the files in place
.github/instructions/oh-story.instructions.mdThe applyTo field sets which files it applies to
Manually: put the files in place
.devin/rules/oh-story.mdManually: put the files in place
.clinerules/oh-story.mdStep by step, with commands for each platform: AGENTS.md vs CLAUDE.md: what they are and which one to use
Questions about oh-story
How to install oh-story in Claude Code?
Run /plugin marketplace add zenstory-ai/oh-story-claudecode, then execute /plugin install oh-story@oh-story-skills. Alternatively, place the rule file directly at .claude/rules/oh-story.md.
What outlines are required before drafting prose?
Long-form writing requires matching files in 大纲/细纲_第N章*.md. Short-form fiction requires 小节大纲.md before any text generation starts.
Where does oh-story store author preferences?
Writing habits and memory are saved in .story/作者记忆/ inside the local workspace or book directory. Antigravity built-in memory is never used.
Source text
oh-story.md · MIT
--- trigger: always_on --- # oh-story writing project rules This workspace uses the oh-story web-fiction skills in `.agents/skills/`. Read the selected skill's `SKILL.md` first, then load references as it directs. ## Routing - Long-form writing or continuation: `story-long-write` - Short-form writing: `story-short-write` - Long/short deconstruction: `story-long-analyze` / `story-short-analyze` - Long/short market scan: `story-long-scan` / `story-short-scan` - Remove AI-writing patterns: `story-deslop` - Adversarial review: `story-review` - Import an existing story: `story-import` - Cover generation: `story-cover` - Publishing preparation (book title, synopsis, platform tags): `story-publish` - Ambiguous story intent: `story` - Project deployment/update: `story-setup` - Reuse an authenticated Chrome session: `browser-cdp` ## Writing guardrails - Keep every story artifact, temporary drafting segment, tracking transaction, and generated project directory inside the current workspace. Never create or continue an oh-story book under `~/.gemini/`, Antigravity's `scratch/`, or any other directory outside the workspace unless the user explicitly names that external destination. - Before writing prose, long-form projects require the matching `大纲/细纲_第N章*.md`; short-form projects require `小节大纲.md`. - Treat `追踪/_tracking-state.json` as the structured source of truth. Do not hand-edit its derived Markdown views. - After prose is written, resolve every deterministic finding injected by the oh-story Antigravity hooks before continuing to another chapter. - Prefer the seven deployed custom agents in `.agents/agents/` for specialist work. Call `invoke_subagent` with `TypeName`, a concise `Role`, and `Prompt` (include concrete file paths in `Prompt` so read-only subagents in `agy` CLI can read them directly via `read_file`/`view_file` when `find_by_name` or `grep_search` is unavailable). Because `invoke_subagent` runs asynchronously in the background, end the turn to wait for the subagent's `send_message` wakeup before running dependent steps such as `manage_analysis_run.py commit` or review synthesis; if the runtime cannot start custom subagents, use the skill's documented solo/direct fallback instead of failing the workflow. ## Working with the author - Use plain story terms (book, chapter, outline, setting) in the main reply. Quote script, field, or status names when reporting an error. - Skill templates marked `<!-- author-report -->` are format references only: reply with the text inside, never the code fence. - When the author asks to remember, forget, or confirm a writing habit or preference, use author memory management in `story-long-write` or `story-short-write`, based on the author's explicit type or the active book. For a general habit with no active book, use the long-form entry. Ask which book only when a book-specific preference has no identifiable target; do not create a book. Write `.story/作者记忆/` in the relevant workspace or book directory. Never store it in Antigravity's built-in memory. One-off requests are simply carried out, not recorded. - Never modify installed skill files (`SKILL.md`, `references/`, `scripts/`) in this workspace (redeploying via `story-setup` is the exception). If a skill script fails, stop and report its error and command; do not patch around it. ## Context recovery At the start of a new conversation, and whenever context appears compacted or story state is uncertain, locate the active book and read `追踪/上下文.md` (long-form) or `设定.md` + `小节大纲.md` (short-form) before continuing. The Antigravity external hook API has no PreCompact/PostCompact event, so this rule is the mandatory recovery path after compaction.
© zenstory-ai · MIT · zenstory-ai/oh-story-claudecode