vibes-plug 2.11.0 → 2.14.1

package/skills/saas-transformer/references/billing_integration_guide.md

@@ -1,401 +0,0 @@
-# Billing & Payment Gateway Integration Guide
-
-A comprehensive guide to setting up subscription billing, payment gateways, and Merchant of Record (MoR) systems. This guide covers Stripe, Midtrans, PayPal, Paddle, and FastSpring, detailing database structures and webhook verification in a multi-tenant SaaS application.
-
----
-
-## 1. Gateway Type: Payment Gateway vs. Merchant of Record (MoR)
-
-Before choosing a billing system, it is vital to understand the two main categories of billing platforms:
-
-| Feature | Payment Gateway (Stripe, Midtrans, PayPal) | Merchant of Record (Paddle, FastSpring) |
-|---|---|---|
-| **Definition** | Processes payments but places legal/financial responsibilities on you. | Acts as the reseller of your software; handles transactions and compliance. |
-| **Sales Tax / VAT** | You must calculate, collect, and file taxes globally (using tools like Stripe Tax). | Automatically handles global taxes, compliance, and invoicing. |
-| **Chargeback Liability**| You manage chargeback disputes directly. | The MoR platform handles chargeback disputes. |
-| **Integration Complexity**| Highly customizable APIs, but requires more backend logic for compliance. | Simple to configure; checkout UI is managed by the MoR. |
-
----
-
-## 2. Generic Multi-Gateway Database Schema
-
-To support multiple payment gateways, use a generic subscription schema.
-
-### Prisma Schema (`prisma/schema.prisma`)
-```prisma
-model Subscription {
-  id                 String   @id @default(cuid())
-  workspaceId        String   @unique
-  workspace          Workspace @relation(fields: [workspaceId], references: [id], onDelete: Cascade)
-  gateway            String   // "stripe", "midtrans", "paypal", "paddle", "fastspring"
-  gatewayCustomerId  String?  @unique
-  gatewaySubscriptionId String? @unique
-  gatewayPriceId     String?
-  status             String   // "active", "trialing", "past_due", "canceled", "unpaid"
-  currentPeriodEnd   DateTime
-  cancelAtPeriodEnd  Boolean  @default(false)
-  createdAt          DateTime @default(now())
-  updatedAt          DateTime @updatedAt
-}
-```
-
-### Drizzle ORM Schema (`lib/db/schema.ts`)
-```typescript
-import { pgTable, text, timestamp, boolean } from 'drizzle-orm/pg-core';
-
-export const subscriptions = pgTable('subscriptions', {
-  id: text('id').primaryKey(),
-  workspaceId: text('workspace_id').notNull().unique(),
-  gateway: text('gateway').notNull(), // "stripe", "midtrans", "paypal", "paddle", "fastspring"
-  gatewayCustomerId: text('gateway_customer_id').unique(),
-  gatewaySubscriptionId: text('gateway_subscription_id').unique(),
-  gatewayPriceId: text('gateway_price_id'),
-  status: text('status').notNull(),
-  currentPeriodEnd: timestamp('current_period_end').notNull(),
-  cancelAtPeriodEnd: boolean('cancel_at_period_end').default(false).notNull(),
-  createdAt: timestamp('created_at').defaultNow().notNull(),
-  updatedAt: timestamp('updated_at').defaultNow().notNull(),
-});
-```
-
----
-
-## 3. Webhook Implementations
-
-Webhooks are crucial to keep your SaaS database in sync with payment updates. Below are the implementation templates for Next.js 15 (App Router).
-
-### A. Stripe Integration
-Processes subscriptions and invoices. Verified via the Stripe SDK.
-
-```typescript
-import { NextResponse } from 'next/server';
-import Stripe from 'stripe';
-import { db } from '@/lib/db';
-import { subscriptions } from '@/lib/db/schema';
-import { eq } from 'drizzle-orm';
-
-const stripe = new Stripe(process.env.STRIPE_SECRET_KEY!, { apiVersion: '2025-01-01' as any });
-
-export async function POST(req: Request) {
-  const body = await req.text();
-  const signature = req.headers.get('Stripe-Signature')!;
-
-  let event: Stripe.Event;
-  try {
-    event = stripe.webhooks.constructEvent(body, signature, process.env.STRIPE_WEBHOOK_SECRET!);
-  } catch (err: any) {
-    return NextResponse.json({ error: `Signature verification failed: ${err.message}` }, { status: 400 });
-  }
-
-  switch (event.type) {
-    case 'checkout.session.completed': {
-      const session = event.data.object as Stripe.Checkout.Session;
-      const workspaceId = session.metadata?.workspaceId;
-      if (!workspaceId) break;
-
-      const subscription = await stripe.subscriptions.retrieve(session.subscription as string);
-      await db.insert(subscriptions).values({
-        id: subscription.id,
-        workspaceId,
-        gateway: 'stripe',
-        gatewayCustomerId: session.customer as string,
-        gatewaySubscriptionId: subscription.id,
-        gatewayPriceId: subscription.items.data[0].price.id,
-        status: subscription.status,
-        currentPeriodEnd: new Date(subscription.current_period_end * 1000),
-      });
-      break;
-    }
-    case 'invoice.payment_succeeded': {
-      const invoice = event.data.object as Stripe.Invoice;
-      if (!invoice.subscription) break;
-      const subscription = await stripe.subscriptions.retrieve(invoice.subscription as string);
-      await db.update(subscriptions)
-        .set({
-          status: subscription.status,
-          currentPeriodEnd: new Date(subscription.current_period_end * 1000),
-        })
-        .where(eq(subscriptions.gatewaySubscriptionId, subscription.id));
-      break;
-    }
-    case 'customer.subscription.deleted': {
-      const subscription = event.data.object as Stripe.Subscription;
-      await db.update(subscriptions)
-        .set({ status: 'canceled' })
-        .where(eq(subscriptions.gatewaySubscriptionId, subscription.id));
-      break;
-    }
-  }
-  return NextResponse.json({ received: true });
-}
-```
-
-### B. Midtrans Integration
-Southeast Asia's popular payment gateway. Verified via SHA512 signature key matching.
-
-```typescript
-import { NextResponse } from 'next/server';
-import crypto from 'crypto';
-import { db } from '@/lib/db';
-import { subscriptions } from '@/lib/db/schema';
-import { eq } from 'drizzle-orm';
-
-export async function POST(req: Request) {
-  const body = await req.json();
-  const { order_id, status_code, gross_amount, signature_key, transaction_status, fraud_status } = body;
-
-  // Verify signature key: sha512(order_id + status_code + gross_amount + server_key)
-  const serverKey = process.env.MIDTRANS_SERVER_KEY!;
-  const hashed = crypto
-    .createHash('sha512')
-    .update(order_id + status_code + gross_amount + serverKey)
-    .digest('hex');
-
-  if (hashed !== signature_key) {
-    return NextResponse.json({ error: 'Invalid Midtrans signature' }, { status: 400 });
-  }
-
-  // Update subscription/payment state based on transaction_status
-  if (transaction_status === 'capture' || transaction_status === 'settlement') {
-    if (fraud_status === 'challenge') {
-      await db.update(subscriptions).set({ status: 'unpaid' }).where(eq(subscriptions.id, order_id));
-    } else {
-      await db.update(subscriptions)
-        .set({ status: 'active', currentPeriodEnd: new Date(Date.now() + 30 * 24 * 60 * 60 * 1000) })
-        .where(eq(subscriptions.id, order_id));
-    }
-  } else if (['cancel', 'deny', 'expire'].includes(transaction_status)) {
-    await db.update(subscriptions).set({ status: 'canceled' }).where(eq(subscriptions.id, order_id));
-  } else if (transaction_status === 'pending') {
-    await db.update(subscriptions).set({ status: 'unpaid' }).where(eq(subscriptions.id, order_id));
-  }
-
-  return NextResponse.json({ success: true });
-}
-```
-
-### C. PayPal Integration
-Global subscription billing. Verified via PayPal API request validation.
-
-```typescript
-import { NextResponse } from 'next/server';
-import { db } from '@/lib/db';
-import { subscriptions } from '@/lib/db/schema';
-import { eq } from 'drizzle-orm';
-
-async function verifyPayPalSignature(headers: Headers, rawBody: string, webhookId: string) {
-  // Call PayPal API to verify signature authenticity
-  const endpoint = process.env.PAYPAL_MODE === 'live' 
-    ? 'https://api-m.paypal.com' 
-    : 'https://api-m.sandbox.paypal.com';
-
-  const authHeader = headers.get('authorization');
-  if (!authHeader) return false;
-
-  const response = await fetch(`${endpoint}/v1/notifications/verify-webhook-signature`, {
-    method: 'POST',
-    headers: {
-      'Content-Type': 'application/json',
-      'Authorization': authHeader,
-    },
-    body: JSON.stringify({
-      auth_algo: headers.get('paypal-auth-algo'),
-      cert_url: headers.get('paypal-cert-url'),
-      transmission_id: headers.get('paypal-transmission-id'),
-      transmission_sig: headers.get('paypal-transmission-sig'),
-      transmission_time: headers.get('paypal-transmission-time'),
-      webhook_id: webhookId,
-      webhook_event: JSON.parse(rawBody),
-    }),
-  });
-
-  const verification = await response.json();
-  return verification.verification_status === 'SUCCESS';
-}
-
-export async function POST(req: Request) {
-  const rawBody = await req.text();
-  const webhookId = process.env.PAYPAL_WEBHOOK_ID!;
-
-  const isValid = await verifyPayPalSignature(req.headers, rawBody, webhookId);
-  if (!isValid) {
-    return NextResponse.json({ error: 'PayPal signature invalid' }, { status: 400 });
-  }
-
-  const event = JSON.parse(rawBody);
-
-  switch (event.event_type) {
-    case 'BILLING.SUBSCRIPTION.CREATED': {
-      const sub = event.resource;
-      const workspaceId = sub.custom_id; // Pass workspace ID in custom_id
-      if (!workspaceId) break;
-
-      await db.insert(subscriptions).values({
-        id: sub.id,
-        workspaceId,
-        gateway: 'paypal',
-        gatewayCustomerId: sub.subscriber.payer_id,
-        gatewaySubscriptionId: sub.id,
-        gatewayPriceId: sub.plan_id,
-        status: 'active',
-        currentPeriodEnd: new Date(sub.billing_info.next_billing_time),
-      });
-      break;
-    }
-    case 'BILLING.SUBSCRIPTION.CANCELLED': {
-      const sub = event.resource;
-      await db.update(subscriptions)
-        .set({ status: 'canceled' })
-        .where(eq(subscriptions.gatewaySubscriptionId, sub.id));
-      break;
-    }
-  }
-
-  return NextResponse.json({ received: true });
-}
-```
-
-### D. Paddle Integration (Paddle Billing v2)
-Merchant of Record. Verified locally using an HMAC-SHA256 signature key verification.
-
-```typescript
-import { NextResponse } from 'next/server';
-import crypto from 'crypto';
-import { db } from '@/lib/db';
-import { subscriptions } from '@/lib/db/schema';
-import { eq } from 'drizzle-orm';
-
-function verifyPaddleSignature(body: string, signatureHeader: string, secret: string): boolean {
-  const parts = signatureHeader.split(';');
-  const tsPart = parts.find(p => p.startsWith('ts='));
-  const h1Part = parts.find(p => p.startsWith('h1='));
-  if (!tsPart || !h1Part) return false;
-
-  const ts = tsPart.split('=')[1];
-  const h1 = h1Part.split('=')[1];
-
-  const payload = `${ts}:${body}`;
-  const computedHash = crypto.createHmac('sha256', secret).update(payload).digest('hex');
-  return computedHash === h1;
-}
-
-export async function POST(req: Request) {
-  const rawBody = await req.text();
-  const signature = req.headers.get('Paddle-Signature')!;
-  const secret = process.env.PADDLE_WEBHOOK_SECRET!;
-
-  if (!verifyPaddleSignature(rawBody, signature, secret)) {
-    return NextResponse.json({ error: 'Invalid Paddle signature' }, { status: 400 });
-  }
-
-  const event = JSON.parse(rawBody);
-  const eventType = event.event_type;
-  const data = event.data;
-
-  switch (eventType) {
-    case 'subscription.created':
-    case 'subscription.updated': {
-      const workspaceId = data.custom_data?.workspaceId;
-      if (!workspaceId) break;
-
-      await db.insert(subscriptions).values({
-        id: data.id,
-        workspaceId,
-        gateway: 'paddle',
-        gatewayCustomerId: data.customer_id,
-        gatewaySubscriptionId: data.id,
-        gatewayPriceId: data.items[0].price.id,
-        status: data.status, // active, trialing, paused
-        currentPeriodEnd: new Date(data.current_billing_period.ends_at),
-      }).onConflictDoUpdate({
-        target: subscriptions.workspaceId,
-        set: {
-          status: data.status,
-          currentPeriodEnd: new Date(data.current_billing_period.ends_at),
-          gatewayPriceId: data.items[0].price.id,
-        }
-      });
-      break;
-    }
-    case 'subscription.canceled': {
-      await db.update(subscriptions)
-        .set({ status: 'canceled' })
-        .where(eq(subscriptions.gatewaySubscriptionId, data.id));
-      break;
-    }
-  }
-
-  return NextResponse.json({ received: true });
-}
-```
-
-### E. FastSpring Integration
-Merchant of Record. Verified via an HMAC-SHA256 signature key verification.
-
-```typescript
-import { NextResponse } from 'next/server';
-import crypto from 'crypto';
-import { db } from '@/lib/db';
-import { subscriptions } from '@/lib/db/schema';
-import { eq } from 'drizzle-orm';
-
-function verifyFastSpringSignature(body: string, signature: string, secretKey: string): boolean {
-  const hash = crypto.createHmac('sha256', secretKey).update(body).digest('base64');
-  return hash === signature;
-}
-
-export async function POST(req: Request) {
-  const rawBody = await req.text();
-  const signature = req.headers.get('X-FS-Signature')!;
-  const secretKey = process.env.FASTSPRING_SHARED_SECRET!;
-
-  if (!verifyFastSpringSignature(rawBody, signature, secretKey)) {
-    return NextResponse.json({ error: 'Invalid FastSpring signature' }, { status: 400 });
-  }
-
-  const payload = JSON.parse(rawBody);
-
-  for (const event of payload.events) {
-    switch (event.type) {
-      case 'subscription.activated': {
-        const sub = event.data;
-        const workspaceId = sub.tags?.workspaceId;
-        if (!workspaceId) break;
-
-        await db.insert(subscriptions).values({
-          id: sub.id,
-          workspaceId,
-          gateway: 'fastspring',
-          gatewayCustomerId: sub.account,
-          gatewaySubscriptionId: sub.id,
-          gatewayPriceId: sub.product,
-          status: 'active',
-          currentPeriodEnd: new Date(sub.nextSession),
-        });
-        break;
-      }
-      case 'subscription.canceled': {
-        const sub = event.data;
-        await db.update(subscriptions)
-          .set({ status: 'canceled' })
-          .where(eq(subscriptions.gatewaySubscriptionId, sub.id));
-        break;
-      }
-    }
-  }
-
-  return NextResponse.json({ received: true });
-}
-```
-
----
-
-## 4. Best Practices for Webhook Handlers
-
-1. **Webhook Idempotency**: Payment gateways can redeliver webhooks. Always store a list of processed event IDs in your database to prevent duplicate actions:
-   ```typescript
-   const processed = await db.query.processedEvents.findFirst({ where: eq(processedEvents.id, eventId) });
-   if (processed) return NextResponse.json({ received: true });
-   ```
-2. **Handle Async Work Gracefully**: Send a fast response (`200 OK`) back to the gateway first, then process any heavy logic asynchronously (or via queue systems like BullMQ) if necessary, to avoid gateway timeouts.
-3. **Database Locks**: Run your update queries inside clean transactions to avoid concurrency anomalies.

package/skills/self-evolving-memory-graph/SKILL.md

@@ -1,91 +0,0 @@
----
-name: self-evolving-memory-graph
-description: "Grants the AI long-term episodic memory. The agent autonomously documents the user's coding preferences, past mistakes to avoid, and architectural decisions into a persistent learning graph."
-author: "Roedy Rustam"
----
-
-# Self-Evolving Memory Graph (Episodic Memory)
-
-[English](#english) | [Bahasa Indonesia](#bahasa-indonesia)
-
----
-
-<a name="english"></a>
-## English
-
-### Orchestration & Integration
-Connects and orchestrates with relevant domain skills like `brainstorming`, `zero-to-prod-orchestrator`, and `project-context-mapper` to ensure cohesive execution.
-
-### Description
-Claude forgets everything once a chat is cleared, and its "Project Knowledge" requires manual human updating. This skill gives Antigravity the "superpower" of continuous, autonomous self-improvement. The agent actively listens for user corrections, stylistic preferences, and hard-learned debugging lessons, writing them into a persistent `LEARNING_GRAPH.md` (or `.agents/LEARNING.md`) file. The agent gets smarter and more aligned with the user over time.
-
-### Trigger Conditions
-Activate this skill when:
-- The user corrects your code (e.g., "Don't use `any`, use `unknown`", or "Always use Arrow functions").
-- You just spent a long time fixing a very complex bug.
-- The user says "Remember this for the future."
-
-### Core Concepts
-
-#### 1. Memory Encoding
-Whenever a hard lesson is learned or a strong user preference is stated, do not just say "I will remember that." You must physically write it down.
-Use the `multi_replace_file_content` or `write_to_file` tool to append the lesson to the memory file.
-
-#### 2. Memory Format (`LEARNING_GRAPH.md`)
-```markdown
-# 🧠 Self-Evolving Memory Graph
-
-## User Stylistic Preferences
-- [2026-08-12] Always use `Tailwind v4 @theme` variables instead of arbitrary values like `text-[#ff0000]`.
-- [2026-08-12] Prefer functional components with `const` over `function` declarations.
-
-## Hard-Learned Lessons (Avoid these mistakes)
-- [2026-08-11] Supabase RLS policies: Never use `auth.uid()` in a `FOR ALL` policy without checking role claims. It caused an infinite recursion bug in `users` table.
-
-## Architectural Decisions
-- [2026-08-10] State Management: We exclusively use `Zustand` for global state. Do not suggest Redux.
-```
-
-#### 3. Memory Retrieval
-Ensure `session-context-loader` is configured to read this memory file at the start of every new chat session. 
-
-#### 4. Cross-Project Episodic Memory (Global Context)
-- **Continuous Capture**: For complex architectural decisions or bug fixes that span beyond a single project, extract the root cause and solution into a global knowledge graph (e.g., `~/.gemini/knowledge` or equivalent `<appDataDir>/knowledge` KI system).
-- **Contextual Retrieval**: On new sessions, search the global context directory for similar past issues before diving into complex bugs.
-- **Synthesis & Injection**: Inject the historical context directly into the current execution loop, stating explicitly: *"I remember we solved this architectural issue in Project X using technique Y. Applying the same proven pattern here."*
-
----
-
-### Integration with Other Skills (MANDATORY)
-- `session-context-loader` — Essential for loading the `LEARNING_GRAPH.md` when a new session starts.
-- `project-context-mapper` — The context map tracks *where* things are; the memory graph tracks *how* and *why* things are built.
-
-### Referenced By Orchestrators (MANDATORY)
-- `brainstorming` — Add to "Discovery & Audit".
-- `zero-to-prod-orchestrator` — Phase 1 (Discovery & Architecture).
-
----
-
-<a name="bahasa-indonesia"></a>
-## Bahasa Indonesia
-
-### Integrasi Orkestrasi
-Terhubung dan mengorkestrasi skill domain yang relevan seperti `brainstorming`, `zero-to-prod-orchestrator`, dan `project-context-mapper` untuk memastikan eksekusi yang kohesif.
-
-### Deskripsi
-Claude melupakan segalanya saat sesi chat baru dimulai. Skill ini memberi Anda "kekuatan super" berupa *Ingatan Jangka Panjang* yang berevolusi sendiri. Agen secara aktif mencatat preferensi koding pengguna, pelajaran dari *bug* yang sulit dipecahkan, dan keputusan arsitektur ke dalam file persisten `LEARNING_GRAPH.md`. 
-
-### Kondisi Pemicu
-- Saat pengguna mengoreksi gaya koding Anda (misal: "Gunakan bahasa Indonesia baku", "Jangan pakai `var`").
-- Setelah Anda berhasil memecahkan *bug* yang menghabiskan waktu lama.
-- Saat pengguna berkata "Ingat ini untuk proyek ke depannya."
-
-### Panduan Singkat
-- **Jangan Hanya Berjanji:** Jika pengguna mengoreksi Anda, jangan sekadar menjawab "Baik, saya akan ingat." LLM tidak punya ingatan bawaan antar-sesi. Anda **wajib** menulis koreksi tersebut ke dalam file `LEARNING_GRAPH.md` di folder `.agents/` atau direktori *root*.
-- **Kategorisasi Ingatan:** Pisahkan ingatan menjadi: Preferensi Gaya (*Style*), Pelajaran Berharga (*Lessons Learned*), dan Keputusan Arsitektur (*Decisions*).
-- **Semakin Lama Semakin Pintar:** Dengan membaca file ini di awal setiap percakapan, Anda tidak akan pernah mengulangi kesalahan yang sama dua kali.
-
-### Memori Episodik Lintas-Proyek (Konteks Global)
-- **Penangkapan Berkelanjutan**: Untuk bug yang rumit dan pola arsitektur tingkat lanjut, ekstrak solusi ke dalam grafik pengetahuan global (misal: `~/.gemini/knowledge`).
-- **Pencarian Kontekstual**: Sebelum memecahkan masalah kompleks baru, cari direktori konteks global untuk kasus serupa.
-- **Sintesis & Injeksi**: Secara proaktif sebutkan: *"Saya ingat kita menyelesaikan ini di Proyek X dengan cara Y, saya akan menerapkannya di sini."*

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

@@ -1,83 +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
-
-### Orchestration & Integration
-Connects and orchestrates with relevant domain skills like `brainstorming`, `zero-to-prod-orchestrator`, and `project-context-mapper` to ensure cohesive execution.
-
-### 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
-
-### Integrasi Orkestrasi
-Terhubung dan mengorkestrasi skill domain yang relevan seperti `brainstorming`, `zero-to-prod-orchestrator`, dan `project-context-mapper` untuk memastikan eksekusi yang kohesif.
-
-### 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.