← ClaudeAtlas

grizzly-cardslisted

Create, update, or bootstrap the project codex (chapter cards, arc cards, character cards). Use when a chapter is finished or edited, when continuity cards need updating, when the user asks to card a chapter, or to onboard an existing manuscript into the codex.
HarishDvs/Grizzly · ★ 1 · AI & Automation · score 74
Install: claude install-skill HarishDvs/Grizzly
# Grizzly Cards — The Codex Maker The codex is the project's memory: extractive cards that let any session answer continuity and planning questions without reloading the manuscript. Templates live in `templates/codex/`. The index (`codex/_Index.md`) is the orientation map; keep it current with every card change. ## The two laws 1. **Extractive, never interpretive.** Cards record what is on the page: events, names, counts, objects, exact preserve-lines. Never motives the text doesn't state, never quality judgments, never speculation. If the author wants analysis, that's a review, not a card. 2. **The chapter file is the source of truth.** A card that disagrees with its chapter is a bug. Fix the card, never the chapter. ## Creating a chapter card 1. Read the full chapter text once. 2. Fill the chapter-card template: frontmatter, one-line logline, events in order (numbered; include the concrete details continuity will later depend on: counts, injuries, promises, objects changing hands), threads opened, threads paid, adjacency links. 3. Ask the author if any lines in this chapter should be marked **preserve** (untouchable verbatim). Copy them into the card exactly. 4. Add the chapter row to `_Index.md`, and update any arc card whose spine this chapter extends. 5. New named characters get a character card (or a stub with first-appearance). ## Updating (the drift rule) When a chapter's events change in any session, its card updates **in the same se