antigravity-ide 4.2.0 → 4.2.1

package/.agent/skills/i18n-localization/SKILL.md

@@ -1,9 +1,7 @@
 ---
 name: i18n-localization
-description: Internationalization and localization patterns.
-category: development
-version: 4.1.0-fractal
-layer: master-skill
+description: Internationalization and localization patterns. Detecting hardcoded strings, managing translations, locale files, RTL support.
+allowed-tools: Read, Glob, Grep
 ---
 
 # i18n & Localization
@@ -37,10 +35,120 @@ layer: master-skill
 
 ## 3. Implementation Patterns
 
-## 🧠 Knowledge Modules (Fractal Skills)
+### React (react-i18next)
 
-### 1. [React (react-i18next)](./sub-skills/react-react-i18next.md)
-### 2. [Next.js (next-intl)](./sub-skills/nextjs-next-intl.md)
-### 3. [Python (gettext)](./sub-skills/python-gettext.md)
-### 4. [DO ✅](./sub-skills/do.md)
-### 5. [DON'T ❌](./sub-skills/dont.md)
+```tsx
+import { useTranslation } from 'react-i18next';
+
+function Welcome() {
+  const { t } = useTranslation();
+  return <h1>{t('welcome.title')}</h1>;
+}
+```
+
+### Next.js (next-intl)
+
+```tsx
+import { useTranslations } from 'next-intl';
+
+export default function Page() {
+  const t = useTranslations('Home');
+  return <h1>{t('title')}</h1>;
+}
+```
+
+### Python (gettext)
+
+```python
+from gettext import gettext as _
+
+print(_("Welcome to our app"))
+```
+
+---
+
+## 4. File Structure
+
+```
+locales/
+├── en/
+│   ├── common.json
+│   ├── auth.json
+│   └── errors.json
+├── tr/
+│   ├── common.json
+│   ├── auth.json
+│   └── errors.json
+└── ar/          # RTL
+    └── ...
+```
+
+---
+
+## 5. Best Practices
+
+### DO ✅
+
+- Use translation keys, not raw text
+- Namespace translations by feature
+- Support pluralization
+- Handle date/number formats per locale
+- Plan for RTL from the start
+- Use ICU message format for complex strings
+
+### DON'T ❌
+
+- Hardcode strings in components
+- Concatenate translated strings
+- Assume text length (German is 30% longer)
+- Forget about RTL layout
+- Mix languages in same file
+
+---
+
+## 6. Common Issues
+
+| Issue | Solution |
+|-------|----------|
+| Missing translation | Fallback to default language |
+| Hardcoded strings | Use linter/checker script |
+| Date format | Use Intl.DateTimeFormat |
+| Number format | Use Intl.NumberFormat |
+| Pluralization | Use ICU message format |
+
+---
+
+## 7. RTL Support
+
+```css
+/* CSS Logical Properties */
+.container {
+  margin-inline-start: 1rem;  /* Not margin-left */
+  padding-inline-end: 1rem;   /* Not padding-right */
+}
+
+[dir="rtl"] .icon {
+  transform: scaleX(-1);
+}
+```
+
+---
+
+## 8. Checklist
+
+Before shipping:
+
+- [ ] All user-facing strings use translation keys
+- [ ] Locale files exist for all supported languages
+- [ ] Date/number formatting uses Intl API
+- [ ] RTL layout tested (if applicable)
+- [ ] Fallback language configured
+- [ ] No hardcoded strings in components
+
+---
+
+## Script
+
+| Script | Purpose | Command |
+|--------|---------|---------|
+| `scripts/i18n_checker.py` | Detect hardcoded strings & missing translations | `python scripts/i18n_checker.py <project_path>` |

package/.agent/skills/incident-responder/SKILL.md

@@ -1,9 +1,11 @@
 ---
 name: incident-responder
-description: Expert SRE incident responder specializing in rapid problem resolution.
-category: infrastructure
-version: 4.1.0-fractal
-layer: master-skill
+description: >
+  Expert SRE incident responder specializing in rapid problem resolution, 
+  modern observability, and comprehensive incident management. Masters 
+  incident command, blameless post-mortems, error budget management, 
+  and system reliability patterns. Handles critical outages, communication 
+  strategies, and continuous improvement.
 ---
 
 # 🚨 Incident Responder Master Kit
@@ -69,8 +71,3 @@ You are an **Elite SRE and Incident Commander**. Your mission is to restore serv
 
 ---
 *Merged and optimized from 5 legacy incident response skills.*
-
-
-## 🧠 Knowledge Modules (Fractal Skills)
-
-### 1. [incident_severity_levels](./sub-skills/incident_severity_levels.md)

package/.agent/skills/legacy-modernizer/SKILL.md

@@ -1,9 +1,9 @@
 ---
 name: legacy-modernizer
-description: Refactor legacy codebases, migrate outdated frameworks, and implement gradual modernization.
-category: development
-version: 4.1.0-fractal
-layer: master-skill
+description: >
+  Refactor legacy codebases, migrate outdated frameworks, and implement gradual 
+  modernization. Handles technical debt, dependency updates, and backward compatibility. 
+  Uses the Strangler Fig pattern for safe transitions.
 ---
 
 # 🏛️ Legacy Modernizer Master Kit
@@ -66,8 +66,3 @@ You are a **Principal Modernization Engineer and Software Strategist**. You tran
 
 ---
 *Merged and optimized from 5 legacy modernization and migration skills.*
-
-
-## 🧠 Knowledge Modules (Fractal Skills)
-
-### 1. [strangler_fig_pattern](./sub-skills/strangler_fig_pattern.md)

package/.agent/skills/lint-and-validate/scripts/lint_runner.py

@@ -14,6 +14,8 @@ Supports:
 import subprocess
 import sys
 import json
+import platform
+import shutil
 from pathlib import Path
 from datetime import datetime
 
@@ -77,14 +79,24 @@ def run_linter(linter: dict, cwd: Path) -> dict:
     }
     
     try:
+        cmd = linter["cmd"]
+        
+        # Windows compatibility for npm/npx
+        if platform.system() == "Windows":
+            if cmd[0] in ["npm", "npx"]:
+                # Force .cmd extension on Windows
+                if not cmd[0].lower().endswith(".cmd"):
+                    cmd[0] = f"{cmd[0]}.cmd"
+        
         proc = subprocess.run(
-            linter["cmd"],
+            cmd,
             cwd=str(cwd),
             capture_output=True,
             text=True,
             encoding='utf-8',
             errors='replace',
-            timeout=120
+            timeout=120,
+            shell=platform.system() == "Windows" # Shell=True often helps with path resolution on Windows
         )
         
         result["output"] = proc.stdout[:2000] if proc.stdout else ""

package/.agent/skills/mcp-builder/SKILL.md

@@ -1,9 +1,7 @@
 ---
 name: mcp-builder
-description: MCP (Model Context Protocol) server building principles.
-category: tools
-version: 4.1.0-fractal
-layer: master-skill
+description: MCP (Model Context Protocol) server building principles. Tool design, resource patterns, best practices.
+allowed-tools: Read, Write, Edit, Glob, Grep
 ---
 
 # MCP Builder
@@ -14,20 +12,165 @@ layer: master-skill
 
 ## 1. MCP Overview
 
-## 🧠 Knowledge Modules (Fractal Skills)
-
-### 1. [What is MCP?](./sub-skills/what-is-mcp.md)
-### 2. [Core Concepts](./sub-skills/core-concepts.md)
-### 3. [Project Structure](./sub-skills/project-structure.md)
-### 4. [Transport Types](./sub-skills/transport-types.md)
-### 5. [Good Tool Design](./sub-skills/good-tool-design.md)
-### 6. [Input Schema Design](./sub-skills/input-schema-design.md)
-### 7. [Resource Types](./sub-skills/resource-types.md)
-### 8. [URI Patterns](./sub-skills/uri-patterns.md)
-### 9. [Error Types](./sub-skills/error-types.md)
-### 10. [Best Practices](./sub-skills/best-practices.md)
-### 11. [Supported Types](./sub-skills/supported-types.md)
-### 12. [Input Validation](./sub-skills/input-validation.md)
-### 13. [API Keys](./sub-skills/api-keys.md)
-### 14. [Claude Desktop Config](./sub-skills/claude-desktop-config.md)
-### 15. [Test Categories](./sub-skills/test-categories.md)
+### What is MCP?
+
+Model Context Protocol - standard for connecting AI systems with external tools and data sources.
+
+### Core Concepts
+
+| Concept | Purpose |
+|---------|---------|
+| **Tools** | Functions AI can call |
+| **Resources** | Data AI can read |
+| **Prompts** | Pre-defined prompt templates |
+
+---
+
+## 2. Server Architecture
+
+### Project Structure
+
+```
+my-mcp-server/
+├── src/
+│   └── index.ts      # Main entry
+├── package.json
+└── tsconfig.json
+```
+
+### Transport Types
+
+| Type | Use |
+|------|-----|
+| **Stdio** | Local, CLI-based |
+| **SSE** | Web-based, streaming |
+| **WebSocket** | Real-time, bidirectional |
+
+---
+
+## 3. Tool Design Principles
+
+### Good Tool Design
+
+| Principle | Description |
+|-----------|-------------|
+| Clear name | Action-oriented (get_weather, create_user) |
+| Single purpose | One thing well |
+| Validated input | Schema with types and descriptions |
+| Structured output | Predictable response format |
+
+### Input Schema Design
+
+| Field | Required? |
+|-------|-----------|
+| Type | Yes - object |
+| Properties | Define each param |
+| Required | List mandatory params |
+| Description | Human-readable |
+
+---
+
+## 4. Resource Patterns
+
+### Resource Types
+
+| Type | Use |
+|------|-----|
+| Static | Fixed data (config, docs) |
+| Dynamic | Generated on request |
+| Template | URI with parameters |
+
+### URI Patterns
+
+| Pattern | Example |
+|---------|---------|
+| Fixed | `docs://readme` |
+| Parameterized | `users://{userId}` |
+| Collection | `files://project/*` |
+
+---
+
+## 5. Error Handling
+
+### Error Types
+
+| Situation | Response |
+|-----------|----------|
+| Invalid params | Validation error message |
+| Not found | Clear "not found" |
+| Server error | Generic error, log details |
+
+### Best Practices
+
+- Return structured errors
+- Don't expose internal details
+- Log for debugging
+- Provide actionable messages
+
+---
+
+## 6. Multimodal Handling
+
+### Supported Types
+
+| Type | Encoding |
+|------|----------|
+| Text | Plain text |
+| Images | Base64 + MIME type |
+| Files | Base64 + MIME type |
+
+---
+
+## 7. Security Principles
+
+### Input Validation
+
+- Validate all tool inputs
+- Sanitize user-provided data
+- Limit resource access
+
+### API Keys
+
+- Use environment variables
+- Don't log secrets
+- Validate permissions
+
+---
+
+## 8. Configuration
+
+### Claude Desktop Config
+
+| Field | Purpose |
+|-------|---------|
+| command | Executable to run |
+| args | Command arguments |
+| env | Environment variables |
+
+---
+
+## 9. Testing
+
+### Test Categories
+
+| Type | Focus |
+|------|-------|
+| Unit | Tool logic |
+| Integration | Full server |
+| Contract | Schema validation |
+
+---
+
+## 10. Best Practices Checklist
+
+- [ ] Clear, action-oriented tool names
+- [ ] Complete input schemas with descriptions
+- [ ] Structured JSON output
+- [ ] Error handling for all cases
+- [ ] Input validation
+- [ ] Environment-based configuration
+- [ ] Logging for debugging
+
+---
+
+> **Remember:** MCP tools should be simple, focused, and well-documented. The AI relies on descriptions to use them correctly.