vibes-plug 2.5.0 → 2.14.1

package/skills/senior-fullstack/scripts/fullstack_scaffolder.py

@@ -1,114 +0,0 @@
-#!/usr/bin/env python3
-"""
-Fullstack Scaffolder
-Automated tool for senior fullstack tasks
-"""
-
-import os
-import sys
-import json
-import argparse
-from pathlib import Path
-from typing import Dict, List, Optional
-
-class FullstackScaffolder:
-    """Main class for fullstack scaffolder functionality"""
-    
-    def __init__(self, target_path: str, verbose: bool = False):
-        self.target_path = Path(target_path)
-        self.verbose = verbose
-        self.results = {}
-    
-    def run(self) -> Dict:
-        """Execute the main functionality"""
-        print(f"🚀 Running {self.__class__.__name__}...")
-        print(f"📁 Target: {self.target_path}")
-        
-        try:
-            self.validate_target()
-            self.analyze()
-            self.generate_report()
-            
-            print("✅ Completed successfully!")
-            return self.results
-            
-        except Exception as e:
-            print(f"❌ Error: {e}")
-            sys.exit(1)
-    
-    def validate_target(self):
-        """Validate the target path exists and is accessible"""
-        if not self.target_path.exists():
-            raise ValueError(f"Target path does not exist: {self.target_path}")
-        
-        if self.verbose:
-            print(f"✓ Target validated: {self.target_path}")
-    
-    def analyze(self):
-        """Perform the main analysis or operation"""
-        if self.verbose:
-            print("📊 Analyzing...")
-        
-        # Main logic here
-        self.results['status'] = 'success'
-        self.results['target'] = str(self.target_path)
-        self.results['findings'] = []
-        
-        # Add analysis results
-        if self.verbose:
-            print(f"✓ Analysis complete: {len(self.results.get('findings', []))} findings")
-    
-    def generate_report(self):
-        """Generate and display the report"""
-        print("\n" + "="*50)
-        print("REPORT")
-        print("="*50)
-        print(f"Target: {self.results.get('target')}")
-        print(f"Status: {self.results.get('status')}")
-        print(f"Findings: {len(self.results.get('findings', []))}")
-        print("="*50 + "\n")
-
-def main():
-    """Main entry point"""
-    parser = argparse.ArgumentParser(
-        description="Fullstack Scaffolder"
-    )
-    parser.add_argument(
-        'target',
-        help='Target path to analyze or process'
-    )
-    parser.add_argument(
-        '--verbose', '-v',
-        action='store_true',
-        help='Enable verbose output'
-    )
-    parser.add_argument(
-        '--json',
-        action='store_true',
-        help='Output results as JSON'
-    )
-    parser.add_argument(
-        '--output', '-o',
-        help='Output file path'
-    )
-    
-    args = parser.parse_args()
-    
-    tool = FullstackScaffolder(
-        args.target,
-        verbose=args.verbose
-    )
-    
-    results = tool.run()
-    
-    if args.json:
-        output = json.dumps(results, indent=2)
-        if args.output:
-            with open(args.output, 'w') as f:
-                f.write(output)
-            print(f"Results written to {args.output}")
-        else:
-            print(output)
-
-if __name__ == '__main__':
-    main()

package/skills/senior-fullstack/scripts/project_scaffolder.py

@@ -1,114 +0,0 @@
-#!/usr/bin/env python3
-"""
-Project Scaffolder
-Automated tool for senior fullstack tasks
-"""
-
-import os
-import sys
-import json
-import argparse
-from pathlib import Path
-from typing import Dict, List, Optional
-
-class ProjectScaffolder:
-    """Main class for project scaffolder functionality"""
-    
-    def __init__(self, target_path: str, verbose: bool = False):
-        self.target_path = Path(target_path)
-        self.verbose = verbose
-        self.results = {}
-    
-    def run(self) -> Dict:
-        """Execute the main functionality"""
-        print(f"🚀 Running {self.__class__.__name__}...")
-        print(f"📁 Target: {self.target_path}")
-        
-        try:
-            self.validate_target()
-            self.analyze()
-            self.generate_report()
-            
-            print("✅ Completed successfully!")
-            return self.results
-            
-        except Exception as e:
-            print(f"❌ Error: {e}")
-            sys.exit(1)
-    
-    def validate_target(self):
-        """Validate the target path exists and is accessible"""
-        if not self.target_path.exists():
-            raise ValueError(f"Target path does not exist: {self.target_path}")
-        
-        if self.verbose:
-            print(f"✓ Target validated: {self.target_path}")
-    
-    def analyze(self):
-        """Perform the main analysis or operation"""
-        if self.verbose:
-            print("📊 Analyzing...")
-        
-        # Main logic here
-        self.results['status'] = 'success'
-        self.results['target'] = str(self.target_path)
-        self.results['findings'] = []
-        
-        # Add analysis results
-        if self.verbose:
-            print(f"✓ Analysis complete: {len(self.results.get('findings', []))} findings")
-    
-    def generate_report(self):
-        """Generate and display the report"""
-        print("\n" + "="*50)
-        print("REPORT")
-        print("="*50)
-        print(f"Target: {self.results.get('target')}")
-        print(f"Status: {self.results.get('status')}")
-        print(f"Findings: {len(self.results.get('findings', []))}")
-        print("="*50 + "\n")
-
-def main():
-    """Main entry point"""
-    parser = argparse.ArgumentParser(
-        description="Project Scaffolder"
-    )
-    parser.add_argument(
-        'target',
-        help='Target path to analyze or process'
-    )
-    parser.add_argument(
-        '--verbose', '-v',
-        action='store_true',
-        help='Enable verbose output'
-    )
-    parser.add_argument(
-        '--json',
-        action='store_true',
-        help='Output results as JSON'
-    )
-    parser.add_argument(
-        '--output', '-o',
-        help='Output file path'
-    )
-    
-    args = parser.parse_args()
-    
-    tool = ProjectScaffolder(
-        args.target,
-        verbose=args.verbose
-    )
-    
-    results = tool.run()
-    
-    if args.json:
-        output = json.dumps(results, indent=2)
-        if args.output:
-            with open(args.output, 'w') as f:
-                f.write(output)
-            print(f"Results written to {args.output}")
-        else:
-            print(output)
-
-if __name__ == '__main__':
-    main()

package/skills/seo-aeo-landing-page-writer/SKILL.md

@@ -1,97 +0,0 @@
----
-name: seo-aeo-landing-page-writer
-description: "Writes complete, structured landing pages optimized for SEO ranking, AEO citation, and visitor conversion / Penulis landing page terstruktur untuk peringkat SEO, sitasi AEO, dan konversi."
-author: "Roedy Rustam"
----
-
-# SEO-AEO Landing Page Writer
-
-[English](#english) | [Bahasa Indonesia](#bahasa-indonesia)
-
----
-
-<a name="english"></a>
-## English
-
-### Overview
-Generates a full, publish-ready landing page following a defined section order with SEO heading structure, AEO extraction blocks, FAQ section, comparison table, social proof, and conversion-focused CTAs. Every section serves a specific purpose in a narrative arc that moves the visitor from awareness to action.
-
-### Trigger Conditions
-Use this skill when:
-- Building a landing page for a new product or service.
-- An existing landing page needs a full SEO and AEO rewrite.
-- You need a page that can be cited by AI engines like Perplexity or ChatGPT.
-- You want conversion copy that leads with pain before pitching the product.
-
-### How It Works (Step-by-Step)
-1. **Map Inputs**: Extract product name, audience, primary keyword, pain points, features, benefits, USPs, social proof, and CTAs.
-2. **Write AEO Extraction Sentence**: Write one 25–40 word sentence that answers "What is [product]?" — standalone, no jargon, placed in a blockquote immediately after the H1. This is the sentence AI engines extract.
-3. **Follow the Narrative Arc**: Write sections in this exact order:
-   - Hero — H1 + AEO sentence + CTA
-   - Problem — Audience pain, no product mention yet
-   - Solution — Introduce product as the answer
-   - Features as Benefits — Table format
-   - Social Proof — Testimonials, logos, stats
-   - Mid-page CTA
-   - How It Works — Numbered steps
-   - Comparison — Table with honest competitor comparison
-   - FAQ — Minimum 6 entries, each under 50 words
-   - Trust Signals
-   - Final CTA
-
-### Best Practices & Pitfalls
-- **Empathy First**: Write the problem section before mentioning the product — empathy first.
-- **AEO Block**: Place the AEO extraction sentence in a blockquote immediately after H1.
-- **FAQ Limits**: Every FAQ answer must be under 50 words and self-contained.
-- **Tone**: Do not use "revolutionary", "game-changing", or "best-in-class".
-- **CTA**: Do not use "Submit" or "Click Here" as CTA button text.
-
-### Layout & UI Aesthetic (Monday.com Inspired)
-- Design the landing page with a modern, spacious aesthetic (see `monday-design-aesthetic` skill).
-- Use generous vertical padding (80-120px) between narrative sections.
-- Display features as benefits using large, rounded cards (12-16px radius) with subtle drop shadows.
-- Keep the background clean white or light gray, using a vibrant brand color for CTA buttons.
-
-
----
-
-<a name="bahasa-indonesia"></a>
-## Bahasa Indonesia
-
-### Ringkasan
-Menghasilkan landing page lengkap yang siap dipublikasikan dengan struktur heading SEO, blok ekstraksi AEO, bagian FAQ, tabel perbandingan, bukti sosial (social proof), dan CTA yang berfokus pada konversi. Setiap bagian dirancang untuk memandu pengunjung dari pemahaman masalah menuju tindakan (pembelian/registrasi).
-
-### Kondisi Pemicu
-Gunakan skill ini ketika:
-- Membangun landing page untuk produk atau layanan baru.
-- Menulis ulang landing page yang ada untuk optimasi SEO dan AEO.
-- Memerlukan halaman yang dapat dengan mudah dikutip oleh mesin pencari AI (seperti Perplexity atau ChatGPT).
-- Membuat salinan konversi (conversion copy) yang menyoroti masalah pengguna sebelum memperkenalkan solusi.
-
-### Cara Kerja (Langkah demi Langkah)
-1. **Pemetaan Input**: Ekstrak nama produk, target audiens, kata kunci utama, keluhan utama pengguna, fitur, manfaat, USP, bukti sosial, dan CTA.
-2. **Tulis Kalimat Ekstraksi AEO**: Buat satu kalimat ringkas berisi 25–40 kata yang menjawab "Apa itu [produk]?" tanpa jargon, dan letakkan di dalam blockquote tepat setelah tag H1. Kalimat ini yang akan diekstraksi oleh mesin pencari AI.
-3. **Ikuti Alur Narasi**: Tulis bagian dalam urutan persis seperti berikut:
-   - Hero — H1 + Kalimat AEO + CTA
-   - Problem — Keluhan utama audiens (tanpa menyebutkan produk terlebih dahulu)
-   - Solution — Memperkenalkan produk sebagai jawaban masalah
-   - Features as Benefits — Tabel fitur dan manfaat
-   - Social Proof — Testimoni, logo klien, statistik
-   - Mid-page CTA — CTA tengah halaman
-   - How It Works — Langkah bernomor
-   - Comparison — Tabel perbandingan jujur dengan kompetitor
-   - FAQ — Minimal 6 entri, masing-masing di bawah 50 kata
-   - Trust Signals — Sinyal kepercayaan (garansi, enkripsi, dll.)
-   - Final CTA — CTA penutup
-
-### Praktik Terbaik & Hal yang Harus Dihindari
-- **Empati Utama**: Tulis bagian masalah terlebih dahulu sebelum menyebutkan produk untuk membangun empati.
-- **Batasan FAQ**: Setiap jawaban FAQ harus di bawah 50 kata, mandiri, dan mudah dipahami tanpa konteks eksternal.
-- **Bahasa Jujur**: Hindari kata-kata berlebihan seperti "revolutionary", "game-changing", or "best-in-class".
-- **CTA Spesifik**: Jangan gunakan teks tombol standar seperti "Submit" atau "Click Here". Gunakan teks berorientasi tindakan (misal: "Mulai Uji Coba Gratis").
-
-### Tata Letak & Estetika UI (Inspirasi Monday.com)
-- Desain landing page dengan estetika modern dan lapang (lihat skill `monday-design-aesthetic`).
-- Gunakan padding vertikal yang lega (80-120px) di antara setiap bagian narasi.
-- Tampilkan fitur sebagai manfaat (features as benefits) menggunakan kartu bersudut melengkung besar (radius 12-16px) dengan efek bayangan halus.
-- Jaga latar belakang tetap putih bersih atau abu-abu terang, menggunakan warna merek yang cerah untuk tombol CTA.

package/skills/seo-geo/SKILL.md

@@ -1,188 +0,0 @@
----
-name: seo-geo
-description: "Generative Engine Optimization (GEO) for AI Overviews, ChatGPT, and Perplexity / Optimasi Mesin Pencari Generatif (GEO) untuk AI Overviews, ChatGPT, dan Perplexity."
-author: "Roedy Rustam"
----
-
-# SEO-GEO Expert (2026 — AI Mode Edition)
-
-[English](#english) | [Bahasa Indonesia](#bahasa-indonesia)
-
----
-
-<a name="english"></a>
-## English
-
-### Description
-Generative Engine Optimization (GEO) for the 2026 AI-powered search landscape — Google AI Mode (successor to AI Overviews), ChatGPT Search, Perplexity Pages, Claude.ai web search, and Grok search. Optimizes content to be cited, quoted, and recommended by AI search engines.
-
-### Trigger Conditions
-- Optimizing content to appear in Google AI Mode responses.
-- Getting cited in ChatGPT Search, Perplexity, Claude web, or Grok results.
-- Adding `/llms.txt` and structured data for AI indexing.
-- Measuring GEO performance (citation rate, AI snippet appearances).
-- Optimizing for "Answer Engine" queries (who, what, how, why questions).
-
-### The 2026 AI Search Landscape
-
-| AI Engine | Source | Citable Content | Key Signal |
-|---|---|---|---|
-| **Google AI Mode** | Google index + Gemini | Yes — with source links | E-E-A-T, structured data |
-| **ChatGPT Search** | Bing index + GPT-4o | Yes — with citations | Bing ranking, freshness |
-| **Perplexity** | Real-time web crawl | Yes — prominent citations | Authority, specificity |
-| **Perplexity Pages** | User-generated long-form | Yes — auto-cited | Depth, comprehensiveness |
-| **Claude Web** | Real-time search | Yes — with URLs | Clarity, structure |
-| **Grok** | X/Twitter + web | Yes | Real-time trending |
-
-### GEO Optimization Framework
-
-#### 1. E-E-A-T Signals (Experience, Expertise, Authoritativeness, Trust)
-Google AI Mode heavily weights E-E-A-T:
-- **Author credentials**: Add `<script type="application/ld+json">` `Person` schema with credentials.
-- **Publication dates**: Always include `datePublished` and `dateModified`.
-- **Primary sources**: Cite original research, government data, and peer-reviewed studies.
-- **About page**: Clear author bios with LinkedIn/professional links.
-
-#### 2. `/llms.txt` — AI Indexing Protocol
-Add an `/llms.txt` file at your domain root — the 2026 standard for telling AI crawlers what to index:
-```
-# /llms.txt
-# AI-friendly site map for LLM indexers
-
-## Product
-- [Features](/features): Complete feature list with pricing
-- [API Docs](/docs/api): REST API reference (JSON schemas included)
-- [Changelog](/changelog): Recent updates and releases
-
-## Content
-- [Blog](/blog): Technical articles on [topic]
-- [Tutorials](/tutorials): Step-by-step guides
-
-## Company
-- [About](/about): Team, mission, and founding story
-- [Pricing](/pricing): Current plan structure
-```
-
-#### 3. Structured Data for AI Comprehension
-```html
-<!-- FAQ Schema — AI engines love Q&A format -->
-<script type="application/ld+json">
-{
-  "@context": "https://schema.org",
-  "@type": "FAQPage",
-  "mainEntity": [{
-    "@type": "Question",
-    "name": "What is [Product]?",
-    "acceptedAnswer": {
-      "@type": "Answer",
-      "text": "Concise, factual answer in 2-3 sentences that AI can quote directly."
-    }
-  }]
-}
-</script>
-
-<!-- HowTo Schema — for instructional content -->
-<script type="application/ld+json">
-{
-  "@context": "https://schema.org",
-  "@type": "HowTo",
-  "name": "How to [Task]",
-  "step": [
-    { "@type": "HowToStep", "name": "Step 1", "text": "..." },
-    { "@type": "HowToStep", "name": "Step 2", "text": "..." }
-  ]
-}
-</script>
-```
-
-#### 4. Content Formatting for AI Citation
-AI engines prefer content that is:
-- **Scannable**: Short paragraphs, headers for each concept, bullet lists.
-- **Definitive**: Declarative statements ("X is Y") over hedging ("X might be Y").
-- **Self-contained**: Each section can stand alone as a quotable snippet.
-- **Cited**: Reference authoritative sources with links.
-- **Fresh**: Updated within the last 6 months — AI engines penalize stale content.
-
-#### 5. Perplexity Pages Optimization
-Perplexity Pages are AI-generated long-form content that cites sources. To be cited in Pages:
-- Cover a topic comprehensively (> 1500 words).
-- Use clear section headers (H2/H3 for each subtopic).
-- Include statistics, data, and specific numbers.
-- Have a clear "Summary" or "TL;DR" section at the top.
-
-#### 6. ChatGPT Search Optimization
-ChatGPT Search is powered by Bing — standard Bing SEO applies, plus:
-- Ensure Bing Webmaster Tools verified and sitemap submitted.
-- OpenGraph tags properly set (`og:title`, `og:description`, `og:image`).
-- Content freshness signals (update dates, news sitemaps).
-
-#### 7. GEO Performance Measurement
-```python
-# Automated GEO tracking
-import httpx
-
-async def check_ai_citation(brand: str, queries: list[str]):
-    for query in queries:
-        # Check Perplexity
-        perp_result = await query_perplexity(query)
-        cited = brand.lower() in perp_result.lower()
-        
-        # Log citation rate per query
-        await log_metric("geo_citation", {
-            "engine": "perplexity",
-            "query": query,
-            "cited": cited,
-        })
-```
-
----
-
-<a name="bahasa-indonesia"></a>
-## Bahasa Indonesia
-
-### Deskripsi
-Generative Engine Optimization (GEO) untuk lanskap pencarian bertenaga AI tahun 2026 — Google AI Mode (penerus AI Overviews), ChatGPT Search, Perplexity Pages, pencarian web Claude.ai, dan pencarian Grok. Mengoptimalkan konten agar dikutip, disebut, dan direkomendasikan oleh mesin pencari AI.
-
-### Kondisi Pemicu
-- Mengoptimalkan konten agar muncul dalam respons Google AI Mode.
-- Mendapatkan kutipan di ChatGPT Search, Perplexity, Claude web, atau hasil Grok.
-- Menambahkan `/llms.txt` dan data terstruktur untuk pengindeksan AI.
-- Mengukur performa GEO (tingkat kutipan, kemunculan AI snippet).
-- Mengoptimalkan untuk kueri "Answer Engine" (pertanyaan siapa, apa, bagaimana, mengapa).
-
-### Lanskap Pencarian AI 2026
-
-| Mesin AI | Sumber | Konten yang Dapat Dikutip | Sinyal Kunci |
-|---|---|---|---|
-| **Google AI Mode** | Indeks Google + Gemini | Ya — dengan tautan sumber | E-E-A-T, data terstruktur |
-| **ChatGPT Search** | Indeks Bing + GPT-4o | Ya — dengan kutipan | Peringkat Bing, kesegaran |
-| **Perplexity** | Crawl web real-time | Ya — kutipan menonjol | Otoritas, spesifisitas |
-| **Perplexity Pages** | Konten panjang yang dibuat AI | Ya — dikutip otomatis | Kedalaman, komprehensivitas |
-| **Claude Web** | Pencarian real-time | Ya — dengan URL | Kejelasan, struktur |
-
-### Kerangka Optimasi GEO
-
-#### 1. Sinyal E-E-A-T
-Google AI Mode sangat mempertimbangkan E-E-A-T: kredensial penulis (schema `Person`), tanggal publikasi, kutipan dari sumber primer, dan halaman About yang jelas.
-
-#### 2. `/llms.txt` — Protokol Pengindeksan AI
-Tambahkan file `/llms.txt` di root domain Anda — standar 2026 untuk memberi tahu crawler AI apa yang harus diindeks. Mirip `robots.txt` tetapi untuk LLM.
-
-#### 3. Data Terstruktur untuk Pemahaman AI
-Gunakan schema `FAQPage` untuk konten Q&A dan `HowTo` untuk konten instruksional — format yang paling disukai mesin AI untuk dikutip.
-
-#### 4. Format Konten untuk Kutipan AI
-- Paragraf pendek, header untuk setiap konsep, daftar poin.
-- Pernyataan definitif ("X adalah Y") bukan hedging ("X mungkin Y").
-- Setiap seksi dapat berdiri sendiri sebagai snippet yang dapat dikutip.
-- Sertakan statistik, data, dan angka spesifik.
-- Diperbarui dalam 6 bulan terakhir.
-
-#### 5. Optimasi Perplexity Pages
-Tulis konten yang komprehensif (> 1500 kata), gunakan header seksi yang jelas, sertakan statistik dan angka spesifik, dan sertakan ringkasan "TL;DR" di bagian atas.
-
-#### 6. Optimasi ChatGPT Search
-ChatGPT Search didukung oleh Bing — SEO Bing standar berlaku. Verifikasi di Bing Webmaster Tools, submit sitemap, dan pastikan tag OpenGraph diatur dengan benar.
-
-#### 7. Pengukuran Performa GEO
-Lacak tingkat kutipan merek Anda per mesin AI per query secara otomatis untuk memantau visibilitas AI dari waktu ke waktu.

package/skills/session-context-loader/SKILL.md

@@ -1,77 +0,0 @@
----
-name: session-context-loader
-description: "Automatically loads and learns project context (Tech Stack, PRD, Roadmap, Blueprint) at the start of every new conversation session to ensure focused and directed development / Otomatis memuat dan mempelajari konteks proyek (Tech Stack, PRD, Roadmap, Blueprint) di awal setiap sesi percakapan baru untuk memastikan pengembangan yang terarah dan fokus."
-author: "Roedy Rustam"
----
-
-# Session Context Loader
-
-[English](#english) | [Bahasa Indonesia](#bahasa-indonesia)
-
----
-
-<a name="english"></a>
-## English
-
-### Description
-This skill ensures that the AI agent is always aligned with the project's core documentation. At the beginning of every new conversation session, it automatically searches for and reads essential project context files (Tech Stack, PRD, Roadmap, Blueprint). This guarantees that development remains focused, directed, and strictly adheres to established requirements and architectural decisions.
-
-### Trigger Conditions
-Activate this skill IMMEDIATELY when:
-- It is the very first message of a new conversation session.
-- The user says "start session", "initialize project", or "load context".
-- The AI realizes it lacks the high-level context of the current repository.
-
-### Execution Protocol
-
-When triggered, you MUST perform the following steps before answering the user's primary request or writing any code:
-
-1. **Locate Key Documentation Files:**
-   Use your file search tools (`list_dir`, `grep_search`, or `view_file`) to look for the following files in the project root or `.docs/` folder:
-   - `PRD.md` (Product Requirements Document)
-   - `ROADMAP.md` or `ROADMAP.txt`
-   - `BLUEPRINT.md` or `ARCHITECTURE.md`
-   - `TECH_STACK.md`, `package.json`, `go.mod`, `Cargo.toml`, or `requirements.txt` (to identify the tech stack)
-
-2. **Read and Internalize Context:**
-   - Read the contents of the found files.
-   - Understand the project's primary goal, current phase in the roadmap, architectural constraints (blueprint), and the specific tech stack being used.
-
-3. **Acknowledge and Align:**
-   - Briefly acknowledge to the user that the project context has been loaded successfully.
-   - State the current Tech Stack and the immediate goal based on the Roadmap/PRD.
-   - Proceed with addressing the user's actual request using the newly loaded context.
-
----
-
-<a name="bahasa-indonesia"></a>
-## Bahasa Indonesia
-
-### Deskripsi
-Skill ini memastikan bahwa agen AI selalu selaras dengan dokumentasi inti proyek. Di awal setiap sesi percakapan baru, agen akan secara otomatis mencari dan membaca file konteks proyek esensial (Tech Stack, PRD, Roadmap, Blueprint). Ini menjamin bahwa pengembangan proyek aplikasi tetap lebih terarah, fokus, dan sangat mematuhi persyaratan serta keputusan arsitektur yang telah ditetapkan.
-
-### Kondisi Pemicu
-Aktifkan skill ini SEGERA ketika:
-- Ini adalah pesan pertama dari sesi percakapan baru.
-- Pengguna berkata "mulai sesi", "inisialisasi proyek", atau "muat konteks".
-- AI menyadari bahwa ia kekurangan konteks tingkat tinggi dari repositori saat ini.
-
-### Protokol Eksekusi
-
-Saat dipicu, Anda HARUS melakukan langkah-langkah berikut sebelum menjawab permintaan utama pengguna atau menulis kode apa pun:
-
-1. **Temukan File Dokumentasi Kunci:**
-   Gunakan alat pencarian file Anda (`list_dir`, `grep_search`, atau `view_file`) untuk mencari file berikut di root proyek atau folder `.docs/`:
-   - `PRD.md` (Product Requirements Document)
-   - `ROADMAP.md` atau `ROADMAP.txt`
-   - `BLUEPRINT.md` atau `ARCHITECTURE.md`
-   - `TECH_STACK.md`, `package.json`, `go.mod`, `Cargo.toml`, atau `requirements.txt` (untuk mengidentifikasi tech stack)
-
-2. **Baca dan Pahami Konteks:**
-   - Baca isi dari file-file yang ditemukan.
-   - Pahami tujuan utama proyek, fase saat ini di roadmap, batasan arsitektur (blueprint), dan tech stack spesifik yang digunakan.
-
-3. **Konfirmasi dan Selaraskan:**
-   - Berikan konfirmasi singkat kepada pengguna bahwa konteks proyek telah berhasil dimuat.
-   - Sebutkan Tech Stack saat ini dan tujuan langsung berdasarkan Roadmap/PRD.
-   - Lanjutkan dengan menjawab permintaan pengguna yang sebenarnya menggunakan konteks yang baru dimuat.