anchi-kit 2.2.0 → 2.3.0

package/.antigravity/command/design/3d.md

@@ -1,65 +0,0 @@
----
-description: Create immersive interactive 3D designs with Three.js
----
-
-Think hard to plan & start working on these tasks follow the Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules:
-<tasks>$ARGUMENTS</tasks>
-
-## Workflow:
-1. Use `ui-ux-designer` subagent and `researcher` subagent to create a comprehensive 3D design plan with TODO tasks in `./plans` directory.
-2. Then use `ui-ux-designer` subagent to implement the plan step by step.
-3. Create immersive 3D experiences using Three.js with particle effects, custom shaders, and interactive elements.
-4. Leverage all available Human MCP capabilities for asset generation and validation.
-5. Report back to user with a summary of the changes and explain everything briefly, ask user to review the changes and approve them.
-6. If user approves the changes, update the `./docs/design-guidelines.md` docs if needed.
-
-## 3D Design Requirements:
-- Implement Three.js scenes with proper optimization
-- Create custom GLSL shaders for unique visual effects
-- Design GPU-accelerated particle systems
-- Add immersive camera controls and cinematic effects
-- Implement post-processing effects and render pipelines
-- Ensure responsive behavior across all devices
-- Optimize performance for real-time rendering
-- Add interactive elements and smooth animations
-
-## Human MCP Tools Integration:
-
-### ai-multimodal Skills & ImageMagick Skill (Asset Generation & Processing):
-- Generate textures, skyboxes, and environment maps with ai-multimodal skills
-- Create custom particle sprites and effect assets via ai-multimodal prompts
-- Generate 3D object textures with specific styles using ai-multimodal skills
-- Create video backgrounds for immersive scenes with ai-multimodal capabilities
-- Apply camera movements, inpainting, and outpainting through ai-multimodal skills
-- Refine, batch edit, and optimize outputs with imagemagick skill workflows
-
-### JIMP Tools (Image Processing):
-- Process and optimize textures for WebGL
-- Create normal maps and height maps from images
-- Generate sprite sheets for particle systems
-- Remove backgrounds for transparent textures
-- Resize and optimize assets for performance
-- Apply masks for complex texture effects
-
-### Eyes Tools (Visual Analysis):
-- Analyze reference images for 3D scene composition
-- Compare design mockups with implementation
-- Validate texture quality and visual consistency
-- Extract color palettes from reference materials
-- Verify shader effects and visual output
-
-## Implementation Stack:
-- Three.js for 3D rendering
-- GLSL for custom vertex and fragment shaders
-- HTML/CSS/JS for UI integration
-- WebGL for GPU-accelerated graphics
-- Post-processing libraries for effects
-
-## Notes:
-- Remember that you have the capability to generate images, videos, edit images, etc. with ai-multimodal skills. Use them extensively to create realistic 3D assets.
-- Always review, analyze and double check generated assets with eyes tools of Human MCP Server.
-- Leverage ai-multimodal skills and imagemagick skill to create custom textures, particle sprites, environment maps, and visual effects.
-- Use imagemagick skill to process and optimize all visual assets for WebGL performance.
-- Test 3D scenes across different devices and optimize for smooth 60fps performance.
-- Maintain and update `./docs/design-guidelines.md` docs with 3D design patterns and shader libraries.
-- Document shader code, particle systems, and reusable 3D components for future reference.

package/.antigravity/command/design/fast.md

@@ -1,18 +0,0 @@
----
-description: Create a quick design
----
-
-Think hard to plan & start working on these tasks follow the Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules: 
-<tasks>$ARGUMENTS</tasks>
-
-## Workflow:
-1. Use `ui-ux-designer` subagent and `researcher` subagent to create a design plan with TODO tasks in `./plans` directory.
-2. Then use `ui-ux-designer` subagent to implement the plan step by step.
-3. If user doesn't specify, create the design in pure HTML/CSS/JS.
-4. Report back to user with a summary of the changes and explain everything briefly, ask user to review the changes and approve them.
-5. If user approves the changes, update the `./docs/design-guidelines.md` docs if needed.
-
-## Notes:
-- Remember that you have the capability to generate images, videos, edit images, etc. with Human MCP Server tools. Use them to create the design and real assets.
-- Always review, analyze and double check generated assets with eyes tools of Human MCP Server.
-- Maintain and update `./docs/design-guidelines.md` docs if needed.

package/.antigravity/command/design/good.md

@@ -1,21 +0,0 @@
----
-description: Create an immersive design
----
-
-Think hard to plan & start working on these tasks follow the Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules: 
-<tasks>$ARGUMENTS</tasks>
-
-## Workflow:
-1. Use `ui-ux-designer` subagent and multiple `researcher` subagents in parallel to create a design plan with TODO tasks in `./plans` directory.
-2. Then use `ui-ux-designer` subagent to implement the plan step by step.
-3. If user doesn't specify, create the design in pure HTML/CSS/JS.
-4. Report back to user with a summary of the changes and explain everything briefly, ask user to review the changes and approve them.
-5. If user approves the changes, update the `./docs/design-guidelines.md` docs if needed.
-
-## Important Notes:
-- **ALWAYS REMEBER that you have the skills of a top-tier UI/UX Designer who won a lot of awards on Dribbble, Behance, Awwwards, Mobbin, TheFWA.**
-- Remember that you have the capability to generate images, videos, edit images, etc. with Human MCP Server tools. Use them to create the design with real assets.
-- Always review, analyze and double check the generated assets with eyes tools of Human MCP Server.
-- Use removal background tools to remove background from generated assets if needed.
-- Create storytelling designs, immersive 3D experiences, micro-interactions, and interactive interfaces.
-- Maintain and update `./docs/design-guidelines.md` docs if needed.

package/.antigravity/command/design/screenshot.md

@@ -1,22 +0,0 @@
----
-description: Create a design based on screenshot
----
-
-Think hard to plan & start designing follow exactly this screenshot: 
-<screenshot>$ARGUMENTS</screenshot>
-
-## Workflow:
-1. Use `ai-multimodal` skills to describe super details of the screenshot.
-2. Use `ui-ux-designer` subagent to create a design plan of creating exactly the same result with the screenshot, break down the plan into TODO tasks in `./plans` directory.
-3. Then implement the plan step by step.
-4. If user doesn't specify, create the design in pure HTML/CSS/JS.
-5. Report back to user with a summary of the changes and explain everything briefly, ask user to review the changes and approve them.
-6. If user approves the changes, update the `./docs/design-guidelines.md` docs if needed.
-
-## Important Notes:
-- **ALWAYS REMEBER that you have the skills of a top-tier UI/UX Designer who won a lot of awards on Dribbble, Behance, Awwwards, Mobbin, TheFWA.**
-- Remember that you have the capability to generate images, videos, edit images, etc. with Human MCP Server tools. Use them to create the design with real assets.
-- Always review, analyze and double check the generated assets with eyes tools of Human MCP Server.
-- Use removal background tools to remove background from generated assets if needed.
-- Create storytelling designs, immersive 3D experiences, micro-interactions, and interactive interfaces.
-- Maintain and update `./docs/design-guidelines.md` docs if needed.

package/.antigravity/command/design/video.md

@@ -1,22 +0,0 @@
----
-description: Create a design based on video
----
-
-Think hard to plan & start designing follow exactly this video: 
-<video>$ARGUMENTS</video>
-
-## Workflow:
-1. Use `ai-multimodal` skills to describe super details of the video: be specific about describing every element, every interaction, every animation, every transition, every color, every font, every spacing, every size, every shape, every texture, every material, every light, every shadow, every reflection, every refraction, every blur, every glow, every reflection, every refraction, every blur, every glow, every reflection, every refraction, every blur, every glow, every image.
-2. Use `ui-ux-designer` subagent to create a design plan of creating exactly the same result with the video, break down the plan into TODO tasks in `./plans` directory.
-3. Then implement the plan step by step.
-4. If user doesn't specify, create the design in pure HTML/CSS/JS.
-5. Report back to user with a summary of the changes and explain everything briefly, ask user to review the changes and approve them.
-6. If user approves the changes, update the `./docs/design-guidelines.md` docs if needed.
-
-## Important Notes:
-- **ALWAYS REMEBER that you have the skills of a top-tier UI/UX Designer who won a lot of awards on Dribbble, Behance, Awwwards, Mobbin, TheFWA.**
-- Remember that you have the capability to generate images, videos, edit images, etc. with Human MCP Server tools. Use them to create the design with real assets.
-- Always review, analyze and double check the generated assets with eyes tools of Human MCP Server.
-- Use removal background tools to remove background from generated assets if needed.
-- Create storytelling designs, immersive 3D experiences, micro-interactions, and interactive interfaces.
-- Maintain and update `./docs/design-guidelines.md` docs if needed.

package/.antigravity/command/docs/init.md

@@ -1,11 +0,0 @@
----
-description: Analyze the codebase and create initial documentation
----
-
-Use `docs/` directory as the source of truth for documentation.
-Use `docs-manager` agent to analyze the codebase and create initial documentation:
-- `docs/project-overview-pdr.md`: Project overview and PDR (Product Development Requirements)
-- `docs/codebase-summary.md`: Codebase summary
-- `docs/codebase-structure-architecture-code-standards.md`: Codebase structure, architecture, and code standards
-
-**IMPORTANT**: **Do not** start implementing.

package/.antigravity/command/docs/summarize.md

@@ -1,10 +0,0 @@
----
-description: Analyze the codebase and update documentation
----
-
-Use `docs-manager` agent to analyze the codebase and update `docs/codebase-summary.md`
-
-## Notes:
-- Use `docs/` directory as the source of truth for documentation.
-
-**IMPORTANT**: **Do not** start implementing.

package/.antigravity/command/docs/update.md

@@ -1,18 +0,0 @@
----
-description: Analyze the codebase and update documentation
----
-
-Use `docs/` directory as the source of truth for documentation.
-Use `docs-manager` agent to analyze the codebase and update documentation:
-- `README.md`: Update README (keep it under 300 lines)
-- `docs/project-overview-pdr.md`: Update project overview and PDR (Product Development Requirements)
-- `docs/codebase-summary.md`: Update codebase summary
-- `docs/codebase-structure-architecture-code-standards.md`: Update codebase structure, architecture, and code standards
-- Only update `CLAUDE.md` or `AGENTS.md` when requested.
-
-## Additional requests
-<additional_requests>
-  $ARGUMENTS
-</additional_requests>
-
-**IMPORTANT**: **Do not** start implementing.

package/.antigravity/command/fix/ci.md

@@ -1,8 +0,0 @@
----
-description: Analyze Github Actions logs and fix issues
----
-## Github Actions URL
- $ARGUMENTS
-
-Use the `planer-researcher` to read the github actions logs, analyze and find the root causes of the issues, then provide a detailed plan for implementing the fixes.
-Then use proper developer agents to implement the plan.

package/.antigravity/command/fix/fast.md

@@ -1,11 +0,0 @@
----
-description: Analyze and fix the issue [FAST]
----
-
-Analyze and fix this issue:
-<issue>$ARGUMENTS</issue>
-
-## Development Rules
-
-- Use `tester` agent to test the fix and make sure it works, then report back to main agent.
-- If there are issues or failed tests, ask main agent to fix all of them and repeat the process until all tests pass.

package/.antigravity/command/fix/hard.md

@@ -1,15 +0,0 @@
----
-description: Use subagents to plan and fix hard issues
----
-
-Think hard to plan & start fixing these issues follow the Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules: 
-<issues>$ARGUMENTS</issues>
-
-## Workflow:
-1. Use `planner` subagent and `researcher` subagent to create a implementation plan with TODO tasks in `./plans` directory.
-2. Then use general agent (main agent) to implement the plan step by step.
-3. Use `tester` subagent to run the tests, make sure it works, then report back to main agent.
-4. If there are issues or failed tests, use `debugger` subagent to find the root cause of the issues, then ask main agent to fix all of them and 
-5. Repeat the process until all tests pass or no more issues are reported.
-6. After finishing, delegate to `code-reviewer` subagent to review code. If there are critical issues, ask main agent to improve the code and test everything again.
-7. Report back to user with a summary of the changes and explain everything briefly.

package/.antigravity/command/fix/logs.md

@@ -1,16 +0,0 @@
----
-description: Analyze logs and fix issues
----
-
-Use `debugger` agent to analyze the `./logs.txt` file, identify root causes of any errors or issues and respond with a report and solution.
-So the main agent can fix them.
-
-## Rules
-
-- Use `debugger` agent to read and analyze the entire `./logs.txt` file
-- Identify all errors, warnings, and potential issues
-- Determine the root causes of each issue
-- Fix all identified problems systematically based on the report
-- Verify fixes by running appropriate commands
-- Re-analyze logs after fixes to ensure issues are resolved
-

package/.antigravity/command/fix/test.md

@@ -1,18 +0,0 @@
----
-description: Run test suite and fix issues
----
-
-## Reported Issues:
-<issue>
- $ARGUMENTS
-</issue>
-
-## Workflow:
-1. First use `tester` subagent to compile the code and fix all syntax errors if any.
-2. Then use `tester` subagent to run the tests.
-3. If there are issues or failed tests, use `debugger` subagent to find the root cause of the issues.
-4. Then use `planner` subagent to create a implementation plan with TODO tasks in `./plans` directory.
-5. Then implement the plan step by step.
-6. Use `tester` subagent to run the tests after implementing the plan, make sure it works, then report back to main agent.
-7. After finishing, delegate to `code-reviewer` agent to review code. If there are critical issues, ask main agent to improve the code and test everything again.
-8. Repeat this process until all tests pass and no more errors are reported.

package/.antigravity/command/fix/types.md

@@ -1,10 +0,0 @@
----
-description: Fix type errors
----
-
-Run `bun run typecheck` and fix all type errors.
-
-## Rules
-
-- Fix all of type errors and repeat the process until there are no more type errors.
-- Do not use `any` just to pass the type check.

package/.antigravity/command/git/cm.md

@@ -1,5 +0,0 @@
----
-description: Stage all files and create a commit.
----
-Use `git-manager` agent to stage all files and create a commit.
-**IMPORTANT: DO NOT push the changes to remote repository**

package/.antigravity/command/git/cp.md

@@ -1,4 +0,0 @@
----
-description: Stage, commit and push all code in the current branch
----
-Use `git-manager` agent to stage all files, create a meaningful commit based on the changes and push to remote repository.

package/.antigravity/command/plan/ci.md

@@ -1,12 +0,0 @@
----
-description: Analyze Github Actions logs and provide a plan to fix the issues
----
-## Github Actions URL
- $ARGUMENTS
-
-Use the `planer-researcher` to read the github actions logs, analyze and find the root causes of the issues, then provide a detailed plan for implementing the fixes.
-
-**Output:**
-Provide at least 2 implementation approaches with clear trade-offs, and explain the pros and cons of each approach, and provide a recommended approach.
-
-**IMPORTANT:** Ask the user for confirmation before implementing.

package/.antigravity/command/plan/two.md

@@ -1,13 +0,0 @@
----
-description: Research & create an implementation plan with 2 approaches
----
-
-Use the `planner` subagent to plan for this task:
-<task>
- $ARGUMENTS
-</task>
-
-**Output:**
-Provide at least 2 implementation approaches with clear trade-offs, and explain the pros and cons of each approach, and provide a recommended approach.
-
-**IMPORTANT**: **Do not** start implementing.

package/.antigravity/command/plan.md

@@ -1,10 +0,0 @@
----
-description: Research, analyze, and create an implementation plan
----
-
-Use the `planner` subagent to plan for this task:
-<task>
- $ARGUMENTS
-</task>
-
-**IMPORTANT**: **Do not** start implementing.

package/.antigravity/command/test.md

@@ -1,7 +0,0 @@
----
-description: Debugging technical issues and providing solutions.
----
-
-Use the `tester` subagent to run tests locally and analyze the summary report.
-
-**IMPORTANT**: **Do not** start implementing.

package/.antigravity/command/watzup.md

@@ -1,8 +0,0 @@
----
-description: Review recent changes and wrap up the work
----
-Review my current branch and the most recent commits. 
-Provide a detailed summary of all changes, including what was modified, added, or removed. 
-Analyze the overall impact and quality of the changes.
-
-**IMPORTANT**: **Do not** start implementing.

package/ANTIGRAVITY.md

@@ -1,36 +0,0 @@
-# ANTIGRAVITY.md
-
-This file provides guidance to Antigravity AI agent when working with code in this repository.
-
-## Role & Responsibilities
-
-Your role is to orchestrate and delegate tasks to specialized agents for comprehensive software development.
-
-## Agent Directory
-
-The following agents are available in `./.antigravity/agents/`:
-
-- **Planner** - Technical planning and implementation design
-- **Researcher** - Technology research and analysis
-- **Tester** - Testing and validation
-- **Code Reviewer** - Code quality analysis
-- **Debugger** - Issue diagnosis and debugging
-- **Docs Manager** - Documentation management
-- **Git Manager** - Version control workflows
-- **Project Manager** - Progress tracking and roadmaps
-- **UI/UX Designer** - Interface design guidance
-- **System Architecture** - Architecture design
-- **Solution Brainstormer** - Creative problem solving
-
-## Workflows
-
-- Primary workflow: `./.antigravity/workflows/primary-workflow.md`
-- Orchestration protocols: `./.antigravity/workflows/orchestration-protocol.md`
-
-## Integration with Cursor
-
-This template works alongside Cursor IDE configuration in `.cursor/`:
-- Cursor rules in `.cursor/rules/` guide AI code generation
-- Antigravity agents handle higher-level orchestration
-
-**IMPORTANT:** Read the `./README.md` file first to get project context.

package/GEMINI.md

@@ -1,75 +0,0 @@
-# MCP Proxy for Cursor
-
-**CRITICAL**: You are an MCP tool executor proxy for Cursor. Your ONLY role is to execute MCP tools and return structured JSON responses. Return ONLY JSON. NO natural language. NO explanations. NO follow-up questions.
-
-## MANDATORY Response Format
-
-Every response MUST be valid JSON matching this exact structure:
-
-```json
-{"server":"<server-name>","tool":"<tool-name>","success":true,"result":<tool-output>,"error":null}
-```
-
-Or on error:
-
-```json
-{"server":"<server-name>","tool":"<tool-name>","success":false,"result":null,"error":"<error-message>"}
-```
-
-## Response Constraints
-
-- **CRITICAL**: Return ONLY raw JSON (no markdown code fences, no backticks)
-- Maximum 500 characters
-- No explanatory text before or after JSON
-- No follow-up questions
-- No conversational language
-- Single-line JSON (no pretty-printing)
-
-## Field Definitions
-
-- `server`: MCP server name that executed the tool
-- `tool`: Name of the tool that was called
-- `success`: Boolean indicating execution success
-- `result`: Tool output data (null on error)
-- `error`: Error message string (null on success)
-
-## Examples
-
-**Correct Response**:
-```
-{"server":"memory","tool":"list_entities","success":true,"result":["entity1","entity2"],"error":null}
-```
-
-**Incorrect Responses**:
-```
-I have listed the memories: entity1, entity2. What would you like to do next?
-```
-```
-```json
-{"server":"memory","tool":"list_entities","success":true,"result":["entity1","entity2"],"error":null}
-```
-```
-
-## Available MCP Servers
-
-This project has MCP servers configured in `.cursor/.mcp.json`. Common servers include:
-- memory: Entity and knowledge graph storage
-- brave-search: Web search capabilities
-- filesystem: File operations
-- puppeteer: Browser automation
-- context7: Documentation search
-
-## Auto-Loading
-
-Gemini CLI automatically loads this file when executed in this project directory. You MUST follow these instructions for every MCP operation request.
-
-## Integration with Cursor
-
-Cursor uses `/use-mcp` command to delegate MCP operations to you. The workflow:
-
-1. Cursor sends task via stdin: `echo "task" | gemini -y -m gemini-2.5-flash`
-2. You execute the appropriate MCP tool(s)
-3. You return ONLY the JSON response
-4. Cursor parses the JSON and continues its work
-
-**Your output is programmatically parsed. Any deviation from the JSON format will break the integration.**

package/scripts/prepare-release-assets.cjs

@@ -1,97 +0,0 @@
-#!/usr/bin/env node
-
-const fs = require('fs');
-const path = require('path');
-const { execSync } = require('child_process');
-
-/**
- * Generate metadata.json aligned with the package version and
- * bundle the release archive ahead of the semantic-release publish step.
- */
-(function main() {
-  const version = process.argv[2];
-
-  if (!version) {
-    console.error('✗ Missing required version argument for prepare-release-assets');
-    process.exit(1);
-  }
-
-  const projectRoot = process.cwd();
-  const packageJsonPath = path.join(projectRoot, 'package.json');
-  const claudeDir = path.join(projectRoot, '.claude');
-  const metadataPath = path.join(claudeDir, 'metadata.json');
-  const distDir = path.join(projectRoot, 'dist');
-  const archivePath = path.join(distDir, 'claudekit-engineer.zip');
-
-  try {
-    if (!fs.existsSync(packageJsonPath)) {
-      throw new Error('package.json not found');
-    }
-
-    const packageJson = JSON.parse(fs.readFileSync(packageJsonPath, 'utf8'));
-
-    if (packageJson.version !== version) {
-      console.warn(
-        `⚠️ package.json version (${packageJson.version}) does not match semantic-release version (${version}).`
-      );
-    }
-
-    const requiredFields = ['name', 'description', 'repository'];
-    const missingFields = requiredFields.filter((field) => !packageJson[field]);
-
-    if (missingFields.length > 0) {
-      throw new Error(`Missing required fields in package.json: ${missingFields.join(', ')}`);
-    }
-
-    if (!fs.existsSync(claudeDir)) {
-      fs.mkdirSync(claudeDir, { recursive: true });
-    }
-
-    const metadata = {
-      version: packageJson.version,
-      name: packageJson.name,
-      description: packageJson.description,
-      buildDate: new Date().toISOString(),
-      repository: packageJson.repository,
-      download: {
-        lastDownloadedAt: null,
-        downloadedBy: null,
-        installCount: 0,
-      },
-    };
-
-    fs.writeFileSync(metadataPath, `${JSON.stringify(metadata, null, 2)}\n`, 'utf8');
-    console.log(`✓ Generated metadata.json with version ${metadata.version}`);
-
-    if (!fs.existsSync(distDir)) {
-      fs.mkdirSync(distDir, { recursive: true });
-    }
-
-    if (fs.existsSync(archivePath)) {
-      fs.unlinkSync(archivePath);
-    }
-
-    const archiveTargets = [
-      '.claude',
-      '.opencode',
-      'plans',
-      '.gitignore',
-      '.repomixignore',
-      '.mcp.json',
-      'CLAUDE.md',
-    ];
-
-    const existingTargets = archiveTargets.filter((target) => fs.existsSync(path.join(projectRoot, target)));
-
-    if (existingTargets.length === 0) {
-      throw new Error('No release assets found to include in archive.');
-    }
-
-    const zipCommand = ['zip', '-r', archivePath, ...existingTargets].join(' ');
-    execSync(zipCommand, { stdio: 'inherit' });
-    console.log(`✓ Prepared ${archivePath}`);
-  } catch (error) {
-    console.error(`✗ Failed to prepare release assets: ${error.message}`);
-    process.exit(1);
-  }
-})();