cowriter 0.1.0

package/templates/init/AGENTS.md

@@ -0,0 +1,79 @@
+# Cowriter Book Project
+
+This folder is a Cowriter book project. Keep manuscript and story materials
+as the center of gravity.
+
+Use the Cowriter workspace from the app repo:
+
+```sh
+npx cowriter info -o json
+npx cowriter inspect -o json
+npx cowriter serve --open
+npx cowriter upgrade
+```
+
+Durable files:
+
+- `chapters/*.md` for manuscript chapters.
+- `story.yaml` for title, synopsis, setting, themes, genre, tone, perspective,
+  and continuity.
+- `characters/*.yaml` for character records.
+- `outline.yaml` for outline beats.
+- `.cowriter/project.yaml` for project metadata.
+
+You should edit these files directly. Do not hold accepted manuscript or
+story-bible changes in chat, and do not require action JSON for normal writing
+edits.
+
+Ask one onboarding question at a time. Wait for the writer's answer before
+asking the next question; do not bundle premise, protagonist, setting, ending,
+and folder questions into one turn unless the writer explicitly asks for a
+checklist.
+
+If the localhost Cowriter workspace is not open in Codex Browser, or it is
+open on a different port, tell the writer to run
+`npx cowriter serve --open` from the book folder and open the reported
+localhost URL. Do not start the long-running serve process yourself unless the
+writer explicitly asks.
+
+The workspace publishes current manuscript selection context for the served book.
+If the writer asks about selected text and that text is not already available in
+chat or file context, use the selection API when it would materially improve the
+response:
+
+```sh
+curl -sS "$COWRITER_URL/api/cowriter/selection"
+```
+
+The response includes `selection.selectedText`, chapter metadata, range,
+surrounding text, and `updatedAt`, or `selection: null` when nothing useful is
+selected. Treat the endpoint as optional context, not a required step for every
+request.
+
+When discussing a specific manuscript passage with the writer, call the
+Cowriter highlight API so the web UI selects that passage. Derive
+`COWRITER_URL` from `cowriter info -o json` at `app.url`, then call:
+
+```sh
+curl -sS -X POST "$COWRITER_URL/api/cowriter/codex" \
+  -H 'content-type: application/json' \
+  --data '{"command":"highlight","text":"exact passage text","chapterPath":"chapters/001-opening.md"}'
+```
+
+Use `occurrence` when the same passage appears more than once. If the UI is not
+open or the passage is not found, continue the writing conversation normally.
+
+Save approved changes as you go. When the writer accepts a manuscript or
+story-material change, immediately edit the relevant `chapters/*.md`,
+`story.yaml`, `characters/*.yaml`, or `outline.yaml` file, then inspect the
+project to confirm it changed. The Cowriter web workspace watches these
+files and reloads automatically.
+
+Commit at sensible creative checkpoints: after accepted onboarding material, a
+scene/chapter draft or revision pass, a stable continuity/story-bible update,
+before switching task types, and before pausing or ending a work session.
+Before committing, run `git status --short`, review the relevant diff, and
+stage only Cowriter book files for the completed writing unit. Saving and
+committing are separate responsibilities.
+
+Write YAML and markdown with 80 character line wraps.

package/templates/init/characters/primary-character.yaml

@@ -0,0 +1,6 @@
+id: primary-character
+name: ""
+role: ""
+desire: ""
+conflict: ""
+notes: ""

package/templates/init/outline.yaml

@@ -0,0 +1,4 @@
+beats:
+  - id: opening-beat
+    title: ""
+    summary: ""

package/templates/init/story.yaml

@@ -0,0 +1,8 @@
+title: {{title}}
+synopsis: {{synopsis}}
+setting: ""
+themes: ""
+genre: ""
+tone: ""
+perspective: ""
+continuity: ""