npm - antigravity-ide - Versions diffs - 4.2.1 → 4.3.3 - Mend

antigravity-ide 4.2.1 → 4.3.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (359) hide show

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

@@ -1,7 +1,9 @@
 ---
 name: mcp-builder
-description: MCP (Model Context Protocol) server building principles. Tool design, resource patterns, best practices.
-allowed-tools: Read, Write, Edit, Glob, Grep
+description: MCP (Model Context Protocol) server building principles.
+category: tools
+version: 4.1.0-fractal
+layer: master-skill
 ---
 # MCP Builder
@@ -12,165 +14,20 @@ allowed-tools: Read, Write, Edit, Glob, Grep
 ## 1. MCP Overview
-### 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.
+## 🧠 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)

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

@@ -1,7 +1,9 @@
 ---
 name: mobile-design
-description: Mobile-first design thinking and decision-making for iOS and Android apps. Touch interaction, performance patterns, platform conventions. Teaches principles, not fixed values. Use when building React Native, Flutter, or native mobile apps.
-allowed-tools: Read, Glob, Grep, Bash
+description: Mobile-first design thinking and decision-making for iOS and Android apps.
+category: design
+version: 4.1.0-fractal
+layer: master-skill
 ---
 # Mobile Design System
@@ -25,370 +27,20 @@ allowed-tools: Read, Glob, Grep, Bash
 **⛔ DO NOT start development until you read the relevant files:**
-### Universal (Always Read)
-| File | Content | Status |
-|------|---------|--------|
-| **[mobile-design-thinking.md](mobile-design-thinking.md)** | **⚠️ ANTI-MEMORIZATION: Forces thinking, prevents AI defaults** | **⬜ CRITICAL FIRST** |
-| **[touch-psychology.md](touch-psychology.md)** | **Fitts' Law, gestures, haptics, thumb zone** | **⬜ CRITICAL** |
-| **[mobile-performance.md](mobile-performance.md)** | **RN/Flutter performance, 60fps, memory** | **⬜ CRITICAL** |
-| **[mobile-backend.md](mobile-backend.md)** | **Push notifications, offline sync, mobile API** | **⬜ CRITICAL** |
-| **[mobile-testing.md](mobile-testing.md)** | **Testing pyramid, E2E, platform-specific** | **⬜ CRITICAL** |
-| **[mobile-debugging.md](mobile-debugging.md)** | **Native vs JS debugging, Flipper, Logcat** | **⬜ CRITICAL** |
-| [mobile-navigation.md](mobile-navigation.md) | Tab/Stack/Drawer, deep linking | ⬜ Read |
-| [mobile-typography.md](mobile-typography.md) | System fonts, Dynamic Type, a11y | ⬜ Read |
-| [mobile-color-system.md](mobile-color-system.md) | OLED, dark mode, battery-aware | ⬜ Read |
-| [decision-trees.md](decision-trees.md) | Framework/state/storage selection | ⬜ Read |
-> 🧠 **mobile-design-thinking.md is PRIORITY!** This file ensures AI thinks instead of using memorized patterns.
-### Platform-Specific (Read Based on Target)
-| Platform | File | Content | When to Read |
-|----------|------|---------|--------------|
-| **iOS** | [platform-ios.md](platform-ios.md) | Human Interface Guidelines, SF Pro, SwiftUI patterns | Building for iPhone/iPad |
-| **Android** | [platform-android.md](platform-android.md) | Material Design 3, Roboto, Compose patterns | Building for Android |
-| **Cross-Platform** | Both above | Platform divergence points | React Native / Flutter |
-> 🔴 **If building for iOS → Read platform-ios.md FIRST!**
-> 🔴 **If building for Android → Read platform-android.md FIRST!**
-> 🔴 **If cross-platform → Read BOTH and apply conditional platform logic!**
----
-## ⚠️ CRITICAL: ASK BEFORE ASSUMING (MANDATORY)
-> **STOP! If the user's request is open-ended, DO NOT default to your favorites.**
-### You MUST Ask If Not Specified:
-| Aspect | Ask | Why |
-|--------|-----|-----|
-| **Platform** | "iOS, Android, or both?" | Affects EVERY design decision |
-| **Framework** | "React Native, Flutter, or native?" | Determines patterns and tools |
-| **Navigation** | "Tab bar, drawer, or stack-based?" | Core UX decision |
-| **State** | "What state management? (Zustand/Redux/Riverpod/BLoC?)" | Architecture foundation |
-| **Offline** | "Does this need to work offline?" | Affects data strategy |
-| **Target devices** | "Phone only, or tablet support?" | Layout complexity |
-### ⛔ AI MOBILE ANTI-PATTERNS (YASAK LİSTESİ)
-> 🚫 **These are AI default tendencies that MUST be avoided!**
-#### Performance Sins
-| ❌ NEVER DO | Why It's Wrong | ✅ ALWAYS DO |
-|-------------|----------------|--------------|
-| **ScrollView for long lists** | Renders ALL items, memory explodes | Use `FlatList` / `FlashList` / `ListView.builder` |
-| **Inline renderItem function** | New function every render, all items re-render | `useCallback` + `React.memo` |
-| **Missing keyExtractor** | Index-based keys cause bugs on reorder | Unique, stable ID from data |
-| **Skip getItemLayout** | Async layout = janky scroll | Provide when items have fixed height |
-| **setState() everywhere** | Unnecessary widget rebuilds | Targeted state, `const` constructors |
-| **Native driver: false** | Animations blocked by JS thread | `useNativeDriver: true` always |
-| **console.log in production** | Blocks JS thread severely | Remove before release build |
-| **Skip React.memo/const** | Every item re-renders on any change | Memoize list items ALWAYS |
-#### Touch/UX Sins
-| ❌ NEVER DO | Why It's Wrong | ✅ ALWAYS DO |
-|-------------|----------------|--------------|
-| **Touch target < 44px** | Impossible to tap accurately, frustrating | Minimum 44pt (iOS) / 48dp (Android) |
-| **Spacing < 8px between targets** | Accidental taps on neighbors | Minimum 8-12px gap |
-| **Gesture-only interactions** | Motor impaired users excluded | Always provide button alternative |
-| **No loading state** | User thinks app crashed | ALWAYS show loading feedback |
-| **No error state** | User stuck, no recovery path | Show error with retry option |
-| **No offline handling** | Crash/block when network lost | Graceful degradation, cached data |
-| **Ignore platform conventions** | Users confused, muscle memory broken | iOS feels iOS, Android feels Android |
-#### Security Sins
-| ❌ NEVER DO | Why It's Wrong | ✅ ALWAYS DO |
-|-------------|----------------|--------------|
-| **Token in AsyncStorage** | Easily accessible, stolen on rooted device | `SecureStore` / `Keychain` / `EncryptedSharedPreferences` |
-| **Hardcode API keys** | Reverse engineered from APK/IPA | Environment variables, secure storage |
-| **Skip SSL pinning** | MITM attacks possible | Pin certificates in production |
-| **Log sensitive data** | Logs can be extracted | Never log tokens, passwords, PII |
-#### Architecture Sins
-| ❌ NEVER DO | Why It's Wrong | ✅ ALWAYS DO |
-|-------------|----------------|--------------|
-| **Business logic in UI** | Untestable, unmaintainable | Service layer separation |
-| **Global state for everything** | Unnecessary re-renders, complexity | Local state default, lift when needed |
-| **Deep linking as afterthought** | Notifications, shares broken | Plan deep links from day one |
-| **Skip dispose/cleanup** | Memory leaks, zombie listeners | Clean up subscriptions, timers |
----
-## 📱 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)
-Error Dialogs       -                             ✅ Platform conventions for alerts
-```
-### 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) |
-| **Pull to Refresh** | Native UIRefreshControl | SwipeRefreshLayout |
----
-## 🧠 Mobile UX Psychology (Quick Reference)
-### 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 |
-For deep dive: [touch-psychology.md](touch-psychology.md)
----
-## ⚡ Performance Principles (Quick Reference)
-### React Native Critical Rules
-```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}
-/>
-```
-### Flutter Critical Rules
-```dart
-// ✅ CORRECT: const constructors prevent rebuilds
-class MyWidget extends StatelessWidget {
-  const MyWidget({super.key}); // CONST!
-  @override
-  Widget build(BuildContext context) {
-    return const Column( // CONST!
-      children: [
-        Text('Static content'),
-        MyConstantWidget(),
-      ],
-    );
-  }
-}
-// ✅ CORRECT: Targeted state with ValueListenableBuilder
-ValueListenableBuilder<int>(
-  valueListenable: counter,
-  builder: (context, value, child) => Text('$value'),
-  child: const ExpensiveWidget(), // Won't rebuild!
-)
-```
-### Animation Performance
-```
-GPU-accelerated (FAST):     CPU-bound (SLOW):
-├── transform               ├── width, height
-├── opacity                 ├── top, left, right, bottom
-└── (use these ONLY)        ├── margin, padding
-                            └── (AVOID animating these)
-```
-For complete guide: [mobile-performance.md](mobile-performance.md)
----
-## 📝 CHECKPOINT (MANDATORY Before Any Mobile Work)
-> **Before writing ANY mobile code, you MUST complete this checkpoint:**
-```
-🧠 CHECKPOINT:
-Platform:   [ iOS / Android / Both ]
-Framework:  [ React Native / Flutter / SwiftUI / Kotlin ]
-Files Read: [ List the skill files you've read ]
-3 Principles I Will Apply:
-1. _______________
-2. _______________
-3. _______________
-Anti-Patterns I Will Avoid:
-1. _______________
-2. _______________
-```
-**Example:**
-```
-🧠 CHECKPOINT:
-Platform:   iOS + Android (Cross-platform)
-Framework:  React Native + Expo
-Files Read: touch-psychology.md, mobile-performance.md, platform-ios.md, platform-android.md
-3 Principles I Will Apply:
-1. FlatList with React.memo + useCallback for all lists
-2. 48px touch targets, thumb zone for primary CTAs
-3. Platform-specific navigation (edge swipe iOS, back button Android)
-Anti-Patterns I Will Avoid:
-1. ScrollView for lists → FlatList
-2. Inline renderItem → Memoized
-3. AsyncStorage for tokens → SecureStore
-```
-> 🔴 **Can't fill the checkpoint? → GO BACK AND READ THE SKILL FILES.**
----
-## 🔧 Framework Decision Tree
-```
-WHAT ARE YOU BUILDING?
-        │
-        ├── Need OTA updates + rapid iteration + web team
-        │   └── ✅ React Native + Expo
-        │
-        ├── Need pixel-perfect custom UI + performance critical
-        │   └── ✅ Flutter
-        │
-        ├── Deep native features + single platform focus
-        │   ├── iOS only → SwiftUI
-        │   └── Android only → Kotlin + Jetpack Compose
-        │
-        ├── Existing RN codebase + new features
-        │   └── ✅ React Native (bare workflow)
-        │
-        └── Enterprise + existing Flutter codebase
-            └── ✅ Flutter
-```
-For complete decision trees: [decision-trees.md](decision-trees.md)
----
-## 📋 Pre-Development Checklist
-### Before Starting ANY Mobile Project
-- [ ] **Platform confirmed?** (iOS / Android / Both)
-- [ ] **Framework chosen?** (RN / Flutter / Native)
-- [ ] **Navigation pattern decided?** (Tabs / Stack / Drawer)
-- [ ] **State management selected?** (Zustand / Redux / Riverpod / BLoC)
-- [ ] **Offline requirements known?**
-- [ ] **Deep linking planned from day one?**
-- [ ] **Target devices defined?** (Phone / Tablet / Both)
-### Before Every Screen
-- [ ] **Touch targets ≥ 44-48px?**
-- [ ] **Primary CTA in thumb zone?**
-- [ ] **Loading state exists?**
-- [ ] **Error state with retry exists?**
-- [ ] **Offline handling considered?**
-- [ ] **Platform conventions followed?**
-### Before Release
-- [ ] **console.log removed?**
-- [ ] **SecureStore for sensitive data?**
-- [ ] **SSL pinning enabled?**
-- [ ] **Lists optimized (memo, keyExtractor)?**
-- [ ] **Memory cleanup on unmount?**
-- [ ] **Tested on low-end devices?**
-- [ ] **Accessibility labels on all interactive elements?**
----
-## 📚 Reference Files
-For deeper guidance on specific areas:
-| File | When to Use |
-|------|-------------|
-| [mobile-design-thinking.md](mobile-design-thinking.md) | **FIRST! Anti-memorization, forces context-based thinking** |
-| [touch-psychology.md](touch-psychology.md) | Understanding touch interaction, Fitts' Law, gesture design |
-| [mobile-performance.md](mobile-performance.md) | Optimizing RN/Flutter, 60fps, memory/battery |
-| [platform-ios.md](platform-ios.md) | iOS-specific design, HIG compliance |
-| [platform-android.md](platform-android.md) | Android-specific design, Material Design 3 |
-| [mobile-navigation.md](mobile-navigation.md) | Navigation patterns, deep linking |
-| [mobile-typography.md](mobile-typography.md) | Type scale, system fonts, accessibility |
-| [mobile-color-system.md](mobile-color-system.md) | OLED optimization, dark mode, battery |
-| [decision-trees.md](decision-trees.md) | Framework, state, storage decisions |
----
-> **Remember:** Mobile users are impatient, interrupted, and using imprecise fingers on small screens. Design for the WORST conditions: bad network, one hand, bright sun, low battery. If it works there, it works everywhere.
+## 🧠 Knowledge Modules (Fractal Skills)
+### 1. [Universal (Always Read)](./sub-skills/universal-always-read.md)
+### 2. [Platform-Specific (Read Based on Target)](./sub-skills/platform-specific-read-based-on-target.md)
+### 3. [You MUST Ask If Not Specified:](./sub-skills/you-must-ask-if-not-specified.md)
+### 4. [⛔ AI MOBILE ANTI-PATTERNS (YASAK LİSTESİ)](./sub-skills/ai-mobile-anti-patterns-yasak-listesi.md)
+### 5. [When to Unify vs Diverge](./sub-skills/when-to-unify-vs-diverge.md)
+### 6. [Quick Reference: Platform Defaults](./sub-skills/quick-reference-platform-defaults.md)
+### 7. [Fitts' Law for Touch](./sub-skills/fitts-law-for-touch.md)
+### 8. [Thumb Zone (One-Handed Usage)](./sub-skills/thumb-zone-one-handed-usage.md)
+### 9. [Mobile-Specific Cognitive Load](./sub-skills/mobile-specific-cognitive-load.md)
+### 10. [React Native Critical Rules](./sub-skills/react-native-critical-rules.md)
+### 11. [Flutter Critical Rules](./sub-skills/flutter-critical-rules.md)
+### 12. [Animation Performance](./sub-skills/animation-performance.md)
+### 13. [Before Starting ANY Mobile Project](./sub-skills/before-starting-any-mobile-project.md)
+### 14. [Before Every Screen](./sub-skills/before-every-screen.md)
+### 15. [Before Release](./sub-skills/before-release.md)

package/.agent/skills/mobile-design/mobile-performance.md CHANGED Viewed

@@ -498,7 +498,7 @@ Everything else causes layout recalculation.
 | Micro-interaction | 100-200ms | ease-out |
 | Standard transition | 200-300ms | ease-out |
 | Page transition | 300-400ms | ease-in-out |
-| Complex/dramatic | 400-600ms | ease-in-out |
+| Complex/dramatic | 4.0.800ms | ease-in-out |
 | Loading skeletons | 1000-1500ms | linear (loop) |
 ### Spring Physics

package/.agent/skills/modern-web-architect/SKILL.md CHANGED Viewed

@@ -1,8 +1,9 @@
 ---
 name: modern-web-architect
-description: >
-  Master Frontend & Web Architecture. Combines React 19, Next.js 15, App Router,
-  State Management, and High-Craft UI Design. Includes FFCI and DFII evaluation frameworks.
+description: Master Frontend & Web Architecture.
+category: architecture
+version: 4.1.0-fractal
+layer: master-skill
 ---
 # 🌐 Modern Web Architect (Master Skill)
@@ -34,6 +35,8 @@ Before coding, calculate the **Frontend Feasibility & Complexity Index (FFCI)**:
 ## 2. React 19 & Next.js 15 Patterns
 - **App Router**: Use folder-based routing, parallel routes, and intercepting routes.
 - **Server Components (RSC)**: Default to Server Components for data fetching. Use `'use client'` only for interactivity.
+- **Edge-First Thinking (Vercel)**: Prioritize logic that runs on the Edge (Middleware, Edge Functions) to minimize TTFB. Use Edge Runtime for high-performance dynamic routing.
+- **Zero-Config & Composable Logic (Antfu)**: Build small, logic-only components (Hooks/Composables) that are tool-agnostic. Prefer `Vite` for development and `Vitest` for lightening-fast testing.
 - **New Hooks**: Leverage `useActionState`, `useOptimistic`, and the `use` API.
 - **Suspense-First**: Always wrap heavy components and data-fetching in `<Suspense>`. **No manual `isLoading` flags.**
@@ -46,6 +49,7 @@ Before coding, calculate the **Frontend Feasibility & Complexity Index (FFCI)**:
   - `Zustand` for complex global state.
   - `Context` for subtree configuration.
 - **Doctrine**: "Props down, Actions up."
+- **Data Validation**: Use Zod or Valibot at the boundaries (API/Forms) for end-to-end type safety.
 ---
@@ -57,16 +61,18 @@ Evaluate via **Design Feasibility & Impact Index (DFII)**:
 - **Mandate**:
   - ❌ No generic "AI UI" or default Tailwind/ShadCN layouts.
-  - ✅ Custom typography, purposeful motion, and textured depth.
-  - ✅ One "Memorable Anchor" per page.
+  - ✅ Custom typography, purposeful motion (Framer Motion), and textured depth.
+  - ✅ One "Memorable Anchor" per page (Magic UI component e.g., Bento Grid).
 ---
 ## 5. Performance & Optimization
+- **Vercel Performance**: Implement ISR (Incremental Static Regeneration) and PPR (Partial Prerendering) where possible.
+- **Turborepo Master**: Use intelligent caching to speed up builds and tests in monorepos.
 - **Code Splitting**: Dynamic imports (`React.lazy`) for heavy modules.
 - **Rendering**: Optimize for Core Web Vitals (LCP < 2.5s, CLS < 0.1).
 - **Images**: Use Next.js `<Image>` for automatic optimization.
-- **Bundle**: Audit dependencies to avoid bloat.
+- **Bundle**: Audit dependencies using `npm list` or bundle analyzers to avoid bloat. Prefer lightweight libraries (e.g., `lucide-react` over `font-awesome`).
 ---

package/.agent/skills/nextjs-react-expert/scripts/convert_rules.py CHANGED Viewed

@@ -187,7 +187,7 @@ def main():
     # Paths
     base_dir = Path(__file__).parent.parent.parent.parent.parent
     rules_dir = base_dir / "others/agent-skills/skills/react-best-practices/rules"
-    output_dir = base_dir / ".agent/skills/react-best-practices"
+    output_dir = base_dir / ".agent/skills/nextjs-react-expert"
     print(f"[*] Reading rules from: {rules_dir}")
     print(f"[*] Output to: {output_dir}")

package/.agent/skills/penetration-tester-master/SKILL.md CHANGED Viewed

@@ -1,9 +1,9 @@
 ---
 name: penetration-tester-master
-description: >
-  Ultimate Offensive Security Master Skill. Covers Ethical Hacking Methodology,
-  Infrastructure Attacks (AD, AWS), Web Vulnerabilities (OWASP Top 10, Bug Bounty),
-  and Advanced Toolsets (Metasploit, Burp Suite, SQLMap).
+description: Ultimate Offensive Security Master Skill.
+category: security
+version: 4.1.0-fractal
+layer: master-skill
 ---
 # 🗡️ Penetration Tester Master Kit
@@ -73,3 +73,8 @@ You are an **Elite Red Team Lead and Professional Pentester**. This skill provid
 ---
 *Merged and optimized from 25 legacy offensive security and tool-specific skills.*
+## 🧠 Knowledge Modules (Fractal Skills)
+### 1. [owasp_top_10_2025](./sub-skills/owasp_top_10_2025.md)