CLAUDE.md · diff

git:20261114.525f78f to git:20261115.7a8a990

2 added, 2 removed. Audit A to A.

What this update changes in the checks

No check changed: every fixed check gives the same answer before and after this update.

A tripped check is a label, not a verdict: read the matched text and the lines below. This week's updates that newly trip a check.

- # Claude Code Instructions for zenn-content
+ # Claude Code Instructions for the writing repo
## Project Overview
This repository contains published, author-voiced Zenn / Dev.to articles and note / Substack essays about
AI agents, Claude Code workflows, and LLM engineering. Study drafts without an author voice do not belong.
The repository is public; nothing load-bearing depends on a publishing platform remaining available.
## Publications index
README is a routing page, not an article list. The exhaustive generated index is `docs/PUBLICATIONS.md`.
- source: `articles/*.md` frontmatter, `scripts/schedule.json`, `scripts/corpus.yml`, `scripts/reading_paths.yml`
- generate after article / URL / essay / paper changes: `npm run generate:index`
- verify drift before handoff: `npm run check:index`
- do not hand-maintain article titles or counts in README / llms files
## Writing harness
Human-primary prose has one entrypoint, resident in this repository:
`.claude/skills/writing-ecosystem/SKILL.md` (the
review agents `review-structure` / `review-certainty` / `review-explanation` / `review-prose` / `review-conventions` / `prose-clarity-reviewer` /
`fact-checker` and the skills `quality-gate` / `session-theme-mining` live in `.claude/` too).
The author's writing values and principles live only in `.claude/rules/writing-principles.md` (the backbone).
Platform and repository values live only in `.claude/rules/publishing-channels.md`.
- For article work in another repository, add this repo with `claude --add-dir ~/MyAI_Lab/zenn-content`
+ For article work in another repository, add this repo with `claude --add-dir ~/MyAI_Lab/writing`
or start the session here.
Do not restate the backbone or the shared flow here. `writing-ecosystem` owns the procedure: the editorial
brief, review order, revision return conditions, and the boundary that excludes ADRs / memory / raw session
history from writing-time rules. Article direction comes from interviewing the author
(`.claude/skills/article-interview/`); outlines and plans for an article are written only after its brief.
The project output style `.claude/output-styles/zenn-writing.md` (selected in `.claude/settings.json`) governs how
Claude talks with the author, not article prose. For coding work such as `scripts/`, set `"outputStyle": "default"` in
`.claude/settings.local.json` (CLI: `/output-style default`).
## Channel and format boundaries
- Zenn: `articles/`; format and syntax are owned by `zenn-format`
- Dev.to: `articles-en/`; translation method is global `prose-translation`, platform conversion is `devto-translator`
- note: `note/`(note 初出の JA 正本と、Zenn 記事の原文転載。転載の正本は `articles/`)
- Substack EN translation: `substack/`
(frontmatter の有無は publishing-channels.md の Deterministic checks 列が持つ)
- note publishing and corpus mirroring: `note-publishing`
- Substack publishing and corpus mirroring: `substack-publishing`
- note daily queue and scheduling: `docs/note-pipeline.md`
- Zenn / Dev.to publishing pipeline: `publish-article`
Exact register, audience promise, review aspects, title limit, `published_at`, cadence, terminology, and
publish handoff are defined in `.claude/rules/publishing-channels.md`; do not duplicate their values here.
Drafting stays in the orchestrator. Review and acceptance follow `writing-ecosystem` (resident in
`.claude/skills/`) plus the local channel contract.
## Post-publication measurement
`article-stocktake` is project-local instrumentation. It collects and reports reception differences, then
stops. Human-side reception data lives in `scripts/metrics/snapshots.jsonl`: Zenn views and note
impressions / PV / likes are read from each platform's dashboard (`source: zenn_dash` / `note_dash`, one row
per article plus an `account` row), alongside the older Zenn / Dev.to API rows. Check this file before
claiming human reception is unmeasured; the row format and collection procedure belong to `article-stocktake`. It does not generate or rank themes and does not call `session-theme-mining` automatically.
## Verification and publishing
Pipeline details live in the scripts (`scripts/devto_crosspost.py --help`, `scripts/note_publish.py --help`) and the
publishing skills below; the schedule.json schema is `.claude/refs/schedule-schema.md`.
1. `/quality-gate <file>`
2. author publication GO
3. `/publish-article <file>` for Zenn / Dev.to, `note-publishing` for note, or `substack-publishing` for Substack
4. `npm run generate:index`
5. `npm run validate` and `npm run check:index`
If article, `schedule.json`, or generated-index changes are committed, remind the user to push. An unpushed
commit does not reach Zenn scheduling or the Dev.to cross-post job.
## Public-repository safety
Never commit personal file paths, API keys, credentials, unsanitized raw logs, or sensitive screenshots.