Menu
実 mulmoclaude を叩く wiki カテゴリ (markdown image coverage) の総合テストを実行する。`yarn dev` が起動済みであることが前提。
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
| name | e2e-live-wiki |
| description | 実 mulmoclaude を叩く wiki カテゴリ (markdown image coverage) の総合テストを実行する。`yarn dev` が起動済みであることが前提。 |
yarn dev を別ターミナルで起動済み(http://localhost:5173 が応答する)yarn test:e2e:live:wiki
HEADED=1 yarn test:e2e:live:wiki
issue #1011 の Stage C 実装。data/wiki/pages/<slug>.md の本文に書ける各画像参照形式が、SPA の v-html サーフェス上で実際に decode されるか (naturalWidth > 0) を検証する。
<img src="../../../artifacts/images/...">(Stage A — markdown rewriter が raw <img> を扱えるか)(常に動くべきパスのリグレッション)<picture><source><img></picture>(Stage B 依存 — 現在は test.fixme でスキップ)<img src="/wrong/prefix/artifacts/images/..."> が useGlobalImageErrorRepair で復活するかdata/wiki/sources/<file> への相対参照playwright-report-live/wiki/index.html(カテゴリ専用サブディレクトリに出力)npx playwright show-trace test-results-live/wiki/<spec>/trace.zipplans/done/feat-markdown-image-coverage.md §自動テスト(e2e-live)rewriteHtmlImageRefs を <source> / <video poster> 対応に拡張) が先に必要。Schedule, list, edit, or remove a recurring agent task (cron / interval) in `config/scheduler/tasks.json`. Use for cross-collection digests, notifications, or any standalone recurring prompt ("毎朝7時に天気", "every weekday 8am check email", "schedule a weekly cleanup"), or to list/stop automations. EXCEPTION — do NOT create a task here to keep ONE collection's records fresh (e.g. "update the stock-quotes daily", "refresh these quotes every morning", "re-poll these URLs"): instead add an `ingest` block with `kind: "agent"` to THAT collection's own `schema.json` (it self-refreshes on schedule and from its Refresh button; syntax in `config/helps/collection-skills.md` → "Scheduled agent refresh"). Read this skill body in full before writing `tasks.json` — the entry format is structured, not free-form.
Turn MulmoClaude work into a Zenn tech article (markdown) inside the workspace. On first use it sets up a Zenn project at `github/zenn/` — clone an existing GitHub repo or `zenn init` a fresh one, idempotent and skipped when already initialized — then writes articles to `github/zenn/articles/<slug>.md` tagged with the `MulmoClaude` topic. Use when the user says "Zenn にまとめて", "この作業を記事にして", "share this on Zenn", "Zenn 始めたい", or "Zenn のリポを用意して".
Personal recipe book — save / read / update / delete cooking recipes as markdown files under `data/cooking/recipes/`, with a `README.md` index that lists every recipe. Use when the user asks to remember a recipe, look one up, or refine one.
Personal book journal — track books the user wants to read or has read, prompt for impressions when they finish one, capture their words verbatim, and surface earlier reactions when they want to recall what they thought about a topic.
Save, edit, list, or delete a Claude Code skill in this workspace. Use when the user wants to turn a workflow into a reusable skill ("skill 化して", "save this as a skill"), modify or remove one, or list what's registered. Writes one markdown file per skill at `data/skills/<slug>/SKILL.md`; a workspace-side hook mirrors it into `.claude/skills/<slug>/SKILL.md` so Claude Code picks it up.
On-demand LLM-driven wiki review — find contradictions between pages, stale claims, and missing concepts (topics mentioned in index.md / log.md / sources but not yet captured as their own page). Read-only — never modifies the wiki. Use when the user asks to "review the wiki", "find contradictions", "what's stale in the wiki", or "what's missing". Sister of mc-wiki-health-check (structural lint).