@cubis/foundry 0.3.32 → 0.3.33

package/workflows/skills/sentry-automation/SKILL.md

@@ -1,232 +1,18 @@
 ---
-name: sentry-automation
-description: "Automate Sentry tasks via Rube MCP (Composio): manage issues/events, configure alerts, track releases, monitor projects and teams. Always search tools first for current schemas."
-requires:
-  mcp: [rube]
+name: "sentry-automation"
+description: "Compatibility wrapper skill. Canonical MCP skill moved to mcp/skills/sentry-automation."
+metadata:
+  deprecated: true
+  replaced_by: "sentry-automation"
+  moved_to: "mcp/skills/sentry-automation/SKILL.md"
+  removal_target: "v0.6.0"
 ---
 
-# Sentry Automation via Rube MCP
+# sentry-automation (Compatibility Wrapper)
 
-Automate Sentry error tracking and monitoring operations through Composio's Sentry toolkit via Rube MCP.
+This legacy workflow-path skill is kept for backward compatibility.
 
-## Prerequisites
+Canonical MCP skill path:
+- mcp/skills/sentry-automation/SKILL.md
 
-- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
-- Active Sentry connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `sentry`
-- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
-
-## Setup
-
-**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
-
-
-1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
-2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `sentry`
-3. If connection is not ACTIVE, follow the returned auth link to complete Sentry OAuth
-4. Confirm connection status shows ACTIVE before running any workflows
-
-## Core Workflows
-
-### 1. Investigate Issues
-
-**When to use**: User wants to find, inspect, or triage error issues
-
-**Tool sequence**:
-1. `SENTRY_LIST_AN_ORGANIZATIONS_ISSUES` - List issues across the organization [Required]
-2. `SENTRY_GET_ORGANIZATION_ISSUE_DETAILS` - Get detailed info on a specific issue [Optional]
-3. `SENTRY_LIST_AN_ISSUES_EVENTS` - View individual error events for an issue [Optional]
-4. `SENTRY_RETRIEVE_AN_ISSUE_EVENT` - Get full event details with stack trace [Optional]
-5. `SENTRY_RETRIEVE_ISSUE_TAG_DETAILS` - Inspect tag distribution for an issue [Optional]
-
-**Key parameters**:
-- `organization_id_or_slug`: Organization identifier
-- `issue_id`: Numeric issue ID
-- `query`: Search query (e.g., `is:unresolved`, `assigned:me`, `browser:Chrome`)
-- `sort`: Sort order (`date`, `new`, `freq`, `priority`)
-- `statsPeriod`: Time window for stats (`24h`, `14d`, etc.)
-
-**Pitfalls**:
-- `organization_id_or_slug` is the org slug (e.g., 'my-org'), not the display name
-- Issue IDs are numeric; do not confuse with event IDs which are UUIDs
-- Query syntax uses Sentry's search format: `is:unresolved`, `assigned:me`, `!has:release`
-- Events within an issue can have different stack traces; inspect individual events for details
-
-### 2. Manage Project Issues
-
-**When to use**: User wants to view issues scoped to a specific project
-
-**Tool sequence**:
-1. `SENTRY_RETRIEVE_ORGANIZATION_PROJECTS` - List projects to find project slug [Prerequisite]
-2. `SENTRY_RETRIEVE_PROJECT_ISSUES_LIST` - List issues for a specific project [Required]
-3. `SENTRY_RETRIEVE_ISSUE_EVENTS_BY_ID` - Get events for a specific issue [Optional]
-
-**Key parameters**:
-- `organization_id_or_slug`: Organization identifier
-- `project_id_or_slug`: Project identifier
-- `query`: Search filter string
-- `statsPeriod`: Stats time window
-
-**Pitfalls**:
-- Project slugs are different from project display names
-- Always resolve project names to slugs via RETRIEVE_ORGANIZATION_PROJECTS first
-- Project-scoped issue lists may have different pagination than org-scoped lists
-
-### 3. Configure Alert Rules
-
-**When to use**: User wants to create or manage alert rules for a project
-
-**Tool sequence**:
-1. `SENTRY_RETRIEVE_ORGANIZATION_PROJECTS` - Find project for the alert [Prerequisite]
-2. `SENTRY_RETRIEVE_PROJECT_RULES_BY_ORG_AND_PROJECT_ID` - List existing rules [Optional]
-3. `SENTRY_CREATE_PROJECT_RULE_FOR_ALERTS` - Create a new alert rule [Required]
-4. `SENTRY_CREATE_ORGANIZATION_ALERT_RULE` - Create org-level metric alert [Alternative]
-5. `SENTRY_UPDATE_ORGANIZATION_ALERT_RULES` - Update existing alert rules [Optional]
-6. `SENTRY_RETRIEVE_ALERT_RULE_DETAILS` - Inspect specific alert rule [Optional]
-7. `SENTRY_GET_PROJECT_RULE_DETAILS` - Get project-level rule details [Optional]
-
-**Key parameters**:
-- `name`: Alert rule name
-- `conditions`: Array of trigger conditions
-- `actions`: Array of actions to perform when triggered
-- `filters`: Array of event filters
-- `frequency`: How often to trigger (in minutes)
-- `actionMatch`: 'all', 'any', or 'none' for condition matching
-
-**Pitfalls**:
-- Project-level rules (CREATE_PROJECT_RULE) and org-level metric alerts (CREATE_ORGANIZATION_ALERT_RULE) are different
-- Conditions, actions, and filters use specific JSON schemas; check Sentry docs for valid types
-- `frequency` is in minutes; setting too low causes alert fatigue
-- `actionMatch` defaults may vary; explicitly set to avoid unexpected behavior
-
-### 4. Manage Releases
-
-**When to use**: User wants to create, track, or manage release versions
-
-**Tool sequence**:
-1. `SENTRY_LIST_ORGANIZATION_RELEASES` - List existing releases [Optional]
-2. `SENTRY_CREATE_RELEASE_FOR_ORGANIZATION` - Create a new release [Required]
-3. `SENTRY_UPDATE_RELEASE_DETAILS_FOR_ORGANIZATION` - Update release metadata [Optional]
-4. `SENTRY_CREATE_RELEASE_DEPLOY_FOR_ORG` - Record a deployment for a release [Optional]
-5. `SENTRY_UPLOAD_RELEASE_FILE_TO_ORGANIZATION` - Upload source maps or files [Optional]
-
-**Key parameters**:
-- `version`: Release version string (e.g., '1.0.0', commit SHA)
-- `projects`: Array of project slugs this release belongs to
-- `dateReleased`: Release timestamp (ISO 8601)
-- `environment`: Deployment environment name (e.g., 'production', 'staging')
-
-**Pitfalls**:
-- Release versions must be unique within an organization
-- Releases can span multiple projects; use the `projects` array
-- Deploying a release is separate from creating it; use CREATE_RELEASE_DEPLOY
-- Source map uploads require the release to exist first
-
-### 5. Monitor Organization and Teams
-
-**When to use**: User wants to view org structure, teams, or member lists
-
-**Tool sequence**:
-1. `SENTRY_GET_ORGANIZATION_DETAILS` or `SENTRY_GET_ORGANIZATION_BY_ID_OR_SLUG` - Get org info [Required]
-2. `SENTRY_LIST_TEAMS_IN_ORGANIZATION` - List all teams [Optional]
-3. `SENTRY_LIST_ORGANIZATION_MEMBERS` - List org members [Optional]
-4. `SENTRY_GET_PROJECT_LIST` - List all accessible projects [Optional]
-
-**Key parameters**:
-- `organization_id_or_slug`: Organization identifier
-- `cursor`: Pagination cursor for large result sets
-
-**Pitfalls**:
-- Organization slugs are URL-safe identifiers, not display names
-- Member lists may be paginated; follow cursor pagination
-- Team and member visibility depends on the authenticated user's permissions
-
-### 6. Manage Monitors (Cron Monitoring)
-
-**When to use**: User wants to update cron job monitoring configuration
-
-**Tool sequence**:
-1. `SENTRY_UPDATE_A_MONITOR` - Update monitor configuration [Required]
-
-**Key parameters**:
-- `organization_id_or_slug`: Organization identifier
-- `monitor_id_or_slug`: Monitor identifier
-- `name`: Monitor display name
-- `schedule`: Cron schedule expression or interval
-- `checkin_margin`: Grace period in minutes for late check-ins
-- `max_runtime`: Maximum expected runtime in minutes
-
-**Pitfalls**:
-- Monitor slugs are auto-generated from the name; use slug for API calls
-- Schedule changes take effect immediately
-- Missing check-ins trigger alerts after the margin period
-
-## Common Patterns
-
-### ID Resolution
-
-**Organization name -> Slug**:
-```
-1. Call SENTRY_GET_ORGANIZATION_DETAILS
-2. Extract slug field from response
-```
-
-**Project name -> Slug**:
-```
-1. Call SENTRY_RETRIEVE_ORGANIZATION_PROJECTS
-2. Find project by name, extract slug
-```
-
-### Pagination
-
-- Sentry uses cursor-based pagination with `Link` headers
-- Check response for cursor values
-- Pass cursor in next request until no more pages
-
-### Search Query Syntax
-
-- `is:unresolved` - Unresolved issues
-- `is:resolved` - Resolved issues
-- `assigned:me` - Assigned to current user
-- `assigned:team-slug` - Assigned to a team
-- `!has:release` - Issues without a release
-- `first-release:1.0.0` - Issues first seen in release
-- `times-seen:>100` - Seen more than 100 times
-- `browser:Chrome` - Filter by browser tag
-
-## Known Pitfalls
-
-**ID Formats**:
-- Organization: use slug (e.g., 'my-org'), not display name
-- Project: use slug (e.g., 'my-project'), not display name
-- Issue IDs: numeric integers
-- Event IDs: UUIDs (32-char hex strings)
-
-**Permissions**:
-- API token scopes must match the operations being performed
-- Organization-level operations require org-level permissions
-- Project-level operations require project access
-
-**Rate Limits**:
-- Sentry enforces per-organization rate limits
-- Implement backoff on 429 responses
-- Bulk operations should be staggered
-
-## Quick Reference
-
-| Task | Tool Slug | Key Params |
-|------|-----------|------------|
-| List org issues | SENTRY_LIST_AN_ORGANIZATIONS_ISSUES | organization_id_or_slug, query |
-| Get issue details | SENTRY_GET_ORGANIZATION_ISSUE_DETAILS | organization_id_or_slug, issue_id |
-| List issue events | SENTRY_LIST_AN_ISSUES_EVENTS | issue_id |
-| Get event details | SENTRY_RETRIEVE_AN_ISSUE_EVENT | organization_id_or_slug, event_id |
-| List project issues | SENTRY_RETRIEVE_PROJECT_ISSUES_LIST | organization_id_or_slug, project_id_or_slug |
-| List projects | SENTRY_RETRIEVE_ORGANIZATION_PROJECTS | organization_id_or_slug |
-| Get org details | SENTRY_GET_ORGANIZATION_DETAILS | organization_id_or_slug |
-| List teams | SENTRY_LIST_TEAMS_IN_ORGANIZATION | organization_id_or_slug |
-| List members | SENTRY_LIST_ORGANIZATION_MEMBERS | organization_id_or_slug |
-| Create alert rule | SENTRY_CREATE_PROJECT_RULE_FOR_ALERTS | organization_id_or_slug, project_id_or_slug |
-| Create metric alert | SENTRY_CREATE_ORGANIZATION_ALERT_RULE | organization_id_or_slug |
-| Create release | SENTRY_CREATE_RELEASE_FOR_ORGANIZATION | organization_id_or_slug, version |
-| Deploy release | SENTRY_CREATE_RELEASE_DEPLOY_FOR_ORG | organization_id_or_slug, version |
-| List releases | SENTRY_LIST_ORGANIZATION_RELEASES | organization_id_or_slug |
-| Update monitor | SENTRY_UPDATE_A_MONITOR | organization_id_or_slug, monitor_id_or_slug |
+Install MCP skills with: cbx workflows install --include-mcp

package/workflows/skills/skills_index.json

@@ -192,6 +192,16 @@
     "description": "Use when reviewing pull requests, conducting code quality audits, or identifying security vulnerabilities. Invoke for PR reviews, code quality checks, refactoring suggestions.",
     "triggers": []
   },
+  {
+    "id": "csharp-pro",
+    "name": "csharp-pro",
+    "canonical_id": "csharp-pro",
+    "deprecated": false,
+    "replaced_by": null,
+    "path": ".agents/skills/csharp-pro/SKILL.md",
+    "description": "Use for modern C# backend/application engineering with C# 14 and .NET 10-era production practices.",
+    "triggers": []
+  },
   {
     "id": "database-design",
     "name": "database-design",
@@ -488,18 +498,8 @@
     "deprecated": false,
     "replaced_by": null,
     "path": ".agents/skills/golang-pro/SKILL.md",
-    "description": "Use when building Go applications requiring concurrent programming, microservices architecture, or high-performance systems. Invoke for goroutines, channels, Go generics, gRPC integration.",
-    "triggers": [
-      "Go",
-      "Golang",
-      "goroutines",
-      "channels",
-      "gRPC",
-      "microservices Go",
-      "Go generics",
-      "concurrent programming",
-      "Go interfaces"
-    ]
+    "description": "Use for modern Go services and tooling with Go 1.26-era language/runtime patterns, concurrency safety, and production operations.",
+    "triggers": []
   },
   {
     "id": "gorouter-restoration",
@@ -551,6 +551,16 @@
     "description": "Automatic agent selection and intelligent task routing. Analyzes user requests and automatically selects the best specialist agent(s) without requiring explicit user mentions.",
     "triggers": []
   },
+  {
+    "id": "java-pro",
+    "name": "java-pro",
+    "canonical_id": "java-pro",
+    "deprecated": false,
+    "replaced_by": null,
+    "path": ".agents/skills/java-pro/SKILL.md",
+    "description": "Use for modern Java backend and platform engineering with Java 25-era language/runtime practices.",
+    "triggers": []
+  },
   {
     "id": "javascript-pro",
     "name": "javascript-pro",
@@ -558,18 +568,18 @@
     "deprecated": false,
     "replaced_by": null,
     "path": ".agents/skills/javascript-pro/SKILL.md",
-    "description": "Use when building JavaScript applications with modern ES2023+ features, async patterns, or Node.js development. Invoke for vanilla JavaScript, browser APIs, performance optimization, module systems.",
-    "triggers": [
-      "JavaScript",
-      "ES2023",
-      "async await",
-      "Node.js",
-      "vanilla JavaScript",
-      "Web Workers",
-      "Fetch API",
-      "browser API",
-      "module system"
-    ]
+    "description": "Use for modern JavaScript architecture and implementation across browser, Node, and edge runtimes with ES2025+ practices.",
+    "triggers": []
+  },
+  {
+    "id": "kotlin-pro",
+    "name": "kotlin-pro",
+    "canonical_id": "kotlin-pro",
+    "deprecated": false,
+    "replaced_by": null,
+    "path": ".agents/skills/kotlin-pro/SKILL.md",
+    "description": "Use for modern Kotlin backend/mobile/shared code with Kotlin 2.3-era language tooling and production patterns.",
+    "triggers": []
   },
   {
     "id": "legacy-modernizer",
@@ -722,7 +732,7 @@
     "deprecated": false,
     "replaced_by": null,
     "path": ".agents/skills/nextjs-developer/SKILL.md",
-    "description": "Use for implementing/refactoring Next.js App Router features, Server Components/Actions, SEO, and production architecture. Not for version migration workflows or cache-components-only tuning.",
+    "description": "Use for implementing/refactoring Next.js App Router features, React Server Components/Actions, SEO, and production architecture.",
     "triggers": []
   },
   {
@@ -742,7 +752,7 @@
     "deprecated": false,
     "replaced_by": null,
     "path": ".agents/skills/nodejs-best-practices/SKILL.md",
-    "description": "Node.js development principles and decision-making. Framework selection, async patterns, security, and architecture. Teaches thinking, not copying.",
+    "description": "Decision framework for modern Node.js backend architecture, operations, and security using current LTS-era practices.",
     "triggers": []
   },
   {
@@ -860,17 +870,8 @@
     "deprecated": false,
     "replaced_by": null,
     "path": ".agents/skills/python-pro/SKILL.md",
-    "description": "Use when building Python 3.11+ applications requiring type safety, async programming, or production-grade patterns. Invoke for type hints, pytest, async/await, dataclasses, mypy configuration.",
-    "triggers": [
-      "Python development",
-      "type hints",
-      "async Python",
-      "pytest",
-      "mypy",
-      "dataclasses",
-      "Python best practices",
-      "Pythonic code"
-    ]
+    "description": "Use for production Python with 3.14-era typing, async, packaging, and testing standards.",
+    "triggers": []
   },
   {
     "id": "react-best-practices",
@@ -879,7 +880,7 @@
     "deprecated": false,
     "replaced_by": null,
     "path": ".agents/skills/react-best-practices/SKILL.md",
-    "description": "Performance-focused React/Next.js review checklist from Vercel. Use for optimization/refactor passes, not as the primary implementation skill.",
+    "description": "Performance-focused React/Next.js review checklist. Use for audits and optimization passes, not as primary implementation skill.",
     "triggers": []
   },
   {
@@ -889,23 +890,8 @@
     "deprecated": false,
     "replaced_by": null,
     "path": ".agents/skills/react-expert/SKILL.md",
-    "description": "Use for framework-agnostic React component architecture, hooks/state patterns, and React 19 APIs. For Next.js routing/App Router specifics, use nextjs-developer.",
-    "triggers": [
-      "React",
-      "JSX",
-      "hooks",
-      "useState",
-      "useEffect",
-      "useContext",
-      "Server Components",
-      "React 19",
-      "Suspense",
-      "TanStack Query",
-      "Redux",
-      "Zustand",
-      "component",
-      "frontend"
-    ]
+    "description": "Use for framework-agnostic React architecture with React 19 patterns, state design, and performance tuning.",
+    "triggers": []
   },
   {
     "id": "red-team-tactics",
@@ -954,7 +940,7 @@
     "deprecated": false,
     "replaced_by": null,
     "path": ".agents/skills/rust-pro/SKILL.md",
-    "description": "Master Rust 1.75+ with modern async patterns, advanced type system",
+    "description": "Use for modern Rust systems/services with stable 1.91-era patterns, async correctness, and performance-focused design.",
     "triggers": []
   },
   {
@@ -1194,7 +1180,7 @@
     "deprecated": false,
     "replaced_by": null,
     "path": ".agents/skills/typescript-pro/SKILL.md",
-    "description": "Use when building TypeScript applications requiring advanced type systems, generics, or full-stack type safety. Invoke for type guards, utility types, tRPC integration, monorepo setup.",
+    "description": "Use for TypeScript architecture and implementation with TS 5.9+ production baselines and TS 6/7 transition readiness.",
     "triggers": []
   },
   {

package/workflows/skills/typescript-pro/SKILL.md

@@ -1,87 +1,60 @@
 ---
 name: "typescript-pro"
-description: "Use when building TypeScript applications requiring advanced type systems, generics, or full-stack type safety. Invoke for type guards, utility types, tRPC integration, monorepo setup."
+description: "Use for TypeScript architecture and implementation with TS 5.9+ production baselines and TS 6/7 transition readiness."
+license: MIT
+metadata:
+  version: "2.0.0"
+  domain: "language"
+  role: "specialist"
+  stack: "typescript"
+  baseline: "TypeScript 5.9 stable"
+  transition: "TypeScript 6 compatibility prep"
 ---
 
-
 # TypeScript Pro
 
-## Overview
-
-Senior TypeScript specialist with deep expertise in advanced type systems, full-stack type safety, and production-grade TypeScript development.
-
-## Role Definition
-
-You are a senior TypeScript developer with 10+ years of experience. You specialize in TypeScript 5.0+ advanced type system features, full-stack type safety, and build optimization. You create type-safe APIs with zero runtime type errors.
-
-## When to Use This Skill
-
-- Building type-safe full-stack applications
-- Implementing advanced generics and conditional types
-- Setting up tsconfig and build tooling
-- Creating discriminated unions and type guards
-- Implementing end-to-end type safety with tRPC
-- Optimizing TypeScript compilation and bundle size
-
-## Core Workflow
-
-1. **Analyze type architecture** - Review tsconfig, type coverage, build performance
-2. **Design type-first APIs** - Create branded types, generics, utility types
-3. **Implement with type safety** - Write type guards, discriminated unions, conditional types
-4. **Optimize build** - Configure project references, incremental compilation, tree shaking
-5. **Test types** - Verify type coverage, test type logic, ensure zero runtime errors
-
-## Available Steering Files
-
-Load detailed guidance on-demand:
-
-| Topic          | Reference                    | Load When                                                    |
-| -------------- | ---------------------------- | ------------------------------------------------------------ |
-| Advanced Types | `references/advanced-types.md` | Generics, conditional types, mapped types, template literals |
-| Type Guards    | `references/type-guards.md`    | Type narrowing, discriminated unions, assertion functions    |
-| Utility Types  | `references/utility-types.md`  | Partial, Pick, Omit, Record, custom utilities                |
-| Configuration  | `references/configuration.md`  | tsconfig options, strict mode, project references            |
-| Patterns       | `references/patterns.md`       | Builder pattern, factory pattern, type-safe APIs             |
-
-## Constraints
+## When to use
 
-### MUST DO
+- Designing type-safe APIs and shared contracts.
+- Refactoring codebases to strict TypeScript.
+- Reducing type regressions in monorepos.
+- Preparing for upcoming TS 6/7 behavior shifts.
 
-- Enable strict mode with all compiler flags
-- Use type-first API design
-- Implement branded types for domain modeling
-- Use `satisfies` operator for type validation
-- Create discriminated unions for state machines
-- Use `Annotated` pattern with type predicates
-- Generate declaration files for libraries
-- Optimize for type inference
+## Core workflow
 
-### MUST NOT DO
+1. Confirm runtime and module target (Node, browser, edge).
+2. Lock strict compiler baseline before feature work.
+3. Model domain types first, then implement behavior.
+4. Keep runtime validation where untrusted input enters.
+5. Run type checks and targeted tests before finishing.
 
-- Use explicit `any` without justification
-- Skip type coverage for public APIs
-- Mix type-only and value imports
-- Disable strict null checks
-- Use `as` assertions without necessity
-- Ignore compiler performance warnings
-- Skip declaration file generation
-- Use enums (prefer const objects with `as const`)
+## Baseline standards
 
-## Output Templates
+- Use `strict: true` and avoid opt-outs unless documented.
+- Prefer `unknown` over `any` at boundaries.
+- Use `satisfies` and `as const` for safer inference.
+- Keep public API types stable and explicit.
+- Use project references for large repos.
 
-When implementing TypeScript features, provide:
+## Implementation guidance
 
-1. Type definitions (interfaces, types, generics)
-2. Implementation with type guards
-3. tsconfig configuration if needed
-4. Brief explanation of type design decisions
+- Encode state with discriminated unions.
+- Narrow with type guards instead of assertions.
+- Keep utility types readable; avoid type-level obfuscation.
+- Use schema validation (zod/valibot/etc.) for external input.
+- Treat type errors as design feedback, not noise.
 
-## Knowledge Reference
+## Avoid
 
-TypeScript 5.0+, generics, conditional types, mapped types, template literal types, discriminated unions, type guards, branded types, tRPC, project references, incremental compilation, declaration files, const assertions, satisfies operator
+- Library-facing `any`.
+- Broad `as` casts to silence errors.
+- Hidden implicit `any` from weak tsconfig defaults.
+- Mixing runtime and type-only imports carelessly.
 
-## Related Powers
+## Reference files
 
-- **React Developer** - Component type safety
-- **Fullstack Guardian** - End-to-end type safety
-- **API Designer** - Type-safe API contracts
+- `references/configuration.md`
+- `references/advanced-types.md`
+- `references/type-guards.md`
+- `references/utility-types.md`
+- `references/patterns.md`

package/workflows/workflows/agent-environment-setup/platforms/antigravity/agents/backend-specialist.md

@@ -3,7 +3,7 @@ name: backend-specialist
 description: Expert backend architect for Node.js, Python, and modern serverless/edge systems. Use for API development, server-side logic, database integration, and security. Triggers on backend, server, api, endpoint, database, auth.
 tools: Read, Grep, Glob, Bash, Edit, Write
 model: inherit
-skills: nodejs-best-practices, api-designer, api-patterns, database-skills, secure-code-guardian, typescript-pro, test-master
+skills: nodejs-best-practices, api-patterns, database-skills, secure-code-guardian
 ---
 
 # Backend Development Architect

package/workflows/workflows/agent-environment-setup/platforms/antigravity/agents/code-archaeologist.md

@@ -3,7 +3,7 @@ name: code-archaeologist
 description: Expert in legacy code, refactoring, and understanding undocumented systems. Use for reading messy code, reverse engineering, and modernization planning. Triggers on legacy, refactor, spaghetti code, analyze repo, explain codebase.
 tools: Read, Grep, Glob, Edit, Write
 model: inherit
-skills: legacy-modernizer, spec-miner, refactor, code-reviewer, feature-forge
+skills: spec-miner, legacy-modernizer, refactor
 ---
 
 # Code Archaeologist

package/workflows/workflows/agent-environment-setup/platforms/antigravity/agents/database-architect.md

@@ -3,7 +3,7 @@ name: database-architect
 description: Expert database architect for schema design, query optimization, migrations, and modern serverless databases. Use for database operations, schema changes, indexing, and data modeling. Triggers on database, sql, schema, migration, query, postgres, index, table.
 tools: Read, Grep, Glob, Bash, Edit, Write
 model: inherit
-skills: database-skills, database-design, database-optimizer, test-master
+skills: database-skills, database-design, database-optimizer
 ---
 
 # Database Architect

package/workflows/workflows/agent-environment-setup/platforms/antigravity/agents/debugger.md

@@ -1,7 +1,7 @@
 ---
 name: debugger
 description: Expert in systematic debugging, root cause analysis, and crash investigation. Use for complex bugs, production issues, performance problems, and error analysis. Triggers on bug, error, crash, not working, broken, investigate, fix.
-skills: systematic-debugging, error-ux-observability, monitoring-expert, find-bugs, test-master
+skills: systematic-debugging, find-bugs, monitoring-expert
 ---
 
 # Debugger - Root Cause Analysis Expert

package/workflows/workflows/agent-environment-setup/platforms/antigravity/agents/devops-engineer.md

@@ -3,7 +3,7 @@ name: devops-engineer
 description: Expert in deployment, server management, CI/CD, and production operations. CRITICAL - Use for deployment, server access, rollback, and production changes. HIGH RISK operations. Triggers on deploy, production, server, pm2, ssh, release, rollback, ci/cd.
 tools: Read, Grep, Glob, Bash, Edit, Write
 model: inherit
-skills: devops-engineer, sre-engineer, monitoring-expert, terraform-engineer, wrangler
+skills: devops-engineer, sre-engineer, monitoring-expert
 ---
 
 # DevOps Engineer

package/workflows/workflows/agent-environment-setup/platforms/antigravity/agents/documentation-writer.md

@@ -3,7 +3,7 @@ name: documentation-writer
 description: Expert in technical documentation. Use ONLY when user explicitly requests documentation (README, API docs, changelog). DO NOT auto-invoke during normal development.
 tools: Read, Grep, Glob, Bash, Edit, Write
 model: inherit
-skills: code-documenter, documentation-templates, openapi-docs, changelog-generator
+skills: code-documenter, documentation-templates
 ---
 
 # Documentation Writer

package/workflows/workflows/agent-environment-setup/platforms/antigravity/agents/explorer-agent.md

@@ -3,7 +3,7 @@ name: explorer-agent
 description: Advanced codebase discovery, deep architectural analysis, and proactive research agent. The eyes and ears of the framework. Use for initial audits, refactoring plans, and deep investigative tasks.
 tools: Read, Grep, Glob, Bash, ViewCodeItem, FindByName
 model: inherit
-skills: spec-miner, architecture-designer, plan-writing, feature-forge
+skills: spec-miner, architecture-designer
 ---
 
 # Explorer Agent - Advanced Discovery & Research

package/workflows/workflows/agent-environment-setup/platforms/antigravity/agents/frontend-specialist.md

@@ -3,7 +3,7 @@ name: frontend-specialist
 description: Senior Frontend Architect who builds maintainable React/Next.js systems with performance-first mindset. Use when working on UI components, styling, state management, responsive design, or frontend architecture. Triggers on keywords like component, react, vue, ui, ux, css, tailwind, responsive.
 tools: Read, Grep, Glob, Bash, Edit, Write
 model: inherit
-skills: react-expert, nextjs-developer, react-best-practices, frontend-design, design-system-builder, accessibility, web-perf, ux-ui-consistency
+skills: react-expert, nextjs-developer, frontend-design, accessibility
 ---
 
 # Senior Frontend Architect

package/workflows/workflows/agent-environment-setup/platforms/antigravity/agents/game-developer.md

@@ -3,7 +3,7 @@ name: game-developer
 description: Game development across all platforms (PC, Web, Mobile, VR/AR). Use when building games with Unity, Godot, Unreal, Phaser, Three.js, or any game engine. Covers game mechanics, multiplayer, optimization, 2D/3D graphics, and game design patterns.
 tools: Read, Write, Edit, Bash, Grep, Glob
 model: inherit
-skills: game-development, javascript-pro, typescript-pro, ui-ux-pro-max
+skills: game-development, javascript-pro
 ---
 
 # Game Developer Agent

package/workflows/workflows/agent-environment-setup/platforms/antigravity/agents/mobile-developer.md

@@ -3,7 +3,7 @@ name: mobile-developer
 description: Expert in React Native and Flutter mobile development. Use for cross-platform mobile apps, native features, and mobile-specific patterns. Triggers on mobile, react native, flutter, ios, android, app store, expo.
 tools: Read, Grep, Glob, Bash, Edit, Write
 model: inherit
-skills: mobile-design, flutter-expert, riverpod-3, gorouter-restoration, drift-flutter, flutter-test-master, accessibility
+skills: mobile-design, flutter-expert, flutter-test-master
 ---
 
 # Mobile Developer