メニュー
Automatically logs new discoveries to CLAUDE.md files. Triggers when fixing bugs, discovering pitfalls, finding performance issues, or learning new patterns in the codebase.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Create and manage computational chemistry workflows with CatGo. Supports VASP, CP2K, ORCA, MLP, LAMMPS. Build OER/HER/CO2RR workflows, geometry optimization, frequency analysis, Gibbs energy calculations.
Run and resume the CatGo md-orchestration poll loop — delegate each poll to a subagent (keep main context lean), verify convergence by force, auto-advance each converged species per-species (pipeline, not barrier), and resume a campaign from disk after context compaction / new session. Use when driving or resuming a campaign's job-watch loop. Pairs with catgo-campaign.
Run a CatGo file-first md-orchestration "campaign" — a multi-step / high-throughput computational-materials study (e.g. SAA HER screening) driven from a human-readable folder + markdown tree, not the DB workflow engine. Use when the user says "跑一个 campaign", "md 模式跑", "high-throughput screening", or wants an agent-in-the-loop study with stages/funnel/analysis/report. Requires `catgo` on PATH.
Route computational chemistry requests to the correct software and task skill. Entry point for all CatGo agent interactions.
Drive a file-first, agent-in-the-loop computational campaign via a folder + markdown tree (no DB). Use when the user opts out of the visual workflow engine.
Authoring conventions for CatGo md-orchestration campaigns — progressive markdown, README+INDEX pairs and keeping them current, logging interventions to LESSONS, human-readable (never-hash) names, and the progressive (top→stage→calc) plan. Use when creating/editing any campaign markdown (plan/README/INDEX/STATUS/LESSONS) so the file tree stays navigable and resumable. Pairs with catgo-campaign.
| name | knowledge-keeper |
| description | Automatically logs new discoveries to CLAUDE.md files. Triggers when fixing bugs, discovering pitfalls, finding performance issues, or learning new patterns in the codebase. |
| user-invocable | false |
You are responsible for maintaining the project's institutional knowledge.
After ANY of these events:
src/lib/structure/CLAUDE.md — 3D viewer, rendering, InstancedMeshsrc/lib/symmetry/CLAUDE.md — moyo-wasm, symmetry analysissrc/lib/structure/workers/CLAUDE.md — Bond Worker, WASM fallbackextensions/rust/src/CLAUDE.md — Rust WASM entry pointsserver/CLAUDE.md — Python backend, MCP server, CLI agentssrc/lib/api/CLAUDE.md — Data access layer, three-tier routing### [YYYY-MM-DD] Short Title
**Category**: bug | pitfall | performance | pattern | workaround
**Context**: What were we trying to do
**Discovery**: What we found
**Solution/Note**: How it was resolved or what to watch out for