@@ -0,0 +1,139 @@
1+---
2+name: add-new-comic
3+description: Use when the user wants to add, generate, render, or submit a new Clanker and the Dev comic/joke. Covers creating comic inbox seeds, running the generation job, reviewing generated specs/posts, and preparing changes for commit or PR.
4+allowed-tools: Read, Write, Edit, Bash
5+---
6+
7+# Add a New Clanker and the Dev Comic
8+
9+This repo is a Jekyll/GitHub Pages comic-strip blog. Comics are generated from small markdown seed files in `comic/inbox/`.
10+
11+Use this skill when a user asks to add a new comic, turn a joke into a strip, create an inbox item, run comic generation, or prepare a joke contribution.
12+
13+## Important project rules
14+
15+- Do not install Ruby gems locally.
16+- Local development runs through Docker with `./dev.sh`.
17+- Comic generation runs through `./job.sh`.
18+- Jekyll posts live in `_posts/`.
19+- Comic seeds start in `comic/inbox/` and move to `comic/done/` or `comic/failed/` after generation.
20+- Generated comic specs live in `comic/specs/`.
21+- The renderer is deterministic: `comic/render-comic.js` turns a JSON spec into an inline SVG post.
22+
23+## Standard workflow
24+
25+### 1. Turn the user's joke into an inbox seed
26+
27+Create a slug from the title or premise:
28+
29+```txt
30+comic/inbox/my-great-joke.md
31+```
32+
33+Use this seed format:
34+
35+```md
36+---
37+title: My Great Joke
38+credit: User / handle / inspiration
39+timestamp: YYYY-MM-DD
40+---
41+
42+1. Set up the premise.
43+2. Escalate the developer pain.
44+3. Let Clanker misunderstand or over-optimize something.
45+4. Land the punchline.
46+```
47+
48+Guidelines:
49+
50+- Keep each numbered beat short and comic-panel-friendly.
51+- Usually one numbered beat becomes one panel.
52+- Preserve the user’s core joke and credit.
53+- Prefer jokes about AI coding, terminals, burnout, yak shaving, refactors, CI, bots, editors, production incidents, or software absurdity.
54+- If the user provides only a rough idea, turn it into 3–5 clear beats.
55+
56+### 2. Run the comic generation job
57+
58+Run:
59+
60+```bash
61+./job.sh
62+```
63+
64+The job processes the first `*.md` file in `comic/inbox/` alphabetically.
65+
66+On success it creates/updates:
67+
68+```txt
69+comic/specs/<slug>.json
70+_posts/YYYY-MM-DD-<slug>.md
71+comic/done/<slug>.md
72+```
73+
74+On failure, the seed is moved to:
75+
76+```txt
77+comic/failed/<slug>.md
78+```
79+
80+### 3. Review generated files
81+
82+Check status and diff:
83+
84+```bash
85+git status
86+git diff
87+```
88+
89+Inspect the generated post in `_posts/` and the generated spec in `comic/specs/`.
90+
91+If the generation failed:
92+
93+1. Read the failed seed in `comic/failed/`.
94+2. Fix the issue or move it back to `comic/inbox/`.
95+3. Re-run `./job.sh`.
96+
97+### 4. Preview locally when useful
98+
99+Use Docker only:
100+
101+```bash
102+./dev.sh
103+```
104+
105+Then open:
106+
107+```txt
108+http://localhost:4000
109+```
110+
111+Do not install or run Bundler/Ruby gems locally outside Docker.
112+
113+### 5. Commit or prepare for PR
114+
115+If the user asks to commit, include the generated seed/spec/post:
116+
117+```bash
118+git add comic/done comic/specs _posts
119+git commit -m "Add <comic title> comic"
120+```
121+
122+If the user is contributing from a fork, remind them to open a pull request with their joke.
123+
124+## Optional direct chat-script path
125+
126+For dialogue-heavy strips, a chat script can be compiled directly:
127+
128+```bash
129+node comic/chat-to-spec.js my-strip.chat comic/specs/my-strip.json
130+node comic/render-comic.js comic/specs/my-strip.json
131+```
132+
133+Chat line format:
134+
135+```txt
136+dev->clanker: ship it? (curious/helpful) [screen-glow]
137+```
138+
139+Repeating a speaker starts a new panel; alternating speakers can share a panel as dialogue balloons.