菜单
Compatibility pointer for the Claude Code AITP v5 adapter; active templates live under deploy/templates/claude-code.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use after AITP v5 routing has claimed a theoretical-physics task; continue the work through typed records, validation gates, and summary regeneration instead of ad hoc notes.
First-run setup assistant for the AITP Research Protocol Kimi Code plugin: detect setup mode, ask for repo/topics paths, persist configuration, and explain when to reload Kimi Code.
HIGHEST PRIORITY - Use for ANY theoretical-physics research, topic continuation, exploratory physics discussion, old-knowledge Q&A tied to project topics, prior topic progress/status inquiries, idea steering, paper learning, derivation work, validation planning, or study of physical systems. Classify request intensity before deciding read-only or write-capable flow.
Continue an AITP v5 theoretical-physics topic through typed claims, source provenance, artifacts, evidence, validation gates, human checkpoints, and trust-controlled memory.
Enter the local AITP v5 research protocol from Codex for theoretical-physics work, topic continuation, prior progress checks, paper reading, derivations, validation, and trust-controlled research memory.
Compatibility pointer for the Codex AITP v5 runtime; canonical Codex skills and plugin assets live under deploy/codex and plugins/aitp-research-protocol.
| name | aitp-runtime |
| description | Compatibility pointer for the Claude Code AITP v5 adapter; active templates live under deploy/templates/claude-code. |
The supported Claude Code path is installed by
python scripts/aitp-pm.py install --agent claude-code and uses:
brain/v5/native_mcp.pymcp__aitp__aitp_v5_*deploy/templates/claude-code/using-aitp.mddeploy/templates/claude-code/aitp-runtime.mdRestore an existing topic through the v5 recovery audit, execution brief, and claim relation map before expanding or recording. Use explicit typed writes at durable research moments and preserve every human, validation, and trust gate.
Legacy stage files and aliases are migration/read-only compatibility surfaces; they are not the active research lifecycle.