菜单
Re-orient after a conversation compaction. Give a short, scannable summary of where the work stands and what's next. Use right after a compaction, or when the user asks "where are we?" / "what were we doing?".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
Audits the copy of a multilingual project (next-intl, i18next, vue-i18n, Rails locales, etc.) for grammar errors, register inconsistencies (e.g. tu/vostè mixing in Catalan, tú/usted in Spanish), cross-locale structural gaps, non-idiomatic phrasing, and formatting issues. Discovers the locale files, presents findings in severity-grouped tables, then asks the user to confirm each group before applying any fix. Use when the user says "audit copy", "check translations", "find copy inconsistencies", "review locale files", or wants to check multilingual content quality.
Audit and realign a project's design system. Finds hardcoded colors/values that bypass DS tokens, unused DS tokens, and font inconsistencies. Use when the user wants to check DS coverage, hunt down hardcoded styling, or readjust styling to flow through the DS.
Capture before/after screenshots (or recordings) of a branch's UI/UX changes by running the base commit and the branch side by side against the same data, then saving paired shots to ~/Downloads. Use when the user asks to screenshot changes before and after, show a branch's visual diff, capture before/after of a PR, or document UI/UX improvements visually. Works for any stack — frontend, backend/API responses, CLI output, etc.
Commit pending changes by planning, staging, and creating separate atomic commits for unrelated WIP. Invoke automatically when the user asks to commit, stage changes, save work to git, or split WIP into commits.
Spawn a fresh subagent, in an unbiased context with no memory of the current conversation, to adversarially challenge the current plan, approach, or facts under discussion — then report back what holds up and what doesn't. Asks the user which model and reasoning effort to use for the challenger, recommending a more capable model than the current session. Use when the user wants a second opinion, wants to stress-test a plan with a sharper/independent reviewer, says "challenge this", "poke holes in this", "play devil's advocate", or wants an adversarial review.
| name | post-compact |
| description | Re-orient after a conversation compaction. Give a short, scannable summary of where the work stands and what's next. Use right after a compaction, or when the user asks "where are we?" / "what were we doing?". |
Re-orient after a compaction. Give the user a short, scannable summary of the current state of the work.
Report:
Keep it to a few lines. Surface only what's needed to continue confidently. If anything is unclear after the compaction, say so instead of guessing.
