d0ublecl1ck

Professional RuyiPage (Python) Firefox automation workflow and troubleshooting using the bundled project README and curated RuyiPage docs; use when writing, debugging, or refactoring RuyiPage scripts for FirefoxPage, FirefoxOptions, launch and attach flows, element interaction, user contexts, request interception, anti-bot flows, BiDi-based automation, and fingerprint-browser takeover.

Professional DrissionPage (Python) automation development workflow and troubleshooting using the bundled DrissionPage docs (v4.1.1.2); use when writing/debugging/refactoring DrissionPage scripts for ChromiumPage/WebPage/SessionPage, element locating and interaction, waits, downloads/uploads, network listening, and configuration.

Safely group all worktree changes into auditable Conventional Commits and push them. Use only when the user explicitly asks to use `commit-and-push` or `cap`, or explicitly instructs the agent to commit and push. Covers dirty worktrees, multiple repositories, first commits, sync-only branches, hooks, ignore rules, secrets, upstream setup, and optional PR creation. Do not use for code changes, review, debugging, planning, vague shipping intent, commit-message drafting alone, or commit-only requests.

Commit and push only the files the agent modified in the current task or session, instead of all worktree changes. Use when the user wants a scoped git commit/push, wants to avoid touching unrelated edits in a dirty worktree, or asks to "push what you did", "只提交你改的文件", or similar selective commit requests. Everything except commit scope mirrors commit-and-push; for committing all worktree changes, use commit-and-push instead.

Develop, debug, test, and document the niuma-cli local Python command-line tool for developer work logs, projects, todos, progress records, focus/chill sessions, tags, config recovery, stats, daily or weekly reports, and OpenAI-compatible LLM report generation. Use when working in or discussing the niuma-cli repository, commands, SQLite schema, local config, tests, docs, packaging, or user-facing CLI behavior.

Create and maintain a private development mirror of a public upstream repository without using the hosting platform's Fork button. Use when a user needs to secondary-develop an open-source project privately, keep proprietary changes out of a public fork, set up origin/upstream remotes, sync upstream changes, or resolve conflicts during upstream merges and rebases on GitHub, GitLab, or similar platforms.

Analyze the current conversation at the end of a task, convert reusable lessons into directly executable project rules or system rules, ask which rule lines should be saved, and persist the confirmed rules into the correct rule files. Use when the user wants to复盘对话、沉淀经验、整理可复用做法、保存踩坑记录、归档工作流经验, especially near the end of a conversation or task.

Render Mermaid diagrams using beautiful-mermaid as Unicode/ASCII (terminal/chat) or SVG (rich UI). Use when you need a quick, good-looking diagram preview in plain text or want to generate an SVG from Mermaid source (Bun preferred).

Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.

Interactive Socratic wizard to create or refine high-quality Product Requirements Documents (PRD) by asking step-by-step discovery questions, then drafting a full Markdown PRD. Use when a user asks to make a PRD, product requirements, spec doc, or wants help refining an idea into a PRD.

Keep documentation and architecture codemaps up to date with the code. Use after significant changes, refactors, or when README/guides/onboarding docs drift; generate or refresh module maps and validate doc accuracy.

Security review and remediation for code that handles user input, authentication/authorization, secrets, file/network access, or sensitive data. Use to detect OWASP-style risks (injection, SSRF, XSS, misconfig) and propose concrete fixes.