Automate Wizstar in BitBrowser fingerprint browser windows with Playwright CDP. Use when the user asks to open a numbered BitBrowser window, log into wizstar.com with a stored local Google account, switch or reuse local account credentials, or navigate to Wizstar tools such as /tools/generate_video.
Coordinate the user's Windows, Mac, and Tencent Cloud server Codex peers through verified threads, AppServer stdio, approved SSH aliases, Tailscale, and restricted relay channels. Use when the user asks Codex peers to communicate, inspect or send work across Windows/Mac/server Codex, run a one-shot exchange with reply writeback, control fixed Mac Codex employees, recover a cross-device job, or mentions 三端 Codex, Codex 点对点, Windows/Mac bridge, 腾讯云 Codex, server-main, Tailscale, SSH relay, AppServer, or 远程调度 Codex.
Safely identify, connect to, inventory, and operate the user's Windows, Linux, and Mac server fleet through recorded SSH aliases and host-specific boundaries. Use when the user asks about a server, VPS, 云服务器, SSH, deployment host, migration, backup, capacity, service, port, domain-to-host route, or which machine should receive work.
Repository-grounded threat modeling that enumerates trust boundaries, assets, attacker capabilities, abuse paths, and mitigations, and writes a concise Markdown threat model. Trigger only when the user explicitly asks to threat model a codebase or path, enumerate threats/abuse paths, or perform AppSec threat modeling. Do not trigger for general architecture summaries, code review, or non-security design work.
Perform language and framework specific security best-practice reviews and suggest improvements. Trigger only when the user explicitly requests security best practices guidance, a security review/report, or secure-by-default coding help. Trigger only for supported languages (python, javascript/typescript, go). Do not trigger for general code review, debugging, or non-security tasks.
Use when the user explicitly asks for a desktop or system screenshot (full screen, specific app or window, or a pixel region), or when tool-specific capture capabilities are unavailable and an OS-level capture is needed.
Design save/load for game state — choosing what to serialize, file formats, save slots, atomic crash-safe writes, schema versioning and migration, and autosave. Engine-neutral. Use when the user mentions save system, save/load, game state persistence, save slots, autosave, save file corruption, or migrating old saves to a new version.
Build a playable prototype in about an hour to answer one question — is it fun? — with greybox primitives, a hard timebox, and explicit keep/kill criteria. Use when prototyping a mechanic, making a vertical slice or MVP, greyboxing/blockout, or judging throwaway vs keep.
Generate game content procedurally — seeded deterministic RNG, value/Perlin/ Simplex noise for terrain and heightmaps, grid dungeon generation (rooms + corridors, BSP, random walk), and weighted loot/drop tables. Engine-neutral algorithms. Use when the user mentions procedural generation, perlin/simplex noise, random seed, dungeon generator, heightmap/terrain, or loot tables.
Persistent browser and Electron interaction through `js_repl` for fast iterative UI debugging.
Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via `playwright-cli` or the bundled wrapper script.
Build, improve, brand, deploy, and verify 念念智剪, the OpenChatCut-based AI video editor at edit.cauai.fun. Use for automatic rough cuts, MiMo ASR or TTS, Qwen forced alignment, captions, transitions, exports, editor-brand changes, public deployment, and integration with Niannian AI.
Run NianNian AI web changes from GitHub Issue through isolated branch, focused implementation, real verification, pull-request handoff, release candidate, and explicitly approved production deployment. Use for NianNian Studio, canvas, API, provider, asset-library, homepage, deployment, rollback, beta-readiness, CI, observability, data-recovery, or two-person collaboration work.
Build, repair, and evolve the Niannian AI websites around their real user paths. Use for ai.cauai.fun main-site workbench, studio, Nomi canvas, projects, brand, and approved surfaces; use for dh.cauai.fun login, TZB, projects, materials, templates, six-step workbench, video delivery, pricing, and billing. Keep the two product boundaries separate.
Prevent mixed website assets, stale cache releases, duplicate runtime ownership, workbench regressions, false completion, and unsafe promotion for Niannian AI websites. Use before any live ai.cauai.fun or dh.cauai.fun code, CSS, JavaScript, SSR, route, asset, authentication, media, or deployment change; also use when a change appears deployed but users still see old or broken behavior.
Build, evaluate, integrate, and quality-check an AI media infinite canvas for Niannian AI. Use when the task involves node-based image or video generation, storyboard canvases, RunningHub/TapNow/ComfyUI-like workflows, Mayi Canvas, Daxiong Canvas, media nodes, provider execution, canvas persistence, or visual workflow integration into ai.cauai.fun.
Manage and run the local GitHub selected-project bundle containing WorldMonitor, DeepTutor, code-review-graph, OfficeCLI, and Archscribe. Use when the user asks to inspect, install, start, stop, check, index, render, or use any of these projects locally, or asks to add another GitHub project to this local bundle.
Build and package media-processing APIs that accept images, prompts, audio, and video, enqueue long-running jobs, run Playwright browser automation, and return durable output-video URLs. Use for API wrappers around web applications, RPA workflows, video-generation pipelines, uploads, API-key authentication, job status, callbacks, Docker deployment, or future tasks that need reusable FastAPI + Redis/Celery + Playwright + MinIO/S3 + PostgreSQL patterns.
