anchi-kit 1.2.1 → 1.2.2

package/.antigravity/skills/_packs/data/pack-data-science.md

@@ -1,36 +0,0 @@
-# Pack: Data Science
-
-Tier: Domain
-Load Cost: High
-Keywords: python, pandas, numpy, visualization, analysis, machine-learning, plot
-
-## Scope
-
-This pack covers **Deep Data Science and Analysis**.
-
-- **Includes**: Data manipulation (Pandas/Polars), Visualization (Matplotlib/Seaborn), Statistical Analysis, Basic ML (Scikit-learn).
-- **Primary Lang**: Python (assumed execution environment or script generation).
-
-## Canonical Patterns (Best Practices)
-
-### 1. Data Pipeline
-
-- **ETL**: Extract -> Transform -> Load. Clean data before analysis.
-- **Vectorization**: Use Pandas/NumPy vector operations, avoid Python loops.
-- **Reproducibility**: Use Jupyter Notebooks or scripts with seed fixing.
-
-### 2. Visualization
-
-- **Clarity**: Label axes, titles, and legends.
-- **Color**: Use accessible color palettes.
-- **Context**: Annotate outliers or key events.
-
-## Anti-Patterns (What to Avoid)
-
-- ❌ **Mutating Data**: Modifying DataFrames in-place implicitly.
-- ❌ **Magic Numbers**: Hardcoding boundaries without explanation.
-- ❌ **Overfitting**: training on test data.
-
-## Load Confirmation
-
-> Rule: If you use this pack, you must explicitly state: "Loaded Data Science Pack."

package/.antigravity/skills/_packs/mobile/pack-mobile.md

@@ -1,40 +0,0 @@
-# Pack: Mobile
-
-Tier: Domain
-Load Cost: Medium
-Keywords: react-native, expo, ios, android, mobile
-
-## Scope
-
-This pack covers **Mobile App Development** using React Native and Expo.
-
-- **Includes**: Native Components, Navigation (React Navigation/Expo Router), native modules, platform-specific code.
-- **Excludes**: Pure web components (DOM-based).
-
-## Canonical Patterns (Best Practices)
-
-### 1. Framework
-
-- **Expo Framework**: Preferred for new projects (File-based routing, Prebuild).
-- **NativeWind**: Tailwind CSS for React Native.
-
-### 2. Components
-
-- **Core Components**: Use `<View>`, `<Text>`, `<Pressable>` (not `<div>`, `<span>`).
-- **Lists**: Use `<FlatList>` or `<FlashList>` for long lists (virtualization).
-- **Images**: Use `expo-image` for caching and performance.
-
-### 3. Navigation
-
-- **Architecture**: Stack Navigator for flows, Tab Navigator for main shell.
-- **Deep Linking**: Configure schemes for external access.
-
-## Anti-Patterns (What to Avoid)
-
-- ❌ **Web-only APIs**: Using `window`, `document`, or `localStorage` (Use `AsyncStorage`).
-- ❌ **Blocking JS Thread**: Heavy computations on UI thread. Use Worklets (Reanimated).
-- ❌ **Unoptimized Images**: Loading huge raw images.
-
-## Load Confirmation
-
-> Rule: If you use this pack, you must explicitly state: "Loaded Mobile Pack."

package/.antigravity/skills/_packs/web/pack-backend.md

@@ -1,61 +0,0 @@
-# Pack: Backend
-
-Tier: Domain
-Load Cost: High
-Keywords: node, api, database, auth, payment, backend, server
-
-## Scope
-
-This pack covers **Backend Development** logic, API design, and Data Management.
-
-- **Includes**: API endpoints (Next.js App Router), Database interactions (Prisma/Drizzle), Authentication (Auth.js), Payments (Stripe), Business Logic.
-- **Excludes**: UI components, detailed DevOps/Infrastructure (see `pack-devops`).
-
-## Canonical Patterns (Best Practices)
-
-### 1. API Design
-
-- **Resource Oriented**: `GET /api/users`, `POST /api/users`.
-- **Validation**: Use Zod for all request body/param validation.
-- **Error Handling**: Return structured errors `{ code, message, details }`.
-- **Type Safety**: Share types between Backend and Frontend (Monorepo/RPC).
-
-### 2. Database Interactions
-
-- **ORM**: Use Prisma or Drizzle.
-- **Migrations**: Always verify migrations locally before commit.
-- **Indexing**: Add indexes for foreign keys and frequently searched columns.
-- **Connection Pooling**: Use connection pooling for Serverless environments.
-
-### 3. Authentication & Security
-
-- **Auth.js / Better-Auth**: Standard implementations preferred.
-- **Middleware**: Protect routes via middleware, not just client-side checks.
-- **RBAC**: Implement Role-Based Access Control logic in services.
-- **Secrets**: Never commit `.env`. Access via `process.env`.
-
-### 4. Payments (Stripe)
-
-- **Webhooks**: Always verify webhook signatures securely.
-- **Idempotency**: Handle duplicate webhook events gracefully.
-- **Client/Server Split**: Create PaymentIntent on server, confirm on client.
-
-## Anti-Patterns (What to Avoid)
-
-- ❌ **Logic in Controllers**: Keep Route Handlers thin; move logic to Services/UseCases.
-- ❌ **N+1 Queries**: Loop queries inside loops. Use `include` or `Promise.all`.
-- ❌ **Trusting Client**: Never trust `req.body` without Zod validation.
-- ❌ **SQL Injection**: Never concat strings for queries. Use ORM or parametrized queries.
-- ❌ **Hardcoded IDs**: Do not rely on specific DB IDs in logic.
-
-## Specialized Modules
-
-### Shopify Integration
-
-- Use Shopify Admin API / Storefront API.
-- Respect rate limits.
-- Handle webhook HMAC verification strict.
-
-## Load Confirmation
-
-> Rule: If you use this pack, you must explicitly state: "Loaded Backend Pack."

package/.antigravity/skills/_packs/web/pack-frontend.md

@@ -1,66 +0,0 @@
-# Pack: Frontend
-
-Tier: Domain
-Load Cost: High
-Keywords: react, nextjs, tailwind, ui, ux, components, frontend
-
-## Scope
-
-This pack covers all aspects of **Frontend Development** within the Anchi-Kit ecosystem.
-
-- **Includes**: Component architecture, UI styling (Tailwind), State Management, React Hooks, Next.js Routing, Client-Side logic, Accessibility (a11y), Animations.
-- **Excludes**: Backend API logic (see `pack-backend`), Database schemas, DevOps pipelines.
-
-## Canonical Patterns (Best Practices)
-
-### 1. Component Design
-
-- **Single Responsibility**: Each component should do one thing well.
-- **Composition over Inheritance**: Use children props and slots.
-- **Props Interface**: Always define explicit interfaces for props (TypeScript).
-- **Atomic Design**: Structure components as Atoms, Molecules, Organisms, Templates.
-
-### 2. Styling (Tailwind CSS)
-
-- **Utility-First**: Use Tailwind classes directly in markup.
-- **Tokens**: Use `theme('colors...')` for consistency.
-- **Responsive**: Mobile-first design (`min-width` default, `md:`, `lg:` overrides).
-- **ClassName Merging**: Use `cn()` utility (clsx + tailwind-merge) for conditional classes.
-
-### 3. State Management
-
-- **Local State**: `useState` for simple UI toggles.
-- **Server State**: Use `useQuery` or Next.js Server Components for data fetching.
-- **Global State**: Minimal use of Context/Zustand only when absolutely necessary (e.g., Theme, Auth User).
-
-### 4. Performance
-
-- **Image Optimization**: Use `next/image`.
-- **Lazy Loading**: Use `dynamic()` for heavy components below the fold.
-- **Memoization**: `useMemo`/`useCallback` only when profiling shows re-render issues.
-
-## Anti-Patterns (What to Avoid)
-
-- ❌ **Hardcoded Styles**: Avoid `style={{ margin: 10 }}`. Use Tailwind classes.
-- ❌ **Prop Drilling**: Passing data through >3 layers. Use Composition or Context.
-- ❌ **Client-Side Heavy**: Making everything `"use client"`. Default to Server Components.
-- ❌ **Magic Numbers**: Using arbitrary pixel values (e.g., `width: 317px`). Use design tokens.
-- ❌ **Huge Components**: Files > 300 lines should likely be split.
-
-## Specialized Modules
-
-### 3D / WebGL (Three.js)
-
-- Use `@react-three/fiber`.
-- Keep canvas logic separate from DOM UI.
-- optimize models (GLB/GLTF) via `gltfjsx`.
-
-### Mobile (React Native / Expo)
-
-- Use `StyleSheet.create` or strict Tailwind integration (NativeWind).
-- Handle platform differences (`Platform.OS`).
-- Avoid web-only APIs is critical paths.
-
-## Load Confirmation
-
-> Rule: If you use this pack, you must explicitly state: "Loaded Frontend Pack."

package/.antigravity/skills/_packs/web3/pack-blockchain.md

@@ -1,37 +0,0 @@
-# Pack: Blockchain
-
-Tier: Domain
-Load Cost: High
-Keywords: blockchain, web3, solidity, smart-contract, ethereum, crypto, wallet
-
-## Scope
-
-This pack covers **Web3 and Blockchain Development**.
-
-- **Includes**: Smart Contract development (Solidity), Interaction (Ethers.js/Viem), Testing (Hardhat/Foundry), Security (Reentrancy prevention).
-- **Excludes**: Creating new L1 chains (Core Protocol Dev).
-
-## Canonical Patterns (Best Practices)
-
-### 1. Smart Contracts (Solidity)
-
-- **Security First**: Use OpenZeppelin contracts (standard libraries).
-- **Checks-Effects-Interactions**: Update state _before_ external calls to prevent Reentrancy.
-- **Gas Optimization**: Use `calldata` vs `memory`, pack variables, avoid loops.
-
-### 2. Integration
-
-- **Wagmi/Viem**: Modern React hooks for wallet connection.
-- **Event Listening**: Index events for UI updates (The Graph or direct listeners).
-- **Error Handling**: Handle chain-specific errors (UserRejected, InsufficientFunds).
-
-## Anti-Patterns (What to Avoid)
-
-- ❌ **Rolling Crypto**: Never invent your own encryption/hashing.
-- ❌ **Unchecked Calls**: Always check return values of low-level calls.
-- ❌ **Timestamp Dependence**: Block timestamps can be manipulated by miners.
-- ❌ **Private Logic**: Nothing on-chain is truly private.
-
-## Load Confirmation
-
-> Rule: If you use this pack, you must explicitly state: "Loaded Blockchain Pack."

package/.antigravity/skills/_template.md

@@ -1,30 +0,0 @@
-# Skill: [Skill Name]
-
-**Description:** [Short description of the technology/framework]
-
-## 🎯 Activation Criteria
-
-- **Files:** `[file_patterns]`
-- **Dependencies:** `[package_names]`
-- **Keywords:** `[keywords]`
-
-## ✅ Best Practices (Rules)
-
-1.  **[Rule 1]:** [Description]
-2.  **[Rule 2]:** [Description]
-3.  **[Naming Convention]:** [Description]
-
-## ❌ Anti-Patterns (Do Not Do)
-
-1.  **[Anti-Pattern 1]:** [Description]
-2.  **[Anti-Pattern 2]:** [Description]
-
-## 📦 Dependencies & Setup
-
-- Recommended Packages:
-  - [pkg1]
-  - [pkg2]
-
-## 🧠 Memory Hooks
-
-- If user asks for [X], suggest [Y].

package/.antigravity/skills/advanced-coding/references/getting-started.md

@@ -1,93 +0,0 @@
-# Getting Started with Anchi Advanced Coding
-
-Installation, authentication, and setup guide for Anchi's Advanced Coding Assistant.
-
-## What is Advanced Coding Assistant?
-
-Anchi's agentic coding tool that lives in the terminal and helps turn ideas into code faster. Key features:
-
-- **Agentic Capabilities**: Autonomous planning, execution, and validation
-- **Terminal Integration**: Works directly in command line
-- **IDE Support**: Extensions for VS Code and JetBrains IDEs
-- **Extensibility**: Plugins, skills, slash commands, and MCP servers
-- **Enterprise Ready**: SSO, sandboxing, monitoring, and compliance features
-
-## Prerequisites
-
-### System Requirements
-- **Operating Systems**: macOS, Linux, or Windows (WSL2)
-- **Runtime**: Node.js 18+ or Python 3.10+
-- **API Key**: From Anchi Console (or configured provider)
-
-## Installation
-
-### Install via npm
-```bash
-npm install -g @anchi-kit/advanced-coding
-```
-
-### Verify Installation
-```bash
-anchi-code --version
-```
-
-## Authentication
-
-### Method 1: Interactive Login
-```bash
-anchi-code login
-# Follow prompts to enter API key
-```
-
-## Basic Usage
-
-### Interactive Mode
-```bash
-$ anchi-code
-Anchi> help me create a React component
-# Agent will plan and execute
-```
-
-### One-Shot Mode
-```bash
-anchi-code "add error handling to main.py"
-```
-
-## Common First Commands
-
-### Explore Codebase
-```bash
-anchi-code "explain the project structure"
-```
-
-### Run Tests
-```bash
-anchi-code "run the test suite"
-```
-
-## Directory Structure
-
-Anchi creates `.cursor/` (or `.anchi/`) in your project:
-
-```
-project/
-├── .cursor/
-│   ├── settings.json      # Project-specific settings
-│   ├── commands/          # Custom slash commands
-│   ├── skills/            # Custom skills
-│   └── hooks.json         # Hook configurations
-└── ...
-```
-
-## Next Steps
-
-### Learn Slash Commands
-```bash
-# See available commands
-/help
-
-# Try common workflows
-/cook implement feature X
-/fix bug in Y
-/test
-```

package/.antigravity/skills/aesthetic/assets/design-guideline-template.md

@@ -1,163 +0,0 @@
-# Design Guidelines: [Project Name]
-
-_Generated: [Date]_
-
-## Design Style
-
-[Specify: Minimalism, Glassmorphism, Neo-brutalism, Modern, Memphis, Flat Design, etc.]
-
-## Color Palette
-
-### Primary Colors
-- **Primary**: `#000000` - [Description/Usage]
-- **Secondary**: `#000000` - [Description/Usage]
-
-### Accent Colors
-- **Accent**: `#000000` - [Description/Usage]
-- **Success**: `#000000` - [Description/Usage]
-- **Warning**: `#000000` - [Description/Usage]
-- **Error**: `#000000` - [Description/Usage]
-
-### Neutral Colors
-- **Background**: `#000000` - [Description/Usage]
-- **Surface**: `#000000` - [Description/Usage]
-- **Border**: `#000000` - [Description/Usage]
-
-### Color Psychology
-[Explain mood and emotions evoked by color choices]
-
-## Typography System
-
-### Font Families
-- **Primary Font**: [Font Name] - Body text, paragraphs
-- **Secondary Font**: [Font Name] - Headings, emphasis
-- **Monospace Font**: [Font Name] - Code, technical content
-
-### Font Hierarchy
-- **H1**: [Size]px / [Weight] / [Line Height] - [Usage]
-- **H2**: [Size]px / [Weight] / [Line Height] - [Usage]
-- **H3**: [Size]px / [Weight] / [Line Height] - [Usage]
-- **Body**: [Size]px / [Weight] / [Line Height] - [Usage]
-- **Small**: [Size]px / [Weight] / [Line Height] - [Usage]
-
-### Typography Guidelines
-- Line length: [Character count] characters max
-- Paragraph spacing: [Value]
-- Letter spacing: [Value]
-
-## Layout Principles
-
-### Grid System
-- Columns: [Number]
-- Gutter: [Size]px
-- Margin: [Size]px
-- Max width: [Size]px
-
-### Spacing Scale
-- xs: [Size]px
-- sm: [Size]px
-- md: [Size]px
-- lg: [Size]px
-- xl: [Size]px
-- 2xl: [Size]px
-
-### Responsive Breakpoints
-- Mobile: [Width]px
-- Tablet: [Width]px
-- Desktop: [Width]px
-- Wide: [Width]px
-
-## Component Styling
-
-### Buttons
-- **Primary**: [Description of style]
-- **Secondary**: [Description of style]
-- **Ghost**: [Description of style]
-- **Sizes**: [List sizes]
-- **States**: Default, Hover, Active, Disabled
-
-### Cards
-- Border radius: [Value]
-- Shadow: [Value]
-- Padding: [Value]
-- Background: [Color]
-
-### Forms
-- Input height: [Value]
-- Border radius: [Value]
-- Focus state: [Description]
-- Error state: [Description]
-
-### Navigation
-- [Description of nav patterns]
-
-## Visual Hierarchy
-
-### Emphasis Techniques
-- [List how to draw attention: size, color, placement, etc.]
-
-### Content Flow
-- [Describe reading patterns: F-pattern, Z-pattern, etc.]
-
-## Micro-Interactions
-
-### Animation Timing
-- Fast: 150ms - [Usage]
-- Normal: 250ms - [Usage]
-- Slow: 350ms - [Usage]
-
-### Easing Curves
-- Ease-out: [Usage]
-- Ease-in: [Usage]
-- Spring: [Usage]
-
-### Interactive States
-- Hover: [Description]
-- Active: [Description]
-- Focus: [Description]
-- Loading: [Description]
-
-## Accessibility
-
-### Contrast Ratios
-- Text: [Ratio] (WCAG AA: 4.5:1 minimum)
-- Large text: [Ratio] (WCAG AA: 3:1 minimum)
-- UI elements: [Ratio]
-
-### Focus Indicators
-- [Description of focus styles]
-
-### Touch Targets
-- Minimum size: 44x44px
-
-## Design Highlights
-
-### What Works Well
-- [List successful design decisions]
-
-### Unique Elements
-- [List distinctive design features]
-
-### Brand Alignment
-- [Explain how design supports brand identity]
-
-## Implementation Notes
-
-### Technologies
-- [List frameworks, libraries, tools used]
-
-### Performance Considerations
-- [List optimization strategies]
-
-### Browser Support
-- [List supported browsers/versions]
-
-## Resources
-
-### Design Files
-- Figma: [Link]
-- Assets: [Link]
-
-### Related Documentation
-- [Link to design-story.md]
-- [Link to component library]

package/.antigravity/skills/aesthetic/assets/design-story-template.md

@@ -1,135 +0,0 @@
-# Design Story: [Project Name]
-
-_Generated: [Date]_
-
-## Project Context
-
-### Purpose
-[What problem does this design solve?]
-
-### Target Audience
-[Who is this design for?]
-
-### Key Objectives
-1. [Objective 1]
-2. [Objective 2]
-3. [Objective 3]
-
-## Design Narrative
-
-### Core Message
-[What story does this design tell?]
-
-### Emotional Journey
-[What should users feel as they interact?]
-
-### Visual Metaphor
-[What metaphor or theme unifies the design?]
-
-## User Journey
-
-### Entry Point
-**First Impression**: [What users see first]
-**Goal**: [What should users understand immediately]
-**Design Choices**: [How design supports this]
-
-### Exploration Phase
-**User Actions**: [What users do next]
-**Design Response**: [How interface responds]
-**Micro-Interactions**: [Subtle feedback provided]
-
-### Engagement Phase
-**Key Interactions**: [Main user activities]
-**Visual Feedback**: [How design reinforces actions]
-**Storytelling Elements**: [Narrative reinforcement]
-
-### Peak Moment
-**Highlight**: [Most memorable interaction]
-**Implementation**: [How it's achieved technically]
-**Purpose**: [Why this moment matters]
-
-## Thematic Elements
-
-### Visual Theme
-[Description of consistent visual approach]
-
-### Narrative Devices
-- **Parallax**: [How depth is used]
-- **Transitions**: [How sections connect]
-- **Progressive Disclosure**: [How information unfolds]
-- **Motion**: [How animation tells the story]
-
-### Symbolism
-[Meaning behind design choices]
-
-## Design Decisions
-
-### Why This Style?
-[Rationale for design style choice]
-
-### Why These Colors?
-[Reasoning behind color palette]
-
-### Why This Layout?
-[Logic behind structure and flow]
-
-### Why These Interactions?
-[Purpose of micro-interactions chosen]
-
-## Technical Storytelling
-
-### Performance Story
-[How fast loading enhances narrative]
-
-### Responsive Story
-[How design adapts across devices]
-
-### Accessibility Story
-[How inclusive design supports everyone]
-
-## Evolution
-
-### Initial Concepts
-[Early ideas explored]
-
-### Key Iterations
-[Major changes and why]
-
-### Final Direction
-[Ultimate design rationale]
-
-## Inspiration
-
-### Design References
-- [Source 1]: [What inspired]
-- [Source 2]: [What inspired]
-- [Source 3]: [What inspired]
-
-### Cultural Context
-[Broader design trends considered]
-
-## Impact
-
-### Intended Effect
-[What users should take away]
-
-### Success Metrics
-[How to measure if story resonates]
-
-### Future Chapters
-[How design can evolve]
-
-## Reflections
-
-### What Worked
-[Successful narrative elements]
-
-### What We Learned
-[Insights gained from process]
-
-### What's Next
-[Future storytelling opportunities]
-
----
-
-**Remember**: Every design tells a story. Make it intentional, coherent, and meaningful.