antigravity-ai-kit 2.1.0

package/.agent/skills/frontend-patterns/SKILL.md

@@ -0,0 +1,141 @@
+---
+name: frontend-patterns
+description: Frontend development patterns for React and modern frameworks
+triggers: [context, frontend, react, component, ui]
+---
+
+# Frontend Patterns Skill
+
+> **Purpose**: Apply modern frontend development patterns
+
+---
+
+## Overview
+
+This skill provides best practices for building maintainable, performant frontend applications.
+
+---
+
+## Component Architecture
+
+### Atomic Design
+
+```
+atoms/          → Button, Input, Label
+molecules/      → FormField, SearchInput
+organisms/      → LoginForm, Header
+templates/      → PageLayout, DashboardLayout
+pages/          → LoginPage, DashboardPage
+```
+
+### Feature-Based Structure
+
+```
+src/
+├── features/
+│   ├── auth/
+│   │   ├── components/
+│   │   ├── hooks/
+│   │   ├── api/
+│   │   └── index.ts
+│   └── dashboard/
+│       ├── components/
+│       ├── hooks/
+│       └── index.ts
+├── shared/
+│   ├── components/
+│   ├── hooks/
+│   └── utils/
+└── App.tsx
+```
+
+---
+
+## React Patterns
+
+### Custom Hooks
+
+```tsx
+function useLocalStorage<T>(key: string, initialValue: T) {
+  const [value, setValue] = useState<T>(() => {
+    const stored = localStorage.getItem(key);
+    return stored ? JSON.parse(stored) : initialValue;
+  });
+
+  useEffect(() => {
+    localStorage.setItem(key, JSON.stringify(value));
+  }, [key, value]);
+
+  return [value, setValue] as const;
+}
+```
+
+### Compound Components
+
+```tsx
+<Select value={selected} onChange={setSelected}>
+  <Select.Trigger>Choose option</Select.Trigger>
+  <Select.Options>
+    <Select.Option value="a">Option A</Select.Option>
+    <Select.Option value="b">Option B</Select.Option>
+  </Select.Options>
+</Select>
+```
+
+### Render Props
+
+```tsx
+<DataFetcher url="/api/users">
+  {({ data, loading, error }) =>
+    loading ? <Spinner /> : <UserList users={data} />
+  }
+</DataFetcher>
+```
+
+---
+
+## State Management
+
+| Solution    | Use Case              |
+| :---------- | :-------------------- |
+| useState    | Local component state |
+| useReducer  | Complex local state   |
+| Context     | Theme, auth, i18n     |
+| Zustand     | Simple global state   |
+| Redux       | Complex global state  |
+| React Query | Server state          |
+
+---
+
+## Performance
+
+### Memoization
+
+```tsx
+// Expensive calculation
+const sortedItems = useMemo(
+  () => items.sort((a, b) => a.name.localeCompare(b.name)),
+  [items],
+);
+
+// Callback stability
+const handleClick = useCallback(() => {
+  onClick(id);
+}, [id, onClick]);
+
+// Component memoization
+const UserCard = memo(({ user }) => <div>{user.name}</div>);
+```
+
+---
+
+## Quick Reference
+
+| Pattern      | Usage                  |
+| :----------- | :--------------------- |
+| Custom Hooks | Reusable logic         |
+| Compound     | Flexible APIs          |
+| Render Props | Dynamic rendering      |
+| HOC          | Cross-cutting concerns |
+| Context      | Global state           |
+| Memoization  | Performance            |

package/.agent/skills/git-workflow/SKILL.md

@@ -0,0 +1,159 @@
+---
+name: git-workflow
+description: Git workflow patterns and best practices
+triggers: [context, git, commit, branch, pr]
+---
+
+# Git Workflow Skill
+
+> **Purpose**: Apply professional Git workflows and conventions
+
+---
+
+## Overview
+
+This skill provides Git workflow patterns for professional software development teams.
+
+---
+
+## Branch Strategy
+
+### GitFlow
+
+```
+main         ──●────────────────●──────────●──→
+              ↑                  ↑
+release    ──●─┘               ●─┘
+              ↑                ↑
+develop   ──●──●──●──●──●──●──●──●──●──→
+             ↑     ↑
+feature   ───●─────●
+```
+
+### Trunk-Based
+
+```
+main      ──●──●──●──●──●──●──●──●──→
+             ↑     ↑
+short     ───●     ●  (< 1 day)
+feature
+```
+
+---
+
+## Branch Naming
+
+```
+feature/ABC-123-add-user-auth
+bugfix/ABC-456-fix-login-error
+hotfix/ABC-789-critical-security-patch
+release/v1.2.0
+chore/update-dependencies
+```
+
+---
+
+## Conventional Commits
+
+### Format
+
+```
+<type>(<scope>): <description>
+
+[optional body]
+
+[optional footer(s)]
+```
+
+### Types
+
+| Type       | Usage            |
+| :--------- | :--------------- |
+| `feat`     | New feature      |
+| `fix`      | Bug fix          |
+| `docs`     | Documentation    |
+| `style`    | Formatting       |
+| `refactor` | Code restructure |
+| `test`     | Adding tests     |
+| `chore`    | Maintenance      |
+| `perf`     | Performance      |
+| `ci`       | CI/CD changes    |
+
+### Examples
+
+```bash
+feat(auth): add JWT refresh token support
+
+fix(api): handle null user in profile endpoint
+
+Closes #123
+
+docs(readme): add installation instructions
+
+chore(deps): update dependencies to latest versions
+```
+
+---
+
+## Pull Request Template
+
+```markdown
+## Description
+
+Brief description of changes
+
+## Type of Change
+
+- [ ] Bug fix
+- [ ] New feature
+- [ ] Breaking change
+- [ ] Documentation update
+
+## Checklist
+
+- [ ] Tests pass locally
+- [ ] Code follows style guidelines
+- [ ] Self-reviewed my code
+- [ ] Added necessary documentation
+- [ ] No new warnings
+
+## Testing
+
+How to test these changes
+```
+
+---
+
+## Common Commands
+
+```bash
+# Create feature branch
+git checkout -b feature/ABC-123-new-feature
+
+# Stage and commit
+git add -p                    # Interactive staging
+git commit -m "feat: add..."
+
+# Rebase on main
+git fetch origin
+git rebase origin/main
+
+# Squash commits
+git rebase -i HEAD~3
+
+# Push feature branch
+git push origin feature/ABC-123-new-feature
+```
+
+---
+
+## Quick Reference
+
+| Command                 | Usage                |
+| :---------------------- | :------------------- |
+| `git log --oneline -10` | Recent commits       |
+| `git diff --staged`     | Staged changes       |
+| `git stash`             | Temporary storage    |
+| `git cherry-pick <sha>` | Pick specific commit |
+| `git bisect`            | Find bad commit      |
+| `git reflog`            | Recovery tool        |

package/.agent/skills/intelligent-routing/SKILL.md

@@ -0,0 +1,180 @@
+---
+name: intelligent-routing
+description: Automatic agent selection and intelligent task routing. Analyzes user requests and selects the best specialist agent(s) for Trust-Grade execution.
+version: 1.0.0
+---
+
+# Intelligent Agent Routing
+
+> **Purpose**: Automatically analyze user requests and route them to the most appropriate specialist agent(s) without requiring explicit user mentions.
+
+## Core Principle
+
+> **The AI should act as an intelligent Project Manager**, analyzing each request and automatically selecting the best specialist(s) for the job while maintaining Trust-Grade governance.
+
+---
+
+## How It Works
+
+### 1. Request Analysis
+
+Before responding to ANY user request, perform automatic analysis:
+
+```mermaid
+graph TD
+    A[User Request] --> B[ANALYZE]
+    B --> C[Keywords]
+    B --> D[Domains]
+    B --> E[Complexity]
+    C --> F[SELECT AGENT]
+    D --> F
+    E --> F
+    F --> G[Apply Trust-Grade Context]
+    G --> H[AUTO-INVOKE with governance]
+```
+
+### 2. Agent Selection Matrix
+
+| User Intent       | Keywords                            | Selected Agent(s)          | Auto-invoke? |
+| ----------------- | ----------------------------------- | -------------------------- | ------------ |
+| **Architecture**  | "design", "structure", "pattern"    | `architect`                | ✅ YES       |
+| **Planning**      | "plan", "roadmap", "sprint"         | `planner`                  | ✅ YES       |
+| **Code Review**   | "review", "check", "audit"          | `code-reviewer`            | ✅ YES       |
+| **Security**      | "security", "vulnerability", "auth" | `security-reviewer`        | ✅ YES       |
+| **Testing**       | "test", "coverage", "e2e"           | `tdd-guide` + `e2e-runner` | ✅ YES       |
+| **Build Errors**  | "error", "build", "compile"         | `build-error-resolver`     | ✅ YES       |
+| **Refactoring**   | "refactor", "clean", "improve"      | `refactor-cleaner`         | ✅ YES       |
+| **Documentation** | "docs", "readme", "document"        | `doc-updater`              | ✅ YES       |
+| **Knowledge**     | "learn", "remember", "pattern"      | `knowledge-agent`          | ✅ YES       |
+| **Complex Task**  | Multiple domains detected           | `planner` → multi-agent    | ⚠️ ASK FIRST |
+
+---
+
+## Domain Detection Rules
+
+### Single-Domain Tasks (Auto-invoke Single Agent)
+
+| Domain           | Patterns                              | Agent                      |
+| ---------------- | ------------------------------------- | -------------------------- |
+| **Architecture** | design, pattern, structure, layer     | `architect`                |
+| **Planning**     | plan, task, sprint, milestone         | `planner`                  |
+| **Security**     | auth, jwt, password, vulnerability    | `security-reviewer`        |
+| **Testing**      | test, jest, coverage, e2e, playwright | `tdd-guide` / `e2e-runner` |
+| **Build**        | error, compile, typescript, lint      | `build-error-resolver`     |
+| **Refactor**     | clean, refactor, improve, optimize    | `refactor-cleaner`         |
+| **Docs**         | readme, document, api-docs            | `doc-updater`              |
+
+### Multi-Domain Tasks (Orchestration Required)
+
+If request matches **2+ domains from different categories**, escalate to `planner` for orchestration:
+
+```
+Example: "Create a secure login with tests"
+→ Detected: Security + Testing + Backend
+→ Auto-invoke: planner (orchestration mode)
+→ Planner will handle: security-reviewer, architect, tdd-guide
+```
+
+---
+
+## Complexity Assessment
+
+### SIMPLE (Direct agent invocation)
+
+- Single file edit
+- Clear, specific task
+- One domain only
+- Example: "Fix the TypeScript error in auth.ts"
+
+**Action**: Auto-invoke respective agent
+
+### MODERATE (2-3 agents)
+
+- 2-3 files affected
+- Clear requirements
+- 2 domains max
+- Example: "Add API endpoint with tests"
+
+**Action**: Auto-invoke relevant agents sequentially
+
+### COMPLEX (Orchestration required)
+
+- Multiple files/domains
+- Architectural decisions needed
+- Unclear requirements
+- Example: "Build a new feature vertical"
+
+**Action**: Auto-invoke `planner` → will ask Socratic questions
+
+---
+
+## Implementation Rules
+
+### Rule 1: Silent Analysis
+
+**DO NOT announce "I'm analyzing your request..."**
+
+- ✅ Analyze silently
+- ✅ Inform which agent is being applied
+- ❌ Avoid verbose meta-commentary
+
+### Rule 2: Inform Agent Selection
+
+**DO inform which expertise is being applied:**
+
+```markdown
+🤖 **Applying `@security-reviewer` expertise...**
+
+I will review the authentication implementation with the following focus:
+[Continue with specialized response]
+```
+
+### Rule 3: Trust-Grade Context
+
+**Always apply project governance context:**
+
+- Load relevant governance rules
+- Apply session state context
+- Enforce pre-task checklists
+
+### Rule 4: Override Capability
+
+**User can still explicitly mention agents:**
+
+```
+User: "Use @architect to review this"
+→ Override auto-selection
+→ Use explicitly mentioned agent
+```
+
+---
+
+## Integration with Project Governance
+
+### With Session State
+
+- Check `session-state.json` for active context
+- Inherit project-specific configurations
+- Maintain Trust-Grade continuity
+
+### With Governance Rules
+
+- Apply relevant governance rules
+- Enforce professional standards
+- Maintain project architecture alignment
+
+### With Checklists
+
+- Trigger pre-task checks for complex operations
+- Validate against session-end protocols
+- Ensure documentation updates
+
+---
+
+## Summary
+
+1. **Analyze every request** before responding
+2. **Select best agent(s)** using the matrix
+3. **Inform user** which expertise is applied
+4. **Maintain governance** through Trust-Grade protocols
+5. **Stay seamless** - user shouldn't notice the routing

package/.agent/skills/mobile-design/SKILL.md

@@ -0,0 +1,191 @@
+---
+name: mobile-design
+description: Mobile UI/UX patterns for iOS and Android. Touch-first, platform-respectful design with React Native/Expo focus.
+version: 1.0.0
+allowed-tools: Read, Glob, Grep
+---
+
+# Mobile Design System
+
+> **Philosophy:** Touch-first. Battery-conscious. Platform-respectful. Offline-capable.
+> **Core Principle:** Mobile is NOT a small desktop. THINK mobile constraints, ASK platform choice.
+
+---
+
+## ⚠️ CRITICAL: ASK BEFORE ASSUMING
+
+### You MUST Ask If Not Specified:
+
+- **Platform**: iOS only? Android only? Both?
+- **Framework**: React Native/Expo? Flutter?
+- **Navigation**: Tab-based? Stack? Drawer?
+- **Offline**: Required? Nice-to-have? Not needed?
+
+---
+
+## 📱 Platform Decision Matrix
+
+### When to Unify vs Diverge
+
+```
+                    UNIFY (same on both)          DIVERGE (platform-specific)
+                    ───────────────────           ──────────────────────────
+Business Logic      ✅ Always                     -
+Data Layer          ✅ Always                     -
+Core Features       ✅ Always                     -
+
+Navigation          -                             ✅ iOS: edge swipe, Android: back button
+Gestures            -                             ✅ Platform-native feel
+Icons               -                             ✅ SF Symbols vs Material Icons
+Date Pickers        -                             ✅ Native pickers feel right
+Modals/Sheets       -                             ✅ iOS: bottom sheet vs Android: dialog
+Typography          -                             ✅ SF Pro vs Roboto (or custom)
+```
+
+### Quick Reference: Platform Defaults
+
+| Element              | iOS                       | Android                    |
+| -------------------- | ------------------------- | -------------------------- |
+| **Primary Font**     | SF Pro / SF Compact       | Roboto                     |
+| **Min Touch Target** | 44pt × 44pt               | 48dp × 48dp                |
+| **Back Navigation**  | Edge swipe left           | System back button/gesture |
+| **Bottom Tab Icons** | SF Symbols                | Material Symbols           |
+| **Action Sheet**     | UIActionSheet from bottom | Bottom Sheet / Dialog      |
+| **Progress**         | Spinner                   | Linear progress (Material) |
+
+---
+
+## 🧠 Mobile UX Psychology
+
+### Fitts' Law for Touch
+
+```
+Desktop: Cursor is precise (1px)
+Mobile:  Finger is imprecise (~7mm contact area)
+
+→ Touch targets MUST be 44-48px minimum
+→ Important actions in THUMB ZONE (bottom of screen)
+→ Destructive actions AWAY from easy reach
+```
+
+### Thumb Zone (One-Handed Usage)
+
+```
+┌─────────────────────────────┐
+│      HARD TO REACH          │ ← Navigation, menu, back
+│        (stretch)            │
+├─────────────────────────────┤
+│      OK TO REACH            │ ← Secondary actions
+│       (natural)             │
+├─────────────────────────────┤
+│      EASY TO REACH          │ ← PRIMARY CTAs, tab bar
+│    (thumb's natural arc)    │ ← Main content interaction
+└─────────────────────────────┘
+        [  HOME  ]
+```
+
+### Mobile-Specific Cognitive Load
+
+| Desktop            | Mobile Difference              |
+| ------------------ | ------------------------------ |
+| Multiple windows   | ONE task at a time             |
+| Keyboard shortcuts | Touch gestures                 |
+| Hover states       | NO hover (tap or nothing)      |
+| Large viewport     | Limited space, scroll vertical |
+| Stable attention   | Interrupted constantly         |
+
+---
+
+## ⚡ React Native/Expo Performance
+
+### FlatList Optimization
+
+```typescript
+// ✅ CORRECT: Memoized renderItem + React.memo wrapper
+const ListItem = React.memo(({ item }: { item: Item }) => (
+  <View style={styles.item}>
+    <Text>{item.title}</Text>
+  </View>
+));
+
+const renderItem = useCallback(
+  ({ item }: { item: Item }) => <ListItem item={item} />,
+  []
+);
+
+// ✅ CORRECT: FlatList with all optimizations
+<FlatList
+  data={items}
+  renderItem={renderItem}
+  keyExtractor={(item) => item.id}  // Stable ID, NOT index
+  getItemLayout={(data, index) => ({
+    length: ITEM_HEIGHT,
+    offset: ITEM_HEIGHT * index,
+    index,
+  })}
+  removeClippedSubviews={true}
+  maxToRenderPerBatch={10}
+  windowSize={5}
+/>
+```
+
+### Animation Performance
+
+```
+GPU-accelerated (FAST):     CPU-bound (SLOW):
+├── transform               ├── width, height
+├── opacity                 ├── top, left, right, bottom
+└── (use these ONLY)        ├── margin, padding
+                            └── (AVOID animating these)
+```
+
+---
+
+## 📝 Pre-Development Checklist
+
+### Before Starting ANY Mobile Project
+
+- [ ] Platform(s) confirmed (iOS/Android/Both)
+- [ ] Framework chosen (Expo preferred for BeSync)
+- [ ] Navigation pattern decided
+- [ ] Offline requirements clarified
+- [ ] Design system tokens defined
+
+### Before Every Screen
+
+- [ ] Touch targets ≥ 44pt
+- [ ] Primary actions in thumb zone
+- [ ] Safe area insets handled
+- [ ] Both orientations considered (or locked)
+
+### Before Release
+
+- [ ] Performance profiled
+- [ ] Memory usage checked
+- [ ] Battery impact tested
+- [ ] Accessibility verified
+
+---
+
+## 🔗 BeSync Mobile Stack
+
+| Layer      | Technology                       |
+| ---------- | -------------------------------- |
+| Framework  | Expo (managed workflow)          |
+| Navigation | Expo Router                      |
+| State      | Zustand + React Query            |
+| Storage    | expo-secure-store + AsyncStorage |
+| UI         | Custom + NativeWind (if needed)  |
+
+---
+
+## ❌ Mobile Anti-Patterns
+
+| ❌ Don't                    | ✅ Do                     |
+| --------------------------- | ------------------------- |
+| Assume platform conventions | Ask or detect platform    |
+| Use web-style hover states  | Use pressable feedback    |
+| Put CTAs at top of screen   | Keep CTAs in thumb zone   |
+| Use tiny touch targets      | Minimum 44-48px           |
+| Ignore safe areas           | Always respect insets     |
+| Over-animate                | Subtle, purposeful motion |