菜单
Use when finishing a brainstorm, writing a design spec, or producing an implementation plan in this project. Directs the output to ClickUp as a doc on the DA-XXX task instead of saving to the repo or local disk.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when adding or changing user-facing strings in the extension (i18n.t calls or locale JSON) under packages/danmaku-anywhere. Surfaces the extract workflow and footguns so the change does not fail the i18n CI check or ship an untranslated or inconsistent string.
Use to open a fresh Claude session in a new terminal tab for a da-dev worktree, after `scripts/da-bootstrap.mjs` prints its READY block. Covers Warp, Windows Terminal, and a manual fallback.
Use when an extension change needs agentic verification in a real browser — content scripts, popup UI, network calls, fonts, console errors. Spawns the agent's own Chrome via the chrome-devtools-ext MCP. Complements (does not replace) human-eye verification via `pnpm dev:browser`.
Use to monitor an open PR for AI/bot review comments, evaluate them critically, push fixes for real issues, and resolve threads — capped at a sensible duration so it self-terminates. Invoke as "babysit PR
Use when about to write or modify a Playwright e2e spec under `packages/danmaku-anywhere/e2e/`. Points at the canonical doctrine and surfaces the load-bearing rules so the spec doesn't get bounced in review.
Use when you need to load a specific published preview/nightly extension build into the agent's MCP browser by run-number, branch name, or tag. Faster than rebuilding locally when you only want to exercise an existing artifact.
| name | specs-in-clickup |
| description | Use when finishing a brainstorm, writing a design spec, or producing an implementation plan in this project. Directs the output to ClickUp as a doc on the DA-XXX task instead of saving to the repo or local disk. |
Brainstorm outputs, design specs, and implementation plans live as ClickUp docs linked from the owning DA-XXX task. Not in the repo (docs/superpowers/specs/, .specs/), not in agent auto-memory long-term. The ClickUp task is the single source of truth; repo-tracked specs go stale, local-only specs vanish with the worktree.
clickup_* tools)CLICKUP_DA_SPACE_ID set in the environment (the developer exports it in their shell, e.g. ~/.zshenv; see da-dev step 1)If either is missing, stop and tell the human. Don't fall back to committing the spec to the repo. Never hardcode IDs in tracked files.
After superpowers:brainstorming, superpowers:writing-plans, or anything that produces a spec/plan:
da-dev step 1 does this. Note the DA-XXX ID.clickup_search with filters: { asset_types: ['doc'] } covers names and contents; clickup_get_task_comments covers links posted to the task. Iterate via clickup_update_document_page rather than recreate.type: "6") surface as views inside the list. Resolve <space_id> from $CLICKUP_DA_SPACE_ID.
clickup_create_document(
name: "Spec: <topic>",
parent: { id: <space_id>, type: "4" },
visibility: <project default>,
create_page: false
)
clickup_create_document_page(
document_id: <new doc id>,
name: "Design", // or "Plan", "Notes"
content: <markdown>
)
clickup_create_document_page calls. One doc per task; multiple pages within.clickup_create_task_comment). There is no single-call attach.If superpowers:brainstorming / superpowers:writing-plans (or anything else) tries to write into docs/superpowers/specs/, docs/superpowers/plans/, or .specs/, send the output to ClickUp instead. If a draft already exists on disk, push it to ClickUp and delete the local copy in the same step.
The doc URL belongs on the ClickUp task, not in the PR body. The PR title's DA-XXX auto-links the task.