content/skills/developer-tools-integrations/antigravity-companion/SKILL.md
Coordinate Antigravity companion workflows for staged review, focused task execution, follow-up analysis, and clear continuation boundaries. Use this skill when the user explicitly wants an Antigravity-native companion process, wants help deciding how Antigravity should review versus implement, or needs a structured Antigravity workflow instead of ad-hoc shell usage. Prefer this whenever the task is specifically about operating Antigravity as a companion rather than a single one-off command.
npx skillsauth add bahayonghang/my-claude-code-settings antigravity-companionInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use this skill when the user wants an Antigravity companion workflow with explicit stages and boundaries.
Use antigravity-companion when the user wants Antigravity to:
| Skill | Best for |
|---|---|
| antigravity-companion | Structured Antigravity companion workflow |
| codex-companion | Codex runtime lifecycle and persistent Codex task handling |
| claude-code-companion | Claude Code-native staged workflow |
| direct Antigravity usage | short one-off Antigravity commands |
Treat this skill as a workflow layer around Antigravity.
Do not promise hidden persistent threads, job ids, or provider-native runtime lifecycle features unless they are actually available in the concrete Antigravity environment being used.
codex-companion.development
Turn vague or complex Codex tasks into strong `/goal` commands with outcome, verification, constraints, boundaries, iteration policy, completion evidence, and pause/block conditions. Use when the user asks for Codex goal instructions, Goal 指令, 目标指令, `/goal` prompts, 中文 Goal 模板, plan-to-goal interviews, success criteria, verification commands, or bounded agent work definitions.
tools
Write, debug, and validate ast-grep structural code search rules. Use this skill when the user needs syntax-aware code search, AST pattern matching, structural refactor discovery, language-construct queries, or searches that plain text tools like rg can miss, such as finding functions with particular descendants, calls inside specific contexts, missing error handling, React hook shapes, decorators, or other Tree-sitter-backed code structures.
development
Use when the user asks to ground an ambitious proposal, avoid over-grand designs, make a bold direction executable, pressure-test feasibility, prevent "too much vision and too little landing", or turn a strategy/refactor/product idea into the smallest verifiable first move with stop rules. Trigger for requests such as 落地, 先落地, 别太飘, 收一收, 可执行, 可验证, 止损, and for follow-ups after geju-style big-picture thinking. Do not trigger for ordinary code review or implementation unless the user explicitly asks to ground or shrink the plan first.
development
Use when the user explicitly asks to think bigger, open up the design space, challenge conservative design, avoid over-indexing on backward compatibility, escape local-detail fixation, or make a bold high-level product or architecture direction call. Use for strategic reframing, not for ordinary code review, PRD writing, implementation planning, or adversarial risk review.