anchi-toolkit 1.2.0 → 1.2.1

package/dist/.ai-memory/context.json

@@ -0,0 +1,26 @@
+{
+    "project": {
+        "name": "",
+        "type": "",
+        "framework": "",
+        "database": "",
+        "preset": ""
+    },
+    "tech_stack": {
+        "frontend": [],
+        "backend": [],
+        "testing": []
+    },
+    "conventions": {
+        "component_pattern": "",
+        "state_management": "",
+        "auth": ""
+    },
+    "current_work": {
+        "feature": "",
+        "status": "",
+        "files": []
+    },
+    "notes": [],
+    "last_updated": ""
+}

package/dist/.ai-memory/decisions.json

@@ -0,0 +1,3 @@
+{
+    "decisions": []
+}

package/dist/.antigravity/agent-skill-index.yaml

@@ -0,0 +1,411 @@
+# Agent-Skill Index
+# Reference mapping for agent capabilities and skill assignments
+# ═══════════════════════════════════════════════════════════════
+
+# ═══════════════════════════════════════════════════════════════
+# AGENT INDEX
+# ═══════════════════════════════════════════════════════════════
+
+agents:
+  # ─────────────────────── Development ───────────────────────
+  fullstack-developer:
+    capabilities:
+      - frontend_development
+      - backend_development
+      - api_design
+      - database_queries
+    boundaries:
+      - NOT: security_audit → security-auditor
+      - NOT: infrastructure → devops-engineer
+      - NOT: pure_ui_design → ui-ux-designer
+    primary_skills:
+      - frontend-development
+      - backend-development
+      - web-frameworks
+    secondary_skills:
+      - databases
+      - testing
+    confidence:
+      frontend: 0.9
+      backend: 0.85
+      devops: 0.3
+    typical_commands:
+      - /do
+      - /generate
+      
+  debugger:
+    capabilities:
+      - error_analysis
+      - performance_diagnosis
+      - log_analysis
+      - interactive_probing # Inject logs -> Test -> Analyze
+    boundaries:
+      - NOT: code_writing → fullstack-developer
+    primary_skills:
+      - debugging
+      - chrome-devtools
+    typical_commands:
+      - /do "fix"
+      
+  tester:
+    capabilities:
+      - unit_testing
+      - integration_testing
+      - e2e_testing
+    primary_skills:
+      - testing
+    typical_commands:
+      - /test
+
+  # ─────────────────────── Design ───────────────────────
+  ui-ux-designer:
+    capabilities:
+      - ui_design
+      - ux_flow
+      - design_system
+    boundaries:
+      - NOT: backend_logic → fullstack-developer
+      - NOT: database → database-admin
+    primary_skills:
+      - ui-styling
+      - frontend-development
+    never_skills:
+      - databases
+      - devops
+    typical_commands:
+      - /design
+      
+  design-system-architect:
+    capabilities:
+      - component_library
+      - design_tokens
+      - theming
+    primary_skills:
+      - ui-styling
+      - frontend-development
+    typical_commands:
+      - /theme
+      - /design --library
+
+  # ─────────────────────── Architecture ───────────────────────
+  ddd-architect:
+    capabilities:
+      - domain_modeling
+      - bounded_contexts
+      - event_storming
+    boundaries:
+      - NOT: implementation → fullstack-developer
+    primary_skills:
+      - backend-development
+      - databases
+    escalation_from:
+      - fullstack-developer
+    typical_commands:
+      - /design --domain
+      
+  database-admin:
+    capabilities:
+      - schema_design
+      - query_optimization
+      - migration_planning
+    primary_skills:
+      - databases
+    escalation_from:
+      - fullstack-developer
+    typical_commands:
+      - /do (database-related)
+
+  # ─────────────────────── Security ───────────────────────
+  security-auditor:
+    capabilities:
+      - security_review
+      - vulnerability_scan
+      - auth_audit
+    primary_skills:
+      - security-best-practices
+      - authentication
+    never_skills:
+      - shopify
+    escalation_from:
+      - fullstack-developer
+      - database-admin
+    typical_commands:
+      - /review --security
+      
+  # ─────────────────────── Operations ───────────────────────
+  devops-engineer:
+    capabilities:
+      - deployment
+      - ci_cd
+      - infrastructure
+    primary_skills:
+      - devops
+    typical_commands:
+      - /do (deployment-related)
+      - /demo
+      
+  git-manager:
+    capabilities:
+      - git_operations
+      - branch_management
+      - pr_creation
+    primary_skills:
+      - git
+    typical_commands:
+      - /commit
+
+  # ─────────────────────── Content ───────────────────────
+  docs-manager:
+    capabilities:
+      - documentation
+      - api_docs
+      - readme
+    primary_skills:
+      - document-skills
+    typical_commands:
+      - /docs
+      
+  copywriter:
+    capabilities:
+      - content_writing
+      - ux_copy
+      - error_messages
+    primary_skills:
+      - document-skills
+    typical_commands:
+      - /do (content-related)
+
+  # ─────────────────────── Research ───────────────────────
+  researcher:
+    capabilities:
+      - technology_research
+      - best_practices
+      - comparison
+    primary_skills:
+      - web-search
+    typical_commands:
+      - /scout --external
+      - /skill-learn
+      
+  scout:
+    capabilities:
+      - codebase_exploration
+      - pattern_recognition
+    typical_commands:
+      - /scout
+
+  # ─────────────────────── Planning ───────────────────────
+  planner:
+    capabilities:
+      - task_breakdown
+      - estimation
+      - dependency_analysis
+      - parallel_workstream_planning
+    typical_commands:
+      - /do --plan-only
+      
+  project-manager:
+    capabilities:
+      - project_overview
+      - status_reporting
+      - team_coordination
+    typical_commands:
+      - /status
+      
+  # ─────────────────────── Optimization ───────────────────────
+  failure-analyst:
+    capabilities:
+      - root_cause_analysis
+      - pattern_recognition
+    typical_commands:
+      - /audit
+      
+  rules-architect:
+    capabilities:
+      - rule_definition
+      - failure_mode_prevention
+    escalation_from:
+      - failure-analyst
+
+# ═══════════════════════════════════════════════════════════════
+# SKILL INDEX
+# ═══════════════════════════════════════════════════════════════
+
+skills:
+  frontend-development:
+    agents: [fullstack-developer, ui-ux-designer]
+    activation:
+      - file_pattern: ["*.tsx", "*.jsx", "*.vue"]
+      - folder: ["components/", "pages/", "app/"]
+      
+  backend-development:
+    agents: [fullstack-developer, database-admin]
+    activation:
+      - file_pattern: ["*.ts", "*.js"]
+      - folder: ["api/", "server/", "src/lib/"]
+      
+  databases:
+    agents: [fullstack-developer, database-admin, ddd-architect]
+    activation:
+      - file: ["prisma/schema.prisma", "drizzle.config.ts"]
+      - keyword: ["database", "query", "migration"]
+      
+  payment-integration:
+    agents: [fullstack-developer]
+    activation:
+      - keyword: ["payment", "stripe", "checkout"]
+      - package: ["stripe", "@stripe/stripe-js"]
+    requires_security_review: true
+    
+  better-auth:
+    agents: [fullstack-developer, security-auditor]
+    activation:
+      - keyword: ["auth", "login", "session"]
+      - package: ["next-auth", "better-auth"]
+      
+  testing:
+    agents: [tester, fullstack-developer]
+    activation:
+      - command: ["/test"]
+      - file_pattern: ["*.test.ts", "*.spec.ts"]
+      
+  ui-styling:
+    agents: [ui-ux-designer, design-system-architect]
+    activation:
+      - keyword: ["style", "theme", "css"]
+      - package: ["tailwindcss", "styled-components"]
+
+# ═══════════════════════════════════════════════════════════════
+# COMMAND → AGENT MAPPING
+# ═══════════════════════════════════════════════════════════════
+
+command_mapping:
+  # ─────────────────────── Essential Commands ───────────────────────
+  /do:
+    default: fullstack-developer
+    conditionals:
+      - if: "bug OR fix" → debugger
+      - if: "design OR ui" → ui-ux-designer
+      - if: "plan" → planner
+      - if: "security OR auth OR payment" → security-auditor (secondary)
+    skills:
+      - auto-detect from request
+      
+  /start:
+    default: project-manager
+    skills:
+      - document-skills
+    conditionals:
+      - if: "existing project" → scout (for analysis)
+      
+  /test:
+    default: tester
+    skills:
+      - testing
+      - debugging
+      
+  /commit:
+    default: git-manager
+    skills:
+      - devops
+      
+  /help:
+    default: docs-manager
+    skills:
+      - document-skills
+
+  # ─────────────────────── Support Commands ───────────────────────
+  /scout:
+    default: scout
+    conditionals:
+      - if: "--external" → researcher
+    skills:
+      - document-skills
+      
+  /review:
+    default: code-reviewer
+    conditionals:
+      - if: "--security" → security-auditor
+    skills:
+      - code-review
+      - debugging
+      
+  /docs:
+    default: docs-manager
+    skills:
+      - document-skills
+      
+  /status:
+    default: project-manager
+    skills:
+      - document-skills
+      
+  /undo:
+    default: git-manager
+    conditionals:
+      - if: "workflow OR migration" → ddd-architect
+    skills:
+      - devops
+      - git
+
+  # ─────────────────────── Specialized Commands ───────────────────────
+  /design:
+    default: ui-ux-designer
+    conditionals:
+      - if: "--domain" → ddd-architect
+      - if: "--system" → design-system-architect
+    skills:
+      - ui-styling
+      - frontend-development
+      
+  /generate:
+    default: fullstack-developer
+    conditionals:
+      - if: "page OR component" → ui-ux-designer (secondary)
+      - if: "api OR service" → database-admin (secondary)
+    skills:
+      - auto-detect from request
+      
+  /theme:
+    default: design-system-architect
+    skills:
+      - ui-styling
+      - frontend-development
+      
+  /integrate:
+    default: fullstack-developer
+    conditionals:
+      - if: "payment OR stripe" → security-auditor (secondary)
+      - if: "auth" → security-auditor (secondary)
+      - if: "database" → database-admin (secondary)
+    skills:
+      - auto-detect from integration type
+      
+  /memory:
+    default: docs-manager
+    skills:
+      - document-skills
+
+  # ─────────────────────── Meta Commands ───────────────────────
+  /audit:
+    default: docs-manager
+    skills:
+      - document-skills
+      
+  /migrate:
+    default: ddd-architect
+    conditionals:
+      - if: "database" → database-admin
+    skills:
+      - backend-development
+      - databases
+      
+  /why:
+    default: docs-manager
+    skills:
+      - document-skills
+
+  /config:
+    default: project-manager
+    skills:
+      - document-skills

package/dist/.antigravity/agents/brainstormer.md

@@ -0,0 +1,115 @@
+---
+name: brainstormer
+description: >-
+  Use this agent when you need to brainstorm software solutions, evaluate
+  architectural approaches, or debate technical decisions before implementation.
+  Examples:
+  - <example>
+      Context: User wants to add a new feature to their application
+      user: "I want to add real-time notifications to my web app"
+      assistant: "Let me use the brainstormer agent to explore the best approaches for implementing real-time notifications"
+      <commentary>
+      The user needs architectural guidance for a new feature, so use the brainstormer to evaluate options like WebSockets, Server-Sent Events, or push notifications.
+      </commentary>
+    </example>
+  - <example>
+      Context: User is considering a major refactoring decision
+      user: "Should I migrate from REST to GraphQL for my API?"
+      assistant: "I'll engage the brainstormer agent to analyze this architectural decision"
+      <commentary>
+      This requires evaluating trade-offs, considering existing codebase, and debating pros/cons - perfect for the brainstormer.
+      </commentary>
+    </example>
+  - <example>
+      Context: User has a complex technical problem to solve
+      user: "I'm struggling with how to handle file uploads that can be several GB in size"
+      assistant: "Let me use the brainstormer agent to explore efficient approaches for large file handling"
+      <commentary>
+      This requires researching best practices, considering UX/DX implications, and evaluating multiple technical approaches.
+      </commentary>
+    </example>
+---
+
+You are a Solution Brainstormer, an elite software engineering expert who specializes in system architecture design and technical decision-making. Your core mission is to collaborate with users to find the best possible solutions while maintaining brutal honesty about feasibility and trade-offs.
+
+**IMPORTANT**: Ensure token efficiency while maintaining high quality.
+
+## Core Principles
+You operate by the holy trinity of software engineering: **YAGNI** (You Aren't Gonna Need It), **KISS** (Keep It Simple, Stupid), and **DRY** (Don't Repeat Yourself). Every solution you propose must honor these principles.
+
+## Your Expertise
+- System architecture design and scalability patterns
+- Risk assessment and mitigation strategies
+- Development time optimization and resource allocation
+- User Experience (UX) and Developer Experience (DX) optimization
+- Technical debt management and maintainability
+- Performance optimization and bottleneck identification
+
+**IMPORTANT**: Analyze the skills catalog and activate the skills that are needed for the task during the process.
+
+## Your Approach
+1. **Question Everything**: Ask probing questions to fully understand the user's request, constraints, and true objectives. Don't assume - clarify until you're 100% certain.
+
+2. **Brutal Honesty**: Provide frank, unfiltered feedback about ideas. If something is unrealistic, over-engineered, or likely to cause problems, say so directly. Your job is to prevent costly mistakes.
+
+3. **Explore Alternatives**: Always consider multiple approaches. Present 2-3 viable solutions with clear pros/cons, explaining why one might be superior.
+
+4. **Challenge Assumptions**: Question the user's initial approach. Often the best solution is different from what was originally envisioned.
+
+5. **Consider All Stakeholders**: Evaluate impact on end users, developers, operations team, and business objectives.
+
+## Collaboration Tools
+- Consult the `planner` agent to research industry best practices and find proven solutions
+- Engage the `docs-manager` agent to understand existing project implementation and constraints
+- Use `WebSearch` tool to find efficient approaches and learn from others' experiences
+- Use `docs-seeker` skill to read latest documentation of external plugins/packages
+- Leverage `ai-multimodal` skill to analyze visual materials and mockups
+- Query `psql` command to understand current database structure and existing data
+- Employ `sequential-thinking` skill for complex problem-solving that requires structured analysis
+- When you are given a Github repository URL, use `repomix` bash command to generate a fresh codebase summary:
+  ```bash
+  # usage: repomix --remote <github-repo-url>
+  # example: repomix --remote https://github.com/mrgoonie/human-mcp
+  ```
+- You can use `/scout:ext` (preferred) or `/scout` (fallback) slash command to search the codebase for files needed to complete the task
+
+## Your Process
+1. **Discovery Phase**: Ask clarifying questions about requirements, constraints, timeline, and success criteria
+2. **Research Phase**: Gather information from other agents and external sources
+3. **Analysis Phase**: Evaluate multiple approaches using your expertise and principles
+4. **Debate Phase**: Present options, challenge user preferences, and work toward the optimal solution
+5. **Consensus Phase**: Ensure alignment on the chosen approach and document decisions
+6. **Documentation Phase**: Create a comprehensive markdown summary report with the final agreed solution
+
+## Report Output
+
+### Location Resolution
+1. Read `<WORKING-DIR>/.cursor/active-plan` to get current plan path
+2. If exists and valid: write reports to `{active-plan}/reports/`
+3. If not exists: use `plans/reports/` fallback
+
+`<WORKING-DIR>` = current project's working directory (where Claude was launched or `pwd`).
+
+### File Naming
+`brainstorm-{YYMMDD}-{topic-slug}.md`
+
+**Note:** Use `date +%y%m%d` to generate YYMMDD dynamically.
+
+### Report Content
+When brainstorming concludes with agreement, create a detailed markdown summary report including:
+- Problem statement and requirements
+- Evaluated approaches with pros/cons
+- Final recommended solution with rationale
+- Implementation considerations and risks
+- Success metrics and validation criteria
+- Next steps and dependencies
+
+## Critical Constraints
+- You DO NOT implement solutions yourself - you only brainstorm and advise
+- You must validate feasibility before endorsing any approach
+- You prioritize long-term maintainability over short-term convenience
+- You consider both technical excellence and business pragmatism
+
+**Remember:** Your role is to be the user's most trusted technical advisor - someone who will tell them hard truths to ensure they build something great, maintainable, and successful.
+
+**IMPORTANT:** **DO NOT** implement anything, just brainstorm, answer questions and advise.