anchi-kit 1.2.0 → 1.2.2

package/.antigravity/skills/problem-solving/references/scale-game.md

@@ -1,95 +0,0 @@
-# Scale Game
-
-Test at extremes (1000x bigger/smaller, instant/year-long) to expose fundamental truths hidden at normal scales.
-
-## Core Principle
-
-**Extremes expose fundamentals.** What works at one scale fails at another.
-
-## When to Use
-
-| Symptom | Action |
-|---------|--------|
-| "Should scale fine" (without testing) | Test at extremes |
-| Uncertain about production behavior | Scale up 1000x |
-| Edge cases unclear | Test minimum and maximum |
-| Architecture validation needed | Extreme testing |
-
-## Quick Reference
-
-| Scale Dimension | Test At Extremes | What It Reveals |
-|-----------------|------------------|-----------------|
-| **Volume** | 1 item vs 1B items | Algorithmic complexity limits |
-| **Speed** | Instant vs 1 year | Async requirements, caching needs |
-| **Users** | 1 user vs 1B users | Concurrency issues, resource limits |
-| **Duration** | Milliseconds vs years | Memory leaks, state growth |
-| **Failure rate** | Never fails vs always fails | Error handling adequacy |
-
-## Process
-
-1. **Pick dimension** - What could vary extremely?
-2. **Test minimum** - What if 1000x smaller/faster/fewer?
-3. **Test maximum** - What if 1000x bigger/slower/more?
-4. **Note what breaks** - Where do limits appear?
-5. **Note what survives** - What's fundamentally sound?
-6. **Design for reality** - Use insights to validate architecture
-
-## Detailed Examples
-
-### Example 1: Error Handling
-- **Normal scale:** "Handle errors when they occur" works fine
-- **At 1B scale:** Error volume overwhelms logging, crashes system
-- **Reveals:** Need to make errors impossible (type systems) or expect them (chaos engineering)
-- **Action:** Design error handling for volume, not just occurrence
-
-### Example 2: Synchronous APIs
-- **Normal scale:** Direct function calls work, < 100ms latency
-- **At global scale:** Network latency makes synchronous unusable (200-500ms)
-- **Reveals:** Async/messaging becomes survival requirement, not optimization
-- **Action:** Design async-first from start
-
-### Example 3: In-Memory State
-- **Normal duration:** Works for hours/days in development
-- **At years:** Memory grows unbounded, eventual crash (weeks → months → years)
-- **Reveals:** Need persistence or periodic cleanup, can't rely on memory forever
-- **Action:** Design for stateless or externalized state
-
-### Example 4: Single vs Million Users
-- **Normal scale:** Session in memory works for 100 users
-- **At 1M scale:** Memory exhausted, server crashes
-- **Reveals:** Need distributed session store (Redis, database)
-- **Action:** Design for horizontal scaling from start
-
-## Both Directions Matter
-
-**Test smaller too:**
-- What if only 1 user? Does complexity make sense?
-- What if only 10 items? Is optimization premature?
-- What if instant response? What becomes unnecessary?
-
-Often reveals over-engineering or premature optimization.
-
-## Red Flags
-
-You need scale game when:
-- "It works in dev" (but will it work in production?)
-- No idea where limits are
-- "Should scale fine" (without evidence)
-- Surprised by production behavior
-- Architecture feels arbitrary
-
-## Success Metrics
-
-After scale game, you should know:
-- Where system breaks (exact limits)
-- What survives (fundamentally sound parts)
-- What needs redesign (scale-dependent)
-- Production readiness (validated architecture)
-
-## Remember
-
-- Extremes reveal fundamentals hidden at normal scales
-- What works at one scale fails at another
-- Test BOTH directions (bigger AND smaller)
-- Use insights to validate architecture early
-- Don't guess - test at extremes

package/.antigravity/skills/problem-solving/references/simplification-cascades.md

@@ -1,80 +0,0 @@
-# Simplification Cascades
-
-Find one insight eliminating multiple components. "If this is true, we don't need X, Y, Z."
-
-## Core Principle
-
-**Everything is a special case of...** collapses complexity dramatically.
-
-One powerful abstraction > ten clever hacks.
-
-## When to Use
-
-| Symptom | Action |
-|---------|--------|
-| Same thing implemented 5+ ways | Abstract the common pattern |
-| Growing special case list | Find the general case |
-| Complex rules with exceptions | Find rule with no exceptions |
-| Excessive config options | Find defaults working for 95% |
-
-## The Pattern
-
-**Look for:**
-- Multiple implementations of similar concepts
-- Special case handling everywhere
-- "We need to handle A, B, C, D differently..."
-- Complex rules with many exceptions
-
-**Ask:** "What if they're all the same thing underneath?"
-
-## Examples
-
-### Example 1: Stream Abstraction
-- **Before:** Separate handlers for batch/real-time/file/network data
-- **Insight:** "All inputs are streams - just different sources"
-- **After:** One stream processor, multiple stream sources
-- **Eliminated:** 4 separate implementations
-
-### Example 2: Resource Governance
-- **Before:** Session tracking, rate limiting, file validation, connection pooling (all separate)
-- **Insight:** "All are per-entity resource limits"
-- **After:** One ResourceGovernor with 4 resource types
-- **Eliminated:** 4 custom enforcement systems
-
-### Example 3: Immutability
-- **Before:** Defensive copying, locking, cache invalidation, temporal coupling
-- **Insight:** "Treat everything as immutable data + transformations"
-- **After:** Functional programming patterns
-- **Eliminated:** Entire classes of synchronization problems
-
-## Process
-
-1. **List variations** - What's implemented multiple ways?
-2. **Find essence** - What's the same underneath?
-3. **Extract abstraction** - What's the domain-independent pattern?
-4. **Test fit** - Do all cases fit cleanly?
-5. **Measure cascade** - How many things become unnecessary?
-
-## Red Flags
-
-Signs you're missing a cascade:
-- "Just need to add one more case..." (repeating forever)
-- "These are similar but different" (maybe they're the same?)
-- Refactoring feels like whack-a-mole (fix one, break another)
-- Growing configuration file
-- "Don't touch that, it's complicated" (complexity hiding pattern)
-
-## Success Metrics
-
-- **10x wins, not 10% improvements**
-- Measure in "how many things can we delete?"
-- Lines of code removed > lines added
-- Configuration options eliminated
-- Special cases unified
-
-## Remember
-
-- The pattern is usually already there, just needs recognition
-- Valid cascades feel obvious in retrospect
-- Test with "can this handle all existing cases?"
-- Document the insight for future reference

package/.antigravity/skills/problem-solving/references/when-stuck.md

@@ -1,72 +0,0 @@
-# When Stuck - Problem-Solving Dispatch
-
-Different stuck-types need different techniques. Match stuck-symptom to technique.
-
-## Dispatch Flowchart
-
-```
-YOU'RE STUCK
-│
-├─ Complexity spiraling? Same thing 5+ ways? Growing special cases?
-│  └─→ USE: Simplification Cascades
-│
-├─ Can't find fitting approach? Conventional solutions inadequate?
-│  └─→ USE: Collision-Zone Thinking
-│
-├─ Same issue different places? Reinventing wheels? Feels familiar?
-│  └─→ USE: Meta-Pattern Recognition
-│
-├─ Solution feels forced? "Must be done this way"? Stuck on assumptions?
-│  └─→ USE: Inversion Exercise
-│
-├─ Will this work at production? Edge cases unclear? Unsure of limits?
-│  └─→ USE: Scale Game
-│
-└─ Code broken? Wrong behavior? Test failing?
-   └─→ USE: Debugging skill (systematic-debugging)
-```
-
-## Stuck-Type → Technique Map
-
-| How You're Stuck | Symptom Details | Use This |
-|------------------|-----------------|----------|
-| **Complexity spiraling** | Same thing 5+ ways, growing special cases, excessive if/else | simplification-cascades.md |
-| **Need innovation** | Conventional inadequate, can't find fitting approach, need breakthrough | collision-zone-thinking.md |
-| **Recurring patterns** | Same issue different places, reinventing wheels, déjà vu feeling | meta-pattern-recognition.md |
-| **Forced by assumptions** | "Must be done this way", can't question premise, forced solution | inversion-exercise.md |
-| **Scale uncertainty** | Production unclear, edge cases unknown, unsure of limits | scale-game.md |
-| **Code broken** | Wrong behavior, test failing, unexpected output | debugging skill |
-
-## Process
-
-1. **Identify stuck-type** - What symptom matches above?
-2. **Load that technique** - Read the specific reference file
-3. **Apply technique** - Follow its process
-4. **Document attempt** - What worked/failed?
-5. **If still stuck** - Try different technique or combine
-
-## Combining Techniques
-
-Some problems need multiple techniques:
-
-- **Simplification + Meta-pattern** - Find pattern → simplify all instances
-- **Collision + Inversion** - Force metaphor → invert assumptions
-- **Scale + Simplification** - Test extremes → reveal what to eliminate
-- **Meta-pattern + Scale** - Universal pattern → test at extremes
-
-## When Nothing Works
-
-If no technique helps:
-1. **Reframe problem** - Are you solving the right problem?
-2. **Get fresh perspective** - Explain to someone else
-3. **Take break** - Distance often reveals solution
-4. **Simplify scope** - Solve smaller version first
-5. **Question constraints** - Are they real or assumed?
-
-## Remember
-
-- Match symptom to technique
-- One technique at a time
-- Combine if first doesn't work
-- Document what you tried
-- Not stuck forever, just temporarily

package/.antigravity/skills/repomix/references/configuration.md

@@ -1,211 +0,0 @@
-# Configuration Reference
-
-Detailed configuration options for Repomix.
-
-## Configuration File
-
-Create `repomix.config.json` in project root:
-
-```json
-{
-  "output": {
-    "filePath": "repomix-output.xml",
-    "style": "xml",
-    "removeComments": false,
-    "showLineNumbers": true,
-    "copyToClipboard": false
-  },
-  "include": ["**/*"],
-  "ignore": {
-    "useGitignore": true,
-    "useDefaultPatterns": true,
-    "customPatterns": ["additional-folder", "**/*.log", "**/tmp/**"]
-  },
-  "security": {
-    "enableSecurityCheck": true
-  }
-}
-```
-
-### Output Options
-
-- `filePath`: Output file path (default: `repomix-output.xml`)
-- `style`: Format - `xml`, `markdown`, `json`, `plain` (default: `xml`)
-- `removeComments`: Strip comments (default: `false`). Supports HTML, CSS, JS/TS, Vue, Svelte, Python, PHP, Ruby, C, C#, Java, Go, Rust, Swift, Kotlin, Dart, Shell, YAML
-- `showLineNumbers`: Include line numbers (default: `true`)
-- `copyToClipboard`: Auto-copy output (default: `false`)
-
-### Include/Ignore
-
-- `include`: Glob patterns for files to include (default: `["**/*"]`)
-- `useGitignore`: Respect .gitignore (default: `true`)
-- `useDefaultPatterns`: Use default ignore patterns (default: `true`)
-- `customPatterns`: Additional ignore patterns (same format as .gitignore)
-
-### Security
-
-- `enableSecurityCheck`: Scan for sensitive data with Secretlint (default: `true`)
-- Detects: API keys, passwords, credentials, private keys, AWS secrets, DB connections
-
-## Glob Patterns
-
-**Wildcards:**
-- `*` - Any chars except `/`
-- `**` - Any chars including `/`
-- `?` - Single char
-- `[abc]` - Char from set
-- `{js,ts}` - Either extension
-
-**Examples:**
-- `**/*.ts` - All TypeScript
-- `src/**` - Specific dir
-- `**/*.{js,jsx,ts,tsx}` - Multiple extensions
-- `!**/*.test.ts` - Exclude tests
-
-### CLI Options
-
-```bash
-# Include patterns
-repomix --include "src/**/*.ts,*.md"
-
-# Ignore patterns
-repomix -i "tests/**,*.test.js"
-
-# Disable .gitignore
-repomix --no-gitignore
-
-# Disable defaults
-repomix --no-default-patterns
-```
-
-### .repomixignore File
-
-Create `.repomixignore` for Repomix-specific patterns (same format as .gitignore):
-
-```
-# Build artifacts
-dist/
-build/
-*.min.js
-out/
-
-# Test files
-**/*.test.ts
-**/*.spec.ts
-coverage/
-__tests__/
-
-# Dependencies
-node_modules/
-vendor/
-packages/*/node_modules/
-
-# Large files
-*.mp4
-*.zip
-*.tar.gz
-*.iso
-
-# Sensitive files
-.env*
-secrets/
-*.key
-*.pem
-
-# IDE files
-.vscode/
-.idea/
-*.swp
-
-# Logs
-logs/
-**/*.log
-```
-
-### Pattern Precedence
-
-Order (highest to lowest priority):
-1. CLI ignore patterns (`-i`)
-2. `.repomixignore` file
-3. Custom patterns in config
-4. `.gitignore` (if enabled)
-5. Default patterns (if enabled)
-
-### Pattern Examples
-
-**TypeScript:**
-```json
-{"include": ["**/*.ts", "**/*.tsx"], "ignore": {"customPatterns": ["**/*.test.ts", "dist/"]}}
-```
-
-**React:**
-```json
-{"include": ["src/**/*.{js,jsx,ts,tsx}", "*.md"], "ignore": {"customPatterns": ["build/"]}}
-```
-
-**Monorepo:**
-```json
-{"include": ["packages/*/src/**"], "ignore": {"customPatterns": ["packages/*/dist/"]}}
-```
-
-## Output Formats
-
-### XML (Default)
-```bash
-repomix --style xml
-```
-Structured AI consumption. Features: tags, hierarchy, metadata, AI-optimized separators.
-Use for: LLMs, structured analysis, programmatic parsing.
-
-### Markdown
-```bash
-repomix --style markdown
-```
-Human-readable with syntax highlighting. Features: syntax highlighting, headers, TOC.
-Use for: documentation, code review, sharing.
-
-### JSON
-```bash
-repomix --style json
-```
-Programmatic processing. Features: structured data, easy parsing, metadata.
-Use for: API integration, custom tooling, data analysis.
-
-### Plain Text
-```bash
-repomix --style plain
-```
-Simple concatenation. Features: no formatting, minimal overhead.
-Use for: simple analysis, minimal processing.
-
-## Advanced Options
-
-```bash
-# Verbose - show processing details
-repomix --verbose
-
-# Custom config file
-repomix -c /path/to/custom-config.json
-
-# Initialize config
-repomix --init
-
-# Disable line numbers - smaller output
-repomix --no-line-numbers
-```
-
-### Performance
-
-**Worker Threads:** Parallel processing handles large codebases efficiently (e.g., facebook/react: 29x faster, 123s → 4s)
-
-**Optimization:**
-```bash
-# Exclude unnecessary files
-repomix -i "node_modules/**,dist/**,*.min.js"
-
-# Specific directories only
-repomix --include "src/**/*.ts"
-
-# Remove comments, disable line numbers
-repomix --remove-comments --no-line-numbers
-```

package/.antigravity/skills/repomix/references/usage-patterns.md

@@ -1,232 +0,0 @@
-# Usage Patterns
-
-Practical workflows and patterns for using Repomix in different scenarios.
-
-## AI Analysis Workflows
-
-### Full Repository
-```bash
-repomix --remove-comments --style markdown -o full-repo.md
-```
-**Use:** New codebase, architecture review, complete LLM context, planning
-**Tips:** Remove comments, use markdown, check token limits, review before sharing
-
-### Focused Module
-```bash
-repomix --include "src/auth/**,src/api/**" -o modules.xml
-```
-**Use:** Feature analysis, debugging specific areas, targeted refactoring
-**Tips:** Include related files only, stay within token limits, use XML for AI
-
-### Incremental Analysis
-```bash
-git checkout feature-branch && repomix --include "src/**" -o feature.xml
-git checkout main && repomix --include "src/**" -o main.xml
-```
-**Use:** Feature branch review, change impact, before/after comparison, migration planning
-
-### Cross-Repository
-```bash
-npx repomix --remote org/repo1 -o repo1.xml
-npx repomix --remote org/repo2 -o repo2.xml
-```
-**Use:** Microservices, library comparisons, consistency checks, integration analysis
-
-## Security Audit
-
-### Third-Party Library
-```bash
-npx repomix --remote vendor/library --style xml -o audit.xml
-```
-**Workflow:** Package library → enable security checks → review vulnerabilities → check suspicious patterns → AI analysis
-**Check for:** API keys, hardcoded credentials, network calls, obfuscation, malicious patterns
-
-### Pre-Deployment
-```bash
-repomix --include "src/**,config/**" --style xml -o pre-deploy-audit.xml
-```
-**Checklist:** No sensitive data, no test credentials, env vars correct, security practices, no debug code
-
-### Dependency Audit
-```bash
-repomix --include "**/package.json,**/package-lock.json" -o deps.md --style markdown
-repomix --include "node_modules/suspicious-package/**" -o dep-audit.xml
-```
-**Use:** Suspicious dependency, security advisory, license compliance, vulnerability assessment
-
-### Compliance
-```bash
-repomix --include "src/**,LICENSE,README.md,docs/**" --style markdown -o compliance.md
-```
-**Include:** Source, licenses, docs, configs. **Exclude:** Test data, dependencies
-
-## Documentation
-
-### Doc Context
-```bash
-repomix --include "src/**,docs/**,*.md" --style markdown -o doc-context.md
-```
-**Use:** API docs, architecture docs, user guides, onboarding
-**Tips:** Include existing docs, include source, use markdown
-
-### API Documentation
-```bash
-repomix --include "src/api/**,src/routes/**,src/controllers/**" --remove-comments -o api-context.xml
-```
-**Include:** Routes, controllers, schemas, middleware
-**Workflow:** Package → AI → OpenAPI/Swagger → endpoint docs → examples
-
-### Architecture
-```bash
-repomix --include "src/**/*.ts,*.md" -i "**/*.test.ts" --style markdown -o architecture.md
-```
-**Focus:** Module structure, dependencies, design patterns, data flow
-
-### Examples
-```bash
-repomix --include "examples/**,demos/**,*.example.js" --style markdown -o examples.md
-```
-
-## Library Evaluation
-
-### Quick Assessment
-```bash
-npx repomix --remote owner/library --style markdown -o library-eval.md
-```
-**Evaluate:** Code quality, architecture, dependencies, tests, docs, maintenance
-
-### Feature Comparison
-```bash
-npx repomix --remote owner/lib-a --style xml -o lib-a.xml
-npx repomix --remote owner/lib-b --style xml -o lib-b.xml
-```
-**Compare:** Features, API design, performance, bundle size, dependencies, maintenance
-
-### Integration Feasibility
-```bash
-npx repomix --remote vendor/library --include "src/**,*.md" -o library.xml
-repomix --include "src/integrations/**" -o our-integrations.xml
-```
-Analyze compatibility between target library and your integration points
-
-### Migration Planning
-```bash
-repomix --include "node_modules/old-lib/**" -o old-lib.xml
-npx repomix --remote owner/new-lib -o new-lib.xml
-```
-Compare current vs target library, analyze usage patterns
-
-## Workflow Integration
-
-### CI/CD
-```yaml
-# GitHub Actions
-- name: Generate Snapshot
-  run: |
-    npm install -g repomix
-    repomix --style markdown -o release-snapshot.md
-- name: Upload Artifact
-  uses: actions/upload-artifact@v3
-  with: {name: repo-snapshot, path: release-snapshot.md}
-```
-**Use:** Release docs, compliance archives, change tracking, audit trails
-
-### Git Hooks
-```bash
-#!/bin/bash
-# .git/hooks/pre-commit
-git diff --cached --name-only > staged-files.txt
-repomix --include "$(cat staged-files.txt | tr '\n' ',')" -o .context/latest.xml
-```
-
-### IDE (VS Code)
-```json
-{"version": "2.0.0", "tasks": [{"label": "Package for AI", "type": "shell", "command": "repomix --include 'src/**' --remove-comments --copy"}]}
-```
-
-### Cursor
-```bash
-repomix --style markdown --copy  # Then paste into Claude
-```
-
-## Language-Specific Patterns
-
-### TypeScript
-```bash
-repomix --include "**/*.ts,**/*.tsx" --remove-comments --no-line-numbers
-```
-**Exclude:** `**/*.test.ts`, `dist/`, `coverage/`
-
-### React
-```bash
-repomix --include "src/**/*.{js,jsx,ts,tsx},public/**" -i "build/,*.test.*"
-```
-**Include:** Components, hooks, utils, public assets
-
-### Node.js Backend
-```bash
-repomix --include "src/**/*.js,config/**" -i "node_modules/,logs/,tmp/"
-```
-**Focus:** Routes, controllers, models, middleware, configs
-
-### Python
-```bash
-repomix --include "**/*.py,requirements.txt,*.md" -i "**/__pycache__/,venv/"
-```
-**Exclude:** `__pycache__/`, `*.pyc`, `venv/`, `.pytest_cache/`
-
-### Monorepo
-```bash
-repomix --include "packages/*/src/**" -i "packages/*/node_modules/,packages/*/dist/"
-```
-**Consider:** Package-specific patterns, shared deps, cross-package refs, workspace structure
-
-## Troubleshooting
-
-### Output Too Large
-**Problem:** Exceeds LLM token limits
-**Fix:**
-```bash
-repomix -i "node_modules/**,dist/**,coverage/**" --include "src/core/**" --remove-comments --no-line-numbers
-```
-
-### Missing Files
-**Problem:** Expected files not included
-**Debug:**
-```bash
-cat .gitignore .repomixignore  # Check ignore patterns
-repomix --no-gitignore --no-default-patterns --verbose
-```
-
-### Sensitive Data Warnings
-**Problem:** Security scanner flags secrets
-**Actions:** Review files → add to `.repomixignore` → remove sensitive data → use env vars
-```bash
-repomix --no-security-check  # Use carefully for false positives
-```
-
-### Performance Issues
-**Problem:** Slow on large repo
-**Optimize:**
-```bash
-repomix --include "src/**/*.ts" -i "node_modules/**,dist/**,vendor/**"
-```
-
-### Remote Access
-**Problem:** Cannot access remote repo
-**Fix:**
-```bash
-npx repomix --remote https://github.com/owner/repo  # Full URL
-npx repomix --remote https://github.com/owner/repo/commit/abc123  # Specific commit
-# For private: clone first, run locally
-```
-
-## Best Practices
-
-**Planning:** Define scope → identify files → check token limits → consider security
-
-**Execution:** Start broad, refine narrow → use appropriate format → enable security checks → monitor tokens
-
-**Review:** Verify no sensitive data → check completeness → validate format → test with LLM
-
-**Iteration:** Refine patterns → adjust format → optimize tokens → document patterns