Coding & Dev Tools

Search GIF providers with CLI/TUI, download results, and extract stills/sheets.

Capture and automate macOS UI with the Peekaboo CLI.

Control Sonos speakers (discover/status/play/volume/group).

GitHub archive: issue/PR search, sync freshness, duplicate clusters, gh-shim PR status, and Gitcrawl repo work.

Add, update, list, search, or inspect Things 3 todos, inbox, today, projects, areas, and tags on macOS.

Send third-party WhatsApp messages or sync/search WhatsApp history via wacli, not normal active chats.

Search meme templates, suggest formats, and generate local or hosted image memes.

Generate charts and visualizations from structured data using D3.js and Chart.js.

Current weather and forecasts with wttr.in via curl for locations, rain, temperature, travel planning.

阶段① 需求确认。以提问方式逐步确认需求，产出 design.md 第一章。

阶段⑤ Review。审查已实现的代码并修复问题。

夜间模式：无人值守连续推进，遇歧义不停下、用最稳妥假设继续并记录。只能由用户手动开启。

阶段③ 任务划分。把 design.md 拆成 tasks/<模块>.md 和 tasks/progress.md。

Use when code is hard to read, has duplication, is too complex, has grown beyond 300 lines, or needs restructuring without changing behavior. For extracting functions, simplifying nested logic, removing dead code, improving naming, splitting large files, and applying clean code principles. Activate when user says "clean this up", "this is messy", "simplify", "extract", or "improve readability".

Use when investigating a bug, runtime error, unexpected behavior, test failure, or crash. For systematic root cause analysis, error message interpretation, stack trace reading, reproduction steps, and targeted fixes. Activate when the user says "it's broken", "this doesn't work", "I'm getting an error", or "help me debug".

Use when an existing Antigravity skill has weak triggers, vague instructions, missing constraints, or poor structure and needs to be improved. Trigger on requests to rewrite, tighten, split, or review a skill for better routing and reuse.

Use when user flows already exist and the team needs a screen inventory, screen responsibilities, key states, and view hierarchy for a product or feature. Trigger on requests to break a flow into pages, views, or screen-level structure.

Use this when the deliverable is a CLI tool, command suite, operator utility, or local developer tool and the team needs command structure, UX, config, packaging, and safety planning across languages.

Use when implementing login, registration, session handling, protected routes, or role-based access.

Use this when a feature or product needs a clear end-to-end user journey across entry, action, system response, and outcome. Trigger on requests to map the full experience before screens or components are finalized.

Use this when the team needs detailed interaction behavior for user inputs, transitions, feedback, validation, confirmations, or stateful UI behavior that should be implementation-ready rather than purely visual.

Use when defining a feature's purpose and user value before building it, writing user stories, mapping user flows end-to-end, prioritizing what to build next, evaluating whether a feature solves a real problem, or reviewing scope to prevent over-engineering. Activate when user says "what should I build", "plan the feature", "is this the right approach", "define the requirements", or presents an idea without a clear user need.

Use this when the team needs to define permissions, roles, membership rules, resource ownership, or action-level authorization separate from authentication choice. Trigger on requests about access models, RBAC, ABAC, tenancy, or protected operations.

Use when the team needs authentication, identity providers, custom claims, session strategy, or permission design for a Firebase-backed app. Trigger on requests to design or review Firebase Auth architecture.

Use this when a Python worker, consumer, scheduled processor, or background execution service needs design or review. Trigger on requests about Python async jobs, consumers, schedulers, or long-running background processes.

Use this when reviewing how a codebase organizes configuration files, env vars, runtime options, feature flags, and per-environment settings. Trigger on requests to clean up or validate config structure.

Use this when the team needs to decide how responsibilities should be split across services, modules, workers, APIs, or runtimes. Trigger on requests about service boundaries, ownership, modularity, monolith versus separation, or where logic should live.

GSD Execute — Get Shit Done

Plan backend domains, services, jobs, integrations, and failure handling for a product or major feature. Use when UX and product scope are defined and the team needs a production-minded backend design without defaulting to premature microservices.

Evaluate a raw app, startup, SaaS, internal tool, marketplace, or AI product idea before planning features. Use when the user shares a vague concept and needs pain analysis, market realism, feasibility, differentiation, risks, or a build/no-build recommendation.

Use when context window is filling up, sessions are getting slow, or you need to preserve state across sessions. For context compression, state snapshots, search-first discipline, and cross-session memory management.

Use when the user wants to create a new Antigravity skill pack or add a focused skill folder with SKILL.md, references, examples, or scripts. Trigger on requests to generate a skill, scaffold a skill, or expand the local skill library.

Use this when a Python repository needs package-level planning, import boundaries, module naming, reusable library extraction, or distribution-friendly structure.

Use this when a Supabase app needs file or object storage design, bucket strategy, signed URL handling, metadata patterns, upload trust boundaries, or storage access controls.

Write an implementation plan from an approved architecture and MVP scope. Use when the team needs milestones, workstreams, dependency ordering, acceptance criteria, and execution sequencing that connect product intent to shippable engineering work.

Extract the core product philosophy, strategic posture, and design principles from a raw concept or founder brief. Use when the team needs a crisp product promise, guiding principles, product point of view, or a philosophy statement before scope and UX planning.