chore(agents): migrate .agent to .agents directory (#10489) (#10491)

Co-authored-by: tobiu <tobiasuhlig78@gmail.com>

Author: neo-gemini-pro

.agent/ANTIGRAVITY_RULES.md .agents/ANTIGRAVITY_RULES.md.agent/ANTIGRAVITY_RULES.md renamed to .agents/ANTIGRAVITY_RULES.md

@@ -4,4 +4,4 @@ description: Authoritative guide on how to architect, format, and structure new
 triggers: Use this skill if the user asks you to create a new skill, teach an agent a new capability, or if you need to recall the exact folder structure and YAML frontmatter required for skills.
 ---
 # Skill Creation Framework
-If you are tasked with creating a new Agent Skill, you MUST immediately use the `view_file` tool to read and strictly adhere to `.agent/skills/create-skill/references/skill-authoring-guide.md` before creating any files. This prevents system prompt bloat and ensures future agents can parse your skill correctly.
+If you are tasked with creating a new Agent Skill, you MUST immediately use the `view_file` tool to read and strictly adhere to `.agents/skills/create-skill/references/skill-authoring-guide.md` before creating any files. This prevents system prompt bloat and ensures future agents can parse your skill correctly.

.agents/skills/create-skill

@@ -14,7 +14,7 @@ You must **NEVER** write the entire instruction manual of a skill directly into
 Whenever you create a new skill named `my-new-skill`, you must scaffold the following standard directory structure:
 
 ```text
-.agent/skills/my-new-skill/
+.agents/skills/my-new-skill/
 ├── SKILL.md                 # Required - Main lightweight router with YAML frontmatter
 ├── references/              # Required - Documentation and heavy payload markdown files
 │   └── [descriptive-payload-name].md
@@ -43,9 +43,9 @@ Below the YAML block, the Markdown body MUST be a concise directive instructing
 
 ```markdown
 # [Skill Title]
-If you need to [do this task], you MUST immediately use the `view_file` tool to read and strictly adhere to `.agent/skills/[skill-name]/references/[descriptive-payload-name].md` before proceeding.
+If you need to [do this task], you MUST immediately use the `view_file` tool to read and strictly adhere to `.agents/skills/[skill-name]/references/[descriptive-payload-name].md` before proceeding.
 ```
-*(Always use a relative path like `.agent/skills/...` for the `view_file` tool parameter).*
+*(Always use a relative path like `.agents/skills/...` for the `view_file` tool parameter).*
 
 ## 2. Writing the Payload (references/*.md)
 
@@ -70,13 +70,13 @@ When a swarm agent discovers a systemic trap, an architectural pattern, or a wor
 
 ## 4. The Claude Symlink Mandate
 
-The Neo.mjs agent swarm operates across multiple identities (e.g., Antigravity and Claude Code). While `.agent/skills/` is the canonical repository of skills, Claude Code relies on a dedicated `.claude/skills/` directory to parse its available tools at boot.
+The Neo.mjs agent swarm operates across multiple identities (e.g., Antigravity and Claude Code). While `.agents/skills/` is the canonical repository of skills, Claude Code relies on a dedicated `.claude/skills/` directory to parse its available tools at boot.
 
-**CRITICAL:** Whenever you create a *new* skill folder in `.agent/skills/`, you **MUST** immediately create a corresponding symlink in the `.claude/skills/` directory.
+**CRITICAL:** Whenever you create a *new* skill folder in `.agents/skills/`, you **MUST** immediately create a corresponding symlink in the `.claude/skills/` directory.
 
 ```bash
 # Run from repository root:
-ln -sf ../../.agent/skills/my-new-skill .claude/skills/my-new-skill
+ln -sf ../../.agents/skills/my-new-skill .claude/skills/my-new-skill
 ```
 
 Failure to create this symlink will result in Claude being entirely blind to the new protocol, causing severe swarm capability desyncs.

.agent/skills/create-skill/SKILL.md .agents/skills/create-skill/SKILL.md.agent/skills/create-skill/SKILL.md renamed to .agents/skills/create-skill/SKILL.md

@@ -4,4 +4,4 @@ description: Authoritative guide on debugging Antigravity IDE MCP servers, preve
 triggers: Use this skill if the user's Antigravity MCP server panel has a perpetual loading spinner, if MCP processes are duplicating, if sqlite workspace states are corrupted (`__store` null error), or if you need to know how to properly scope `.gemini/settings.json` vs global configurations.
 ---
 # Antigravity Debugging Guide
-If you need to debug Antigravity IDE issues, MCP server duplication, database initialization race conditions, or fix workspace UI crashes (loading spinners), you MUST immediately use the `view_file` tool to read and strictly adhere to `.agent/skills/debugging-antigravity/references/debugging-guide.md` before proceeding.
+If you need to debug Antigravity IDE issues, MCP server duplication, database initialization race conditions, or fix workspace UI crashes (loading spinners), you MUST immediately use the `view_file` tool to read and strictly adhere to `.agents/skills/debugging-antigravity/references/debugging-guide.md` before proceeding.

…kill/references/skill-authoring-guide.md …kill/references/skill-authoring-guide.md.agent/skills/create-skill/references/skill-authoring-guide.md renamed to .agents/skills/create-skill/references/skill-authoring-guide.md .agent/skills/create-skill/references/skill-authoring-guide.md renamed to .agents/skills/create-skill/references/skill-authoring-guide.md

@@ -77,7 +77,7 @@ Find and destroy orphaned workspace hashes so the IDE does not re-register them
 find "$HOME/Library/Application Support/Antigravity/User/workspaceStorage" -name "workspace.json" 2>/dev/null
 
 # Typically, you delete the folders containing stale mapping values like:
-# {"folder": "file://.agent/skills/ticket-intake"}
+# {"folder": "file://.agents/skills/ticket-intake"}
 ```
 
 After performing these purges, closing and restarting the IDE forces the UI to cleanly rebuild the workspace payload based only on the actively opened directory.

…nt/skills/debugging-antigravity/SKILL.md …ts/skills/debugging-antigravity/SKILL.md.agent/skills/debugging-antigravity/SKILL.md renamed to .agents/skills/debugging-antigravity/SKILL.md .agent/skills/debugging-antigravity/SKILL.md renamed to .agents/skills/debugging-antigravity/SKILL.md

@@ -5,6 +5,6 @@ triggers: Use this skill when an agent is about to pick up its first sub from an
 ---
 # Epic Review Skill
 
-If you are about to pick up your first sub-issue from an epic that your model-identity has not yet reviewed, you MUST immediately use the `view_file` tool to read and strictly adhere to `.agent/skills/epic-review/references/epic-review-workflow.md` before running `ticket-intake` or any sub-work steps.
+If you are about to pick up your first sub-issue from an epic that your model-identity has not yet reviewed, you MUST immediately use the `view_file` tool to read and strictly adhere to `.agents/skills/epic-review/references/epic-review-workflow.md` before running `ticket-intake` or any sub-work steps.
 
 Subsequent sub pickups from the same epic by the same model-identity cite the prior review by URL reference instead of re-running the skill.

…ntigravity/references/debugging-guide.md …ntigravity/references/debugging-guide.md.agent/skills/debugging-antigravity/references/debugging-guide.md renamed to .agents/skills/debugging-antigravity/references/debugging-guide.md .agent/skills/debugging-antigravity/references/debugging-guide.md renamed to .agents/skills/debugging-antigravity/references/debugging-guide.md

@@ -105,7 +105,7 @@ Missing traps are an **extension opportunity**, not a blocker — flag them in t
 
 ## 4. Comment Output Format
 
-Post the review as a comment on the epic ticket using `manage_issue_comment` with action `create`. Use the template at `.agent/skills/epic-review/assets/epic-review-comment-template.md` as the structural skeleton.
+Post the review as a comment on the epic ticket using `manage_issue_comment` with action `create`. Use the template at `.agents/skills/epic-review/assets/epic-review-comment-template.md` as the structural skeleton.
 
 **Short form** (stage 1 or 2 failure):
 - Header: `Epic Review — Stage [1|2] Challenge by [model-identity]`