codehava-agent-kit 1.0.1 → 2.0.0

package/README.md

@@ -1,56 +1,49 @@
-# Codehava Agent Kit
+# Codehava Antigravity Agent Kit 🚀
 
-A powerful CLI tool to scaffold custom AI Agent templates, workflows, skills, and "Vibe Coding" memory protocols into any project. Dengan alat ini, kamu bisa menyulap AI IDE apa pun (Cursor, Claude Code, GitHub Copilot) menjadi *Software Engineer* profesional yang mematuhi standar kerja timmu 100%.
+The ultimate **Vibe Coding** Agent Kit boilerplate designed to turn plain-text ideas into production-ready Web and Mobile applications seamlessly. Codehava Agent Kit is specifically curated to inject superhuman coding capabilities into Cursor, Antigravity, or Claude Code.
 
-## 🌟 Fitur Unggulan (The Ultimate Vibe Coding Arsenal)
+## 🌟 What's Inside?
 
-- **Workflows (Slash Commands):** Perintah bawaan seperti `/vibe-plan`, `/new-feature`, `/health-check`, dan **`/vibe-recap`** (untuk merekap dan memulihkan memori konteks obrolan yang sudah terlalu panjang).
-- **Skills (Konteks Spesifik):** Ratusan injeksi trik spesifik yang memanipulasi kepribadian dan pengetahuan AI. Misalnya *Skill* `nextjs-api-route`, `vibe-prd`, `backend_security`.
-- **Code Snippets (`.agent/snippets/`):** Memaksa AI untuk mencontek *template* atau kerangka kode standar proyekmu tiap kali ia diminta membuat file baru (misal: `@react-component-template.tsx`).
-- **Self-Improving Memory:** Menggunakan file sakti `.antigravity/rules.md` yang secara permanen **memaksa AI** untuk selalu mencatat _error_ di file `docs/troubleshooting.md`, dan melakukan langkah kerja secara bertahap menggunakan daftar Checklist `[ ]` di `docs/task_on_hand.md`.
+We've supercharged this kit to be fully autonomous, meaning you **no longer need to memorize skill names or syntax**.
 
----
+1. **Auto-Discovery Engine (450+ Elite Skills):**
+   This kit ships with ~455 hand-picked, elite-tier skills inside the `.agent/skills/` directory (Frontend, Backend, Security, React, Next.js, and Mobile). Depending on your natural language prompt, the AI will *automatically discover*, load, and route tasks to the best skill seamlessly. 
 
-## 🚀 Cara Instalasi & Penggunaan
+2. **Long-Term Memory Protocol (`MEMORY.md`):**
+   Vibe coding sessions can go on for hours. To prevent your AI from forgetting initial architectural decisions, the kit enforces an autonomous memory state. The AI will quietly maintain a `.agent/MEMORY.md` file to preserve colors, database schemas, and global context permanently.
 
-### 1. Inisialisasi Proyek Baru
-Di dalam direktori proyek aplikasimu (terminal), jalankan perintah berikut:
+3. **Vibe Workflow (Skill Chaining):**
+   Say goodbye to rushy, hallucinated code. When you ask the agent to build a new feature, the Agent Kit forces a staged pipeline:
+   `vibe-prd` ➔ `vibe-techdesign` ➔ `coding specialist`.
 
-```bash
-npx codehava-agent-kit init
-```
-
-*CLI ini akan secara otomatis menyebarkan folder `.agent`, `.antigravity`, `docs`, `specs`, dan file `AGENTS.md` langsung ke dalam proyekmu.*
+4. **Self-Healing Protocol:**
+   Encountered a syntax error? Let the AI handle it autonomously using `@systematic-debugging` and `@lint-and-validate` skills without asking you "how to fix this stack trace".
 
-### 2. Cara Menggunakannya di AI Editor (Cursor, dll)
+5. **Built-in Vibe MCP Servers:**
+   Pre-configured `mcp_config.json` integrating:
+   - **Brave Search / Tavily:** Real-time documentation web scraping to fight AI hallucinations.
+   - **Sequential Thinking:** An Anthropic-approved system for logical AI braking.
+   - **Figma & Google Stitch:** Direct integration to extract design DNA straight into code.
 
-Setelah di-inisialisasi, instruksikan AI Anda untuk mengikuti standar operasional (*SOP*) yang telah dibuat. 
-Sebagai contoh, ketikkan ini di awal *chat* pada editor kamu:
+## 📦 Installation & Usage
 
-> *"Mulai bekerja. Tolong baca AGENTS.md terlebih dahulu, lalu kerjakan fitur login menggunakan /new-feature."*
+You can initialize this kit in any empty directory to begin your vibe coding journey:
 
-AI secara ajaib akan mematuhi semua aturan kode, menyelaraskan desain dengan `docs/SRS-Template.md`, dan menggunakan *Code Snippets* lokal.
+```bash
+npx codehava-agent-kit init
+```
 
-### 3. Mereset / Menyegarkan Memori AI (Context Compaction)
-Jika percakapan AI di dalam proyekmu sudah terlalu panjang dan ia mulai merespons sembarangan ("halusinasi"):
-1. Ketik `/recap` atau `/vibe-recap` di *chat*.
-2. AI akan memindahkan seluruh isi otak sementaranya ke dalam file `docs/recap.md`.
-3. Buka *Chat* yang benar-benar baru, dan katakan: *"Lanjutkan pekerjaan berdasarkan docs/recap.md"*. Memori segarnya akan kembali fokus ke target utama!
+*This command will install the `.agent/`, `docs/`, `specs/` directories and prompt a successful connection.*
 
----
+## ⚡ How to "Vibe Code"
 
-## 🛠 Aturan Kustomisasi (Untuk Maintainer)
+1. Open the initialized folder in your AI IDE (Antigravity, Cursor, etc.).
+2. Tell it what you want in human language:
+   > *"Tolong buatkan saya aplikasi POS kasir. Gunakan nextjs-app-router dan UI modern dengan dark mode."*
+3. Watch the Magic happen. The AI will Auto-Discover the best matching framework, record the session memory, and generate interactive, animated UI out of the box using `ui-ux-pro-max` guidelines!
 
-Jika kamu ingin memperbarui isi standar dari Agent Kit ini untuk digunakan semua orang di timmu:
+## 🔧 Excluded Bloat
+We've pruned over 800+ niche/outdated community skills to ensure this NPM module is incredibly light and fast during the initialization process. Your IDE will load context in milliseconds.
 
-1. Edit konten *markdown* yang ada di dalam folder `templates/`.
-2. Jika ada *snippet* kode yang sering dipakai di perusahaanmu, masukkan ke `templates/.agent/snippets/`.
-3. Test secara lokal:
-   ```bash
-   npm link
-   codehava-agent-kit init
-   ```
-4. Jika sudah oke, rilis versinya secara publik:
-   ```bash
-   npm publish
-   ```
+## License
+MIT License - Codehava

package/bin/cli.js

@@ -39,14 +39,10 @@ program
       // Copy template to user's directory
       await fs.copy(sourceDir, targetDir, {
         overwrite: true,
-        filter: (src) => !src.includes('.DS_Store')
+        filter: (src) => !src.includes('.DS_Store') && !src.includes('skills-archive')
       });
       
-      console.log(chalk.green('✅ Successfully initialized Agent Kit!'));
-      console.log(chalk.white('   Folders added: .agent, .antigravity, docs, specs.'));
-      console.log(chalk.white('   Files added: AGENTS.md'));
-      console.log('');
-      console.log(chalk.cyan('   You are now ready to use Codehava workflows and skills!'));
+      console.log(chalk.green('\n✅ Selamat! Codehava Antigravity Agent Kit Connected\n'));
       
     } catch (err) {
       console.error(chalk.red('❌ Failed to initialize Agent Kit:'), err);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "codehava-agent-kit",
-  "version": "1.0.1",
+  "version": "2.0.0",
   "description": "Codehava Agent Kit - CLI to initialize agent templates, workflows, and skills",
   "main": "index.js",
   "type": "module",

package/templates/.agent/AGENTS_INDEX.md

@@ -1,26 +1,13 @@
-# Master Agents Index
+# Auto-Discovery Agent Persona Mechanism
 
-AI, whenever you are assigned a task, scan this list to determine which Agent Persona you should adopt. Read the full agent file at `templates/.agent/agents/<agent-name>.md` to load your persona BEFORE coding.
+> [!WARNING]
+> STATIC INDEX OBSOLETE: We explicitly removed the hardcoded `AGENTS_INDEX.md` mapping file because maintaining an index for Vibe Coding personas is obsolete.
 
-- **ai-engineer**: Expert in Large Language Models (LLMs), RAG pipelines, Vector Databases (Pinecone/pgvector), LangChain, and integrating OpenAI/Anthropic/Gemini APIs into production applications. Triggers on ai, llm, rag, vector, embedding, openai, gemini, prompt.
-- **backend-specialist**: Expert backend architect for Node.js, Python, and modern serverless/edge systems. Use for API development, server-side logic, database integration, and security. Triggers on backend, server, api, endpoint, database, auth.
-- **code-archaeologist**: Expert in legacy code, refactoring, and understanding undocumented systems. Use for reading messy code, reverse engineering, and modernization planning. Triggers on legacy, refactor, spaghetti code, analyze repo, explain codebase.
-- **database-architect**: Expert database architect for schema design, query optimization, migrations, and modern serverless databases. Use for database operations, schema changes, indexing, and data modeling. Triggers on database, sql, schema, migration, query, postgres, index, table.
-- **debugger**: Expert in systematic debugging, root cause analysis, and crash investigation. Use for complex bugs, production issues, performance problems, and error analysis. Triggers on bug, error, crash, not working, broken, investigate, fix.
-- **devops-engineer**: Expert in deployment, server management, CI/CD, and production operations. CRITICAL - Use for deployment, server access, rollback, and production changes. HIGH RISK operations. Triggers on deploy, production, server, pm2, ssh, release, rollback, ci/cd.
-- **documentation-writer**: Expert in technical documentation. Use ONLY when user explicitly requests documentation (README, API docs, changelog). DO NOT auto-invoke during normal development.
-- **explorer-agent**: Advanced codebase discovery, deep architectural analysis, and proactive research agent. The eyes and ears of the framework. Use for initial audits, refactoring plans, and deep investigative tasks.
-- **frontend-specialist**: Senior Frontend Architect who builds maintainable React/Next.js systems with performance-first mindset. Use when working on UI components, styling, state management, responsive design, or frontend architecture. Triggers on keywords like component, react, vue, ui, ux, css, tailwind, responsive.
-- **game-developer**: Game development across all platforms (PC, Web, Mobile, VR/AR). Use when building games with Unity, Godot, Unreal, Phaser, Three.js, or any game engine. Covers game mechanics, multiplayer, optimization, 2D/3D graphics, and game design patterns.
-- **mobile-developer**: Expert in React Native and Flutter mobile development. Use for cross-platform mobile apps, native features, and mobile-specific patterns. Triggers on mobile, react native, flutter, ios, android, app store, expo.
-- **orchestrator**: Multi-agent coordination and task orchestration. Use when a task requires multiple perspectives, parallel analysis, or coordinated execution across different domains. Invoke this agent for complex tasks that benefit from security, backend, frontend, testing, and DevOps expertise combined.
-- **penetration-tester**: Expert in offensive security, penetration testing, red team operations, and vulnerability exploitation. Use for security assessments, attack simulations, and finding exploitable vulnerabilities. Triggers on pentest, exploit, attack, hack, breach, pwn, redteam, offensive.
-- **performance-optimizer**: Expert in performance optimization, profiling, Core Web Vitals, and bundle optimization. Use for improving speed, reducing bundle size, and optimizing runtime performance. Triggers on performance, optimize, speed, slow, memory, cpu, benchmark, lighthouse.
-- **product-manager**: Expert in product requirements, user stories, and acceptance criteria. Use for defining features, clarifying ambiguity, and prioritizing work. Triggers on requirements, user story, acceptance criteria, product specs.
-- **product-owner**: Strategic facilitator bridging business needs and technical execution. Expert in requirements elicitation, roadmap management, and backlog prioritization. Triggers on requirements, user story, backlog, MVP, PRD, stakeholder.
-- **project-planner**: Smart project planning agent. Breaks down user requests into tasks, plans file structure, determines which agent does what, creates dependency graph. Use when starting new projects or planning major features.
-- **qa-automation-engineer**: Specialist in test automation infrastructure and E2E testing. Focuses on Playwright, Cypress, CI pipelines, and breaking the system. Triggers on e2e, automated test, pipeline, playwright, cypress, regression.
-- **security-auditor**: Elite cybersecurity expert. Think like an attacker, defend like an expert. OWASP 2025, supply chain security, zero trust architecture. Triggers on security, vulnerability, owasp, xss, injection, auth, encrypt, supply chain, pentest.
-- **seo-specialist**: SEO and GEO (Generative Engine Optimization) expert. Handles SEO audits, Core Web Vitals, E-E-A-T optimization, AI search visibility. Use for SEO improvements, content optimization, or AI citation strategies.
-- **test-engineer**: Expert in testing, TDD, and test automation. Use for writing tests, improving coverage, debugging test failures. Triggers on test, spec, coverage, jest, pytest, playwright, e2e, unit test.
-- **ui-ux-designer**: Expert in UI/UX principles, WCAG accessibility, Figma translation, typography, spacing, color theory, and micro-interactions. Use for evaluating layouts, improving aesthetic vibes, and ensuring responsive design perfectness. Triggers on ui, ux, design, layout, aesthetic, color, spacing, figma.
+## Instructions for AI
+
+You MUST NOT rely on an index file to discover Agent Personas. You are equipped with the **Auto-Discovery Engine**.
+
+**Protocol:**
+1. Determine the relevant keywords from the user request (e.g. `frontend-specialist`, `security-auditor`, `orchestrator`).
+2. Run a keyword search on the directory using `find` or `grep_search` against `.agent/agents/` to adopt a character.
+3. Notify the user indirectly that you have adopted the persona.

package/templates/.agent/SKILLS_INDEX.md

@@ -1,56 +1,14 @@
-# Master Skills Index
+# Auto-Discovery Routing Mechanism
 
-AI, whenever you are assigned a task, scan this list to find relevant skills. If a skill seems relevant to the task, read its full `SKILL.md` file located at `templates/.agent/skills/<skill-name>/SKILL.md` BEFORE coding.
+> [!WARNING]
+> STATIC INDEX OBSOLETE: We explicitly removed the hardcoded `SKILLS_INDEX.md` mapping file because maintaining an index for over 455 Elite Web & Mobile skills is technically impossible and computationally expensive for LLM Context Windows.
 
-- **api-patterns**: allowed-tools: Read, Write, Edit, Glob, Grep --- 
-- **app-builder**: allowed-tools: Read, Write, Edit, Glob, Grep, Bash, Agent --- 
-- **architecture**: allowed-tools: Read, Glob, Grep --- 
-- **bash-linux**: allowed-tools: Read, Write, Edit, Glob, Grep, Bash --- 
-- **behavioral-modes**: allowed-tools: Read, Glob, Grep --- 
-- **better-auth-patterns**:   Use when implementing authentication, authorization, session management,   login/register flows, Google OAuth, or protected routes. Triggers on 
-- **brainstorming**: allowed-tools: Read, Glob, Grep --- 
-- **bullmq-worker**:   Use when creating background jobs, queues, workers, or scheduling tasks.   Also use when connecting background job results to Socket.io realtime events 
-- **clean-code**: allowed-tools: Read, Write, Edit version: 2.0 
-- **code-review-checklist**: allowed-tools: Read, Glob, Grep --- 
-- **database-design**: allowed-tools: Read, Write, Edit, Glob, Grep --- 
-- **deployment-procedures**: allowed-tools: Read, Glob, Grep, Bash --- 
-- **documentation-templates**: allowed-tools: Read, Glob, Grep --- 
-- **drizzle-orm-patterns**:   Use when writing Drizzle ORM database code, migrations, or schema design. Very useful for Edge and Serverless database environments like Turso, Neon, or Cloudflare D1. Triggers on drizzle, schema, migration, orm, query, insert, select, postgres, sqlite. --- 
-- **feature-spec-writer**:   Use when planning a new feature before coding, creating a feature brief,   or writing acceptance criteria. Triggers on "plan this feature", "write a spec", 
-- **frontend-design**: allowed-tools: Read, Write, Edit, Glob, Grep, Bash --- 
-- **game-development**: allowed-tools: Read, Write, Edit, Glob, Grep, Bash --- 
-- **geo-fundamentals**: allowed-tools: Read, Glob, Grep --- 
-- **i18n-localization**: allowed-tools: Read, Glob, Grep --- 
-- **intelligent-routing**: version: 1.0.0 --- 
-- **lint-and-validate**: allowed-tools: Read, Glob, Grep, Bash --- 
-- **mcp-builder**: allowed-tools: Read, Write, Edit, Glob, Grep --- 
-- **mobile-design**: allowed-tools: Read, Glob, Grep, Bash --- 
-- **neo-storage**:   Use when uploading, downloading, deleting files, or generating presigned URLs   with NEO Object Storage (Biznet Gio). Triggers on "upload file", "object storage", 
-- **nextjs-api-route**:   Use when creating or modifying Next.js App Router API routes (route.ts files),   Server Actions, or Server Components that fetch data. Triggers on "api route", 
-- **nextjs-react-expert**: allowed-tools: Read, Write, Edit, Glob, Grep, Bash --- 
-- **nodejs-best-practices**: allowed-tools: Read, Write, Edit, Glob, Grep --- 
-- **parallel-agents**: allowed-tools: Read, Glob, Grep --- 
-- **performance-profiling**: allowed-tools: Read, Glob, Grep, Bash --- 
-- **plan-writing**: allowed-tools: Read, Glob, Grep --- 
-- **powershell-windows**: allowed-tools: Read, Write, Edit, Glob, Grep, Bash --- 
-- **prisma-7-patterns**:   Use when writing ANY Prisma database code, creating models, running queries,   setting up the Prisma client, or running migrations. Triggers on "prisma", 
-- **python-patterns**: allowed-tools: Read, Write, Edit, Glob, Grep --- 
-- **rag-vector-db**:   Use when building AI applications that require memory, semantic search, embeddings, document chat, or connecting an LLM to a private dataset (RAG). Triggers on rag, vector, embedding, pinecone, qdrant, pgvector, similarity search. --- 
-- **red-team-tactics**: allowed-tools: Read, Glob, Grep --- 
-- **rust-pro**:   features, and production-ready systems programming. Expert in the latest Rust   ecosystem including Tokio, axum, and cutting-edge crates. Use PROACTIVELY for 
-- **seo-fundamentals**: allowed-tools: Read, Glob, Grep --- 
-- **server-management**: allowed-tools: Read, Write, Edit, Glob, Grep, Bash --- 
-- **systematic-debugging**: allowed-tools: Read, Glob, Grep --- 
-- **tailwind-patterns**: allowed-tools: Read, Write, Edit, Glob, Grep --- 
-- **tdd-workflow**: allowed-tools: Read, Write, Edit, Glob, Grep, Bash --- 
-- **testing-patterns**: allowed-tools: Read, Write, Edit, Glob, Grep, Bash --- 
-- **uu-pdp-feature-check**:   Use when building any feature that collects, stores, displays, or processes   user personal data. Triggers on "user data", "personal info", "profile", 
-- **vibe-buildplan**:   Use after vibe-techdesign. Generates sprint plan and initial backlog from PRD.   Triggers on "buat sprint plan", "breakdown task", "berapa sprint", 
-- **vibe-prd**:   Use after vibe-research, or when starting to define product requirements.   Triggers on "buat PRD", "definisikan fitur", "apa yang harus dibangun", 
-- **vibe-research**:   Use at the START of a new project, before PRD or coding.   Triggers on "riset aplikasi ini", "research dulu", "validasi ide", 
-- **vibe-stitch-prompt**:   Use when the user wants to generate a UI design prompt for Google Stitch   based on the existing PRD and UI Guidelines. Triggers on "buat prompt stitch", 
-- **vibe-techdesign**:   Use after vibe-prd, or when deciding architecture and stack.   Triggers on "pilih stack", "desain arsitektur", "database apa yang cocok", 
-- **vulnerability-scanner**: allowed-tools: Read, Glob, Grep, Bash --- 
-- **web-design-guidelines**: metadata:   author: vercel 
-- **webapp-testing**: allowed-tools: Read, Write, Edit, Glob, Grep, Bash --- 
-- **xendit-integration**:   Use when working with Xendit payment integration: creating payment links,   handling webhooks, implementing split payment, or managing disbursements. 
+## Instructions for AI
+
+You MUST NOT rely on an index file to discover skills. You are equipped with the **Auto-Discovery Engine**.
+
+**Protocol:**
+1. Determine the relevant keywords from the user request (e.g. `seo`, `auth`, `aws`, `stripe`, `react`).
+2. Run a keyword search on the directory using `find` or `grep_search` against `.agent/skills/`.
+3. Pick the matched directory, read its `SKILL.md` silently, then fulfill the prompt using its expert context.
+4. Notify the user: `🤖 Auto-Discovery: Mengaktifkan skill @[skill-name]...`

package/templates/.agent/mcp_config.json

@@ -7,9 +7,9 @@
     "JANGAN commit file ini jika sudah ada credentials — tambahkan ke .gitignore"
   ],
   "_tiers": {
-    "tier1_wajib": ["context7", "github"],
+    "tier1_wajib": ["context7", "github", "brave-search", "sequential-thinking"],
     "tier2_sangat_berguna": ["postgresql", "playwright", "sentry", "docker"],
-    "tier3_opsional": ["firecrawl", "notion", "slack"]
+    "tier3_opsional": ["firecrawl", "figma", "google-stitch"]
   },
 
   "mcpServers": {
@@ -101,28 +101,45 @@
       }
     },
 
-    "notion": {
+    "brave-search": {
+      "_tier": "TIER 1 — WAJIB",
+      "_description": "Web scraping & pencarian dokumentasi realtime. Wajib untuk mengatasi halusinasi kode.",
+      "_usage": "AI akan otomatis menggunakannya bila menemukan library asing atau error syntax modern.",
+      "command": "npx",
+      "args": ["-y", "@modelcontextprotocol/server-brave-search"],
+      "env": {
+        "BRAVE_API_KEY": "[BRAVE_API_KEY — signup di brave.com/search/api]"
+      }
+    },
+
+    "sequential-thinking": {
+      "_tier": "TIER 1 — WAJIB",
+      "_description": "Sistem pengereman AI (Chain-of-Thought) agar AI tidak gegabah saat ditanya masalah rumit.",
+      "_usage": "Terpanggil otomatis di background saat AI disuruh merancang fitur atau debugging rumit.",
+      "command": "npx",
+      "args": ["-y", "@modelcontextprotocol/server-sequential-thinking"],
+      "env": {}
+    },
+
+    "figma": {
       "_tier": "TIER 3 — OPSIONAL",
-      "_description": "Akses Notion pages/databases dari IDE. Berguna jika PRD atau backlog di Notion.",
-      "_usage": "Contoh: 'Show current sprint tasks from Notion', 'Create a new task in backlog database'",
-      "_setup": "Buat Notion Integration di notion.so/my-integrations, share workspace ke integration",
+      "_description": "Baca file desain Figma langsung ke dalam IDE untuk diubah jadi UI code.",
+      "_usage": "Contoh: 'Buat komponen React berdasarkan desain Figma link_terlampir'.",
       "command": "npx",
-      "args": ["-y", "@notionhq/notion-mcp-server"],
+      "args": ["-y", "mcp-server-figma"],
       "env": {
-        "NOTION_API_KEY": "[NOTION_API_KEY — notion.so/my-integrations]"
+        "FIGMA_PERSONAL_ACCESS_TOKEN": "[FIGMA_PAT — figma.com/settings]"
       }
     },
 
-    "slack": {
+    "google-stitch": {
       "_tier": "TIER 3 — OPSIONAL",
-      "_description": "Search, read, dan kirim Slack messages dari IDE. Berguna untuk check diskusi tim tentang bug tertentu.",
-      "_usage": "Contoh: 'Search Slack for messages about payment bug', 'Post update to #dev channel'",
-      "_setup": "Buat Slack App di api.slack.com/apps dengan scope: channels:read, chat:write, search:read",
+      "_description": "Integrasi Google Stitch UI/UX. Ekstrak Design DNA (warna, fonts, tailwind) langsung ke code AI.",
+      "_usage": "Contoh: 'Tarik design context dari project Google Stitch dan buatkan form login'.",
       "command": "npx",
-      "args": ["-y", "@modelcontextprotocol/server-slack"],
+      "args": ["-y", "@_davideast/stitch-mcp"],
       "env": {
-        "SLACK_BOT_TOKEN": "[xoxb-... — api.slack.com/apps → OAuth & Permissions]",
-        "SLACK_TEAM_ID": "[T... — Slack workspace ID]"
+        "GOOGLE_CLOUD_PROJECT_ID": "[PROJECT_ID_GCP]"
       }
     }
   }

package/templates/.agent/rules/GEMINI.md

@@ -42,34 +42,33 @@ Agent activated → Check frontmatter "skills:" → Read SKILL.md (INDEX) → Re
 
 ---
 
-## 🤖 INTELLIGENT AGENT ROUTING (STEP 2 - AUTO)
+## 🤖 INTELLIGENT AGENT ROUTING & AUTO-DISCOVERY (STEP 2 - AUTO)
 
-**ALWAYS ACTIVE: Before responding to ANY request, automatically analyze and select the best agent(s).**
+**ALWAYS ACTIVE: Before responding to ANY request, automatically analyze and select the best skill(s) from the 1300+ available repository.**
 
-> 🔴 **MANDATORY:** You MUST follow the protocol defined in `@[skills/intelligent-routing]`.
+> 🔴 **MANDATORY:** You MUST follow the Auto-Discovery protocol defined in `@[skills/intelligent-routing]`.
 
-### Auto-Selection Protocol
-
-1. **Analyze (Silent)**: Detect domains (Frontend, Backend, Security, etc.) from user request.
-2. **Select Agent(s)**: Choose the most appropriate specialist(s).
-3. **Inform User**: Concisely state which expertise is being applied.
-4. **Apply**: Generate response using the selected agent's persona and rules.
+### Auto-Discovery Protocol (1300+ Skills)
+1. **Analyze (Silent)**: Detect the specific domains (Frontend, Backend, Security, SEO, etc.) from the user's request.
+2. **Search Directory**: Do NOT rely merely on memory. You MUST perform a keyword-based search in `.agent/skills/` (e.g. searching for `react`, `aws`, `seo`, `tailwind`) to discover matching skills.
+3. **Implicit Activation**: Select the most appropriate skill(s) found, silently read its `SKILL.md`, and apply it to fulfill the prompt.
+4. **Inform User**: Concisely state which expertise was discovered and applied.
 
 ### Response Format (MANDATORY)
 
-When auto-applying an agent, inform the user:
+When auto-applying an agent/skill, inform the user:
 
 ```markdown
-🤖 **Applying knowledge of `@[agent-name]`...**
+🤖 **Auto-Discovery: Mendeteksi dan mengaktifkan skill `@[nama-skill-yg-ditemukan]`...**
 
 [Continue with specialized response]
 ```
 
 **Rules:**
 
-1. **Silent Analysis**: No verbose meta-commentary ("I am analyzing...").
-2. **Respect Overrides**: If user mentions `@agent`, use it.
-3. **Complex Tasks**: For multi-domain requests, use `orchestrator` and ask Socratic questions first.
+1. **Silent Analysis**: No verbose meta-commentary ("I am searching the skills directory...").
+2. **Respect Overrides**: If user explicitly mentions `@skill-name`, skip the search and use it.
+3. **Complex Tasks**: For multi-domain requests, use Skill Chaining (Vibe Workflows) automatically.
 
 ### ⚠️ AGENT ROUTING CHECKLIST (MANDATORY BEFORE EVERY CODE/DESIGN RESPONSE)
 
@@ -77,19 +76,18 @@ When auto-applying an agent, inform the user:
 
 | Step | Check | If Unchecked |
 |------|-------|--------------|
-| 1 | Did I identify the correct agent for this domain? | → STOP. Analyze request domain first. |
-| 2 | Did I READ the agent's `.md` file (or recall its rules)? | → STOP. Open `.agent/agents/{agent}.md` |
-| 3 | Did I announce `🤖 Applying knowledge of @[agent]...`? | → STOP. Add announcement before response. |
-| 4 | Did I load required skills from agent's frontmatter? | → STOP. Check `skills:` field and read them. |
+| 1 | Did I automatically search the `.agent/skills` folder for relevant matches? | → STOP. Do a keyword search in `.agent/skills` first. |
+| 2 | Did I READ the discovered skill's `.md` file? | → STOP. Open `.agent/skills/{skill}/SKILL.md` |
+| 3 | Did I announce `🤖 Auto-Discovery: Mengaktifkan skill @[skill]...`? | → STOP. Add announcement before response. |
 
 **Failure Conditions:**
 
-- ❌ Writing code without identifying an agent = **PROTOCOL VIOLATION**
-- ❌ Skipping the announcement = **USER CANNOT VERIFY AGENT WAS USED**
+- ❌ Writing code without automatically discovering relevant skills = **PROTOCOL VIOLATION**
+- ❌ Skipping the announcement = **USER CANNOT VERIFY WHICH SKILL WAS USED**
 - ❌ Ignoring agent-specific rules (e.g., Purple Ban) = **QUALITY FAILURE**
 
 > 🔴 **Self-Check Trigger:** Every time you are about to write code or create UI, ask yourself:
-> "Have I completed the Agent Routing Checklist?" If NO → Complete it first.
+> "Have I checked if there are advanced skills for this in the 1300+ library?" If NO → Search it first.
 
 ---
 
@@ -145,6 +143,39 @@ When user's prompt is NOT in English:
 
 ---
 
+## 🎨 VIBE CODING MODE (NON-TECHNICAL USERS ENHANCEMENTS)
+
+**When fulfilling requests related to building or editing applications, you must act as a fully autonomous Tech Lead and Developer, minimizing the cognitive load on the user.**
+
+### 1. Skill Chaining (Automated Vibe Workflows)
+When the user asks to build a new feature or complex UI ("Bikinkan saya halaman dashboard"), **never jump straight to coding.**
+- You must sequentially chain predefined skills implicitly:
+  1. Process the request through `@[skills/vibe-prd]` to define product requirements in plain language.
+  2. Map the technical architecture quietly using `@[skills/vibe-techdesign]`.
+  3. Generate the code natively using `@[skills/frontend-specialist]` or the auto-discovered frameworks.
+
+### 2. Auto-Recovery & Self-Healing Protocol
+If your code generates an error, a stack traceback, or if a verification script fails (e.g., compiler error):
+- **NEVER present the raw error to the user and ask "How should I fix this?"**
+- You must **autonomously** invoke `@[skills/lint-and-validate]` and `@[skills/systematic-debugging]` to diagnose the issue.
+- Read logs, formulate a silent fix, apply it, and only inform the user when it succeeds. ("Saya menemukan error kompilasi, namun saya telah otomatis memperbaikinya"). You act; the user only watches.
+
+### 3. UI/UX Interactivity by Default (No Unstyled UI)
+Any frontend code generated MUST look polished, vibrant, and interactive immediately.
+- Auto-inject `@[skills/ui-ux-pro-max]`, `@[skills/frontend-design]`, and `@[skills/tailwind-design-system]` rules into every UI response.
+- Default to using dark/light modes, premium framer-motion/tailwind animations, smooth gradients, and modern aesthetics unless explicitly told otherwise.
+- Avoid generic placeholders. Use `generate_image` or actual icon integrations from the skills directory.
+
+### 4. Long-Term Memory Protocol (CRITICAL)
+In long Vibe Coding sessions, you will eventually lose early context (chosen colors, database schema, project rules) due to context window limits.
+- **You MUST actively maintain a state file at `.agent/MEMORY.md`.**
+- **Protocol:**
+  1. Check for `.agent/MEMORY.md`. If it doesn't exist, silently create it.
+  2. Every time a major architectural decision is made (e.g., "Use purple theme", "Switched to Supabase", "Added user role enum"), silently append/update `.agent/MEMORY.md`.
+  3. **Read `.agent/MEMORY.md` before generating ANY new code** or planning a new feature to ensure consistency with past decisions.
+
+---
+
 ## TIER 1: CODE RULES (When Writing Code)
 
 ### 📱 Project Type Routing