All Skills

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

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

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

Use this skill when the user is designing any visual system, UI, graphic, layout, brand asset, or interface and needs structured, high-quality, communication-first design decisions across typography, layout, color, imagery, and UX.

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 this when reviewing a full system design, architecture plan, or cross-service implementation for operational risk, boundary clarity, security posture, deployability, and maintainability.

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 when the team needs a repeatable multi-step workflow, pipeline, or operating sequence that connects multiple skills, systems, or product stages. Trigger on requests to design a workflow from idea to launch, onboarding to retention, or request to execution.

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 this when reviewing a feature, service, API, auth design, integration, job system, or deployment plan for security weaknesses, unsafe trust assumptions, input risks, or privilege issues.

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

Use when a product needs third-party integrations such as payments, email, analytics, AI providers, storage, or internal services. Trigger on requests to plan integration boundaries, provider selection, failure handling, or sync strategies.

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 this when designing or refining a Node.js backend service, daemon, worker, integration service, or internal runtime that is not just an Express route layer.

Use this when the system needs logging, metrics, tracing, alerting, or operator-visible runtime signals for APIs, workers, integrations, serverless functions, or local-to-production supportability.

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 this when reviewing or designing UI for keyboard access, semantic structure, focus handling, labels, contrast, error communication, motion sensitivity, or screen-reader-friendly behavior.

Use this when a codebase or design effort needs consistency enforcement for tokens, spacing, typography, color usage, component variants, and reusable interaction patterns.

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 before any complex or ambiguous task where the path forward is unclear. For breaking down multi-step problems, choosing between approaches, clarifying vague requirements, identifying hidden assumptions, planning before building, and preventing costly mistakes from starting in the wrong direction. Activate when user says "how should I approach this", "what's the best way to", "I'm not sure how to", or presents a problem without a clear solution.

Use when the team needs a strategy for validation errors, API failures, job retries, user-facing error UX, observability, or recovery behavior. Trigger on requests to design error handling across frontend, backend, and integrations.

Use this when building or planning a Python command-line tool, command surface, argument model, package entrypoint, or automation-oriented CLI workflow.

Use this when the system needs scheduled tasks, cron-style jobs, periodic maintenance, sync loops, cleanup tasks, or non-interactive background automation that is not simply an API request or queue worker.

Design an application database schema from product flows and backend responsibilities. Use when the team needs core entities, relationships, lifecycle fields, indexes, audit needs, tenancy boundaries, and migration-minded schema planning for an MVP or production system.

Use this when the user gives a broad app, system, service, tool, or feature request and it must be converted into structured implementation requirements, runtime assumptions, security concerns, likely components, and handoff tasks for developer or designer skills.

Use when designing PostgreSQL tables, enums, relationships, migrations, storage metadata, or tenant-aware schema structures for a Supabase-backed app. Trigger on requests about Supabase schema planning or SQL-first data design.

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 when building or planning Firebase Cloud Functions for webhooks, backend APIs, scheduled jobs, claim assignment, or privileged Firestore logic. Trigger on requests to create or review Firebase Functions.

Use when Codex needs to generate or scaffold a React or Next.js component with clear props, state handling, Tailwind styling direction, accessibility, and file structure. Trigger on requests to create a component, page section, dashboard widget, form, modal, or reusable UI block.

Use when a web product or component needs responsive layout planning across mobile, tablet, and desktop. Trigger on requests about breakpoints, layout adaptation, content priority, or mobile-first UI behavior.

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.