菜单
Create a typed project recap conversation artifact. Use when the user invokes /project-recap, asks for a context-switching recap, wants a visual summary of project state, decisions, progress, blockers, or next steps.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when deciding between follow-up queues, scheduled callbacks, automation-owned attention, wakeups, and async follow-up surfaces.
Use when a task benefits from JavaScript orchestration, explicit phases, structured progress logs, parallel fanout, or multiple daemon-backed subagents coordinated through the workflow tool.
Use when starting, inspecting, rerunning, following up, or cancelling durable background commands or subagents.
Use when designing, creating, editing, building, validating, installing, or debugging Neon Pilot extensions, application pages, contributions to existing applications, or complete first-class applications from the bundled desktop app. This skill is self-contained and must be used without a Neon Pilot source checkout.
Use when working with the built-in desktop Workbench Browser, browser comments, browser snapshots, CDP actions, screenshots, or the browser versus agent-browser boundary.
Use the unified Neon Pilot CLI/control plane for self-administration, delegated agent control, conversations, workspace/sidebar state, runs, automations, extensions, settings, and extension-contributed administration surfaces.
| name | project-recap-artifact |
| description | Create a typed project recap conversation artifact. Use when the user invokes /project-recap, asks for a context-switching recap, wants a visual summary of project state, decisions, progress, blockers, or next steps. |
Create a concise visual recap that helps someone re-enter a project with the current state, decisions, open work, and next actions in one place.
../artifacts/references/visual-explainer-defaults.md and use the technical-report preset.../../templates/visual-explainer.html as the HTML starting point when helpful.artifact tool with the metadata below.{
"action": "save",
"kind": "html",
"artifactType": "project-recap",
"stylePreset": "technical-report",
"templateVersion": "visual-explainer-v1",
"source": {
"kind": "command",
"command": "project-recap"
}
}
Add source.paths for project files or docs used as recap sources.
styleOverrides while keeping the recap calm and readable.