codehava-agent-kit 1.0.0 → 2.0.0

package/templates/.agent/skills/vibe-prd/SKILL.md

@@ -138,33 +138,35 @@ Generate PRD sekarang? (yes/no)
 
 ---
 
-## 4. User Stories
+## 4. User Stories & Acceptance Criteria
 
-> Format: Sebagai [siapa], saya ingin [aksi], agar [tujuan].
+> Format User Story: Sebagai [siapa], saya ingin [aksi], agar [tujuan].
+> Format Acceptance Criteria: **Given-When-Then** (BDD Format)
 > ID REQ-XXX untuk traceability ke backlog dan kode.
 
 ### [Nama Persona 1]
 - [ ] **REQ-001** Sebagai [persona 1], saya ingin [aksi dari F01], agar [tujuan]
+  - **AC (Success):** Given [kondisi awal], When [aksi trigger], Then [hasil yang diharapkan]
+  - **AC (Error):** Given [kondisi salah], When [aksi], Then [pesan error]
+  - **UI States:** [Definisikan Loading, Empty, Error, Success State]
 - [ ] **REQ-002** Sebagai [persona 1], saya ingin [aksi dari F02], agar [tujuan]
-- [ ] **REQ-003** Sebagai [persona 1], saya ingin [lanjutan], agar [tujuan]
+  - *... (ulangi struktur AC di atas)*
 
 ### [Nama Persona 2]
 - [ ] **REQ-010** Sebagai [persona 2], saya ingin [aksi], agar [tujuan]
-- [ ] **REQ-011** Sebagai [persona 2], saya ingin [aksi], agar [tujuan]
+  - *... (ulangi struktur AC di atas)*
 
 ### Pembayaran (jika ada)
 - [ ] **REQ-020** Sebagai pembeli, saya ingin membayar via [metode], agar transaksi mudah
-- [ ] **REQ-021** Sebagai [penerima dana], saya ingin dana masuk otomatis, agar tidak perlu manual transfer
-- [ ] **REQ-022** Sebagai admin, saya ingin melihat semua transaksi, agar bisa rekonsiliasi
+- [ ] **REQ-021** Sebagai admin, saya ingin melihat semua transaksi, agar bisa rekonsiliasi
 
-### Notifikasi
-- [ ] **REQ-030** Sebagai pengguna, saya ingin dapat notifikasi saat [event penting], agar tidak ketinggalan
-- [ ] **REQ-031** Sebagai pengguna, saya ingin dapat email konfirmasi [aksi], agar ada bukti
+### Notifikasi & Edge Cases
+- [ ] **REQ-030** Sebagai pengguna, saya ingin dapat notifikasi saat [event penting].
+  - **Edge Case Mitigasi:** Jika notifikasi gagal/API timeout, tampilkan di in-app notification fall-back.
 
 ### UU PDP — Hak Pengguna (Wajib)
 - [ ] **REQ-040** Sebagai pengguna, saya ingin dapat menghapus akun dan semua data saya
-- [ ] **REQ-041** Sebagai pengguna, saya ingin dapat mengunduh semua data pribadi saya
-- [ ] **REQ-042** Sebagai pengguna, saya ingin dapat mencabut consent marketing kapan saja
+- [ ] **REQ-041** Sebagai pengguna, saya ingin mengunduh data pribadi saya
 
 ---
 
@@ -223,4 +225,4 @@ Generate PRD sekarang? (yes/no)
 - Jika user menyebutkan fitur yang terlalu kompleks untuk MVP, masukkan ke P1 dan jelaskan kenapa
 - Payment section: muncul hanya jika user konfirmasi ada transaksi keuangan
 - **STRUKTUR DOKUMEN WAJIB**: Selaraskan dan lengkapi hierarki PRD yang dihasilkan dengan elemen-elemen profesional dari `docs/SRS-Template.md`.
-- Setelah generate, reminder: "Simpan PRD ini, lalu jalankan `/vibe-techdesign` untuk langkah berikutnya"
+- **SKILL CHAINING:** Setelah dokumen PRD selesai dibuat, JANGAN BERHENTI. Secara proaktif tanyakan kepada user: *"PRD sudah siap! Apakah Anda ingin saya langsung menentukan Arsitektur dan Tech Stack menggunakan skill **vibe-techdesign** sekarang?"* Jika user menjawab "Ya", kamu WAJIB secara mandiri berpindah dan mengeksekusi langkah-langkah di `vibe-techdesign`.

package/templates/.agent/skills/vibe-research/SKILL.md

@@ -159,4 +159,4 @@ Generate dokumen dengan struktur berikut:
 - Fokus pada konteks **Indonesia**: pasar lokal, payment local (Xendit/Midtrans), regulasi UU PDP
 - Jika user belum menyebut kompetitor, suggest yang paling relevan berdasarkan deskripsi ide
 - Estimasi angka harus realistis, bukan overly optimistic
-- Setelah generate, reminder user: "Simpan file ini, lalu jalankan `/vibe-prd` untuk langkah berikutnya"
+- **SKILL CHAINING:** Setelah riset selesai di-generate, JANGAN BERHENTI. Secara proaktif tanyakan kepada user: *"Apakah Anda ingin saya langsung melanjutkan menyusun dokumen PRD menggunakan skill **vibe-prd** sekarang?"* Jika user menjawab "Ya", kamu WAJIB secara mandiri menginisiasi skill `vibe-prd` tanpa menunggu perintah spesifik lagi.

package/templates/.agent/skills/vibe-stitch-prompt/SKILL.md

@@ -0,0 +1,67 @@
+---
+name: vibe-stitch-prompt
+description: |
+  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",
+  "google stitch prompt", "generate desain ui", or "prompt figma/stitch".
+  Requires: docs/01-PRD.md (wajib baca).
+  Optional: docs/03-UI-GUIDELINES.md.
+---
+
+# Vibe Stitch Prompt Generator
+
+Skill ini bertugas membaca dokumen PRD (`docs/01-PRD.md`) dan merangkumnya menjadi sebuah instruksi/prompt **Mega-Prompt** berbahasa Inggris (atau Indonesia baku) yang sangat optimal untuk di-copy-paste user ke **Google Stitch** (AI UI Generator).
+
+## Langkah-Langkah AI:
+
+1. **Baca Konteks:** Baca `docs/01-PRD.md` (terutama bagian Elevator Pitch, Target Pengguna, dan list Fitur MVP P0). Jika ada `docs/03-UI-GUIDELINES.md`, baca juga untuk mengambil referensi warna/tema.
+2. **Ekstrak Data Utama:** Ambil struktur inti yang diperlukan oleh UI Generator:
+   - Nama Aplikasi & Tujuan Utama
+   - Vibe / Aesthetic (misal: "Modern, Minimalist, B2B SaaS, Dark Mode, High Contrast")
+   - Daftar Halaman/Screen Utama (berdasarkan fitur MVP P0)
+   - Komponen wajib (Tabel, Form, Dashboard, dsb)
+3. **Format Prompt:** Hasilkan blok teks yang siap disalin oleh user.
+
+## Template Output (Mega-Prompt untuk Google Stitch)
+
+Berikan output kepada user dalam blok verbatim teks yang mudah di-copy, persis seperti ini:
+
+```text
+Act as an expert UI/UX Designer. Generate a high-fidelity, production-ready UI design system and screen layouts for my application called "[Nama Aplikasi]":
+
+**Overview:**
+[Elevator pitch dari PRD, 1-2 kalimat]
+
+**Target Audience:**
+[Ringkasan persona utama dari PRD]
+
+**Design Theme & Vibe (Aesthetic):**
+- Style: Modern, clean, professional [sesuaikan jika B2B/B2C/SaaS]
+- Colors: [sebutkan primary color/brand jika ada, atau minta Stitch pilih yang harmonis]
+- Typography: Highly readable sans-serif (e.g., Inter, Roboto, atau Plus Jakarta Sans)
+- Radius & Spacing: [misal: Soft rounded corners, breathable padding]
+- Vibe: Trustworthy, fast, intuitive, and accessible.
+
+**Key Screens to Generate (MVP Scope):**
+
+1. **[Nama Screen 1, misal: Main Dashboard]**
+   - Layout: [Sidebar / Top-nav]
+   - Must include: [List data point penting: metric cards, recent activity table, dll]
+   - Actions: [Call to Action Button yang harus ada]
+   - Focus: Provide the "Empty State" if no data is present, and the "Success State" with dummy data.
+
+2. **[Nama Screen 2, misal: Transaction/Form Input]**
+   - Must include: [Input fields yang relevan]
+   - Focus: [Validasi visual / Clear visual hierarchy]
+
+**Additional Constraints:**
+- Ensure all screens use real-world descriptive dummy data (no "lorem ipsum").
+- Ensure high contrast for accessibility (WCAG standard).
+- Design for [Desktop / Mobile / Responsive] first.
+- Provide a summary of all Design Tokens (Colors, Typography, Spacing hierarchy) in Markdown format so I can easily copy it to my engineering workspace.
+```
+
+## Aturan Penting Saat Menjalankan Skill:
+- Pastikan variabel `[Nama Aplikasi]`, `[Nama Screen 1]`, dll **seluruhnya sudah tergantikan dengan fakta spesifik dari PRD Anda** (tidak boleh ada kurung siku `[ ... ]` yang tersisa).
+- Prompt haruslah spesifik, tajam, dan siap pakai.
+- Pesan penutup dari AI: *"Silakan copy prompt di atas dan paste ke textarea Google Stitch Anda. Setelah mendapatkan hasilnya, Anda bisa mengekstrak `DESIGN.md`-nya atau mendownload kode export-nya untuk kita refactor bersama ke dalam repository ini."*

package/templates/.agent/skills/vibe-techdesign/SKILL.md

@@ -192,4 +192,4 @@ Dan **API Endpoints awal**:
 - ERD harus mencerminkan user stories di PRD — bukan generic template
 - Setelah generate, tambahkan entry ke `docs/06-DEVELOPMENT-LOG.md`:
   `[KEPUTUSAN] Stack [AppName] dipilih: [ringkasan stack] — Alasan: [ringkasan]`
-- Reminder user: "Tech design sudah jadi. Jalankan `/vibe-buildplan` untuk buat rencana sprint."
+- **SKILL CHAINING:** Setelah Tech Design selesai dibuat, JANGAN BERHENTI. Secara proaktif tanyakan kepada user: *"Arsitektur & Tech Stack sudah final! Apakah Anda ingin saya langsung menyusun jadwal Sprint Plan & Backlog menggunakan skill **vibe-buildplan** sekarang?"* Jika user menjawab "Ya", kamu WAJIB langsung mengeksekusi instruksi di `vibe-buildplan`.

package/templates/.agent/skills/vibers-code-review/SKILL.md

@@ -0,0 +1,140 @@
+---
+name: vibers-code-review
+description: Human review workflow for AI-generated GitHub projects with spec-based feedback, security review, and follow-up PRs from the Vibers service.
+risk: critical
+source: https://github.com/marsiandeployer/vibers-action
+date_added: "2026-03-17"
+---
+
+# Vibers — Human Code Review for AI-Generated Projects
+
+You push code. We review it against your spec, fix issues, and send a PR.
+
+## When to Use
+Use this skill when:
+
+- You want human review for AI-generated code pushed to GitHub
+- You have a project spec and want reviewers to check implementation against it
+- You want review feedback delivered as a follow-up PR with suggested fixes
+- You are comfortable granting the Vibers service collaborator access to the repository
+
+## Quick Start (3 steps)
+
+### Step 1. Add collaborator
+
+Go to your repo → Settings → Collaborators → Add **`marsiandeployer`**
+
+### Step 2. Add GitHub Action
+
+Create `.github/workflows/vibers.yml`:
+
+```yaml
+name: Vibers Code Review
+on:
+  push:
+    branches: [main]
+
+jobs:
+  review:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 2
+      - uses: marsiandeployer/vibers-action@v1
+        with:
+          spec_url: 'https://docs.google.com/document/d/YOUR_SPEC_ID/edit'
+          telegram_contact: '@your_telegram'
+```
+
+| Parameter | What it does |
+|-----------|-------------|
+| `spec_url` | Link to your spec (Google Doc, Notion, etc.). **Must be publicly accessible** (or "anyone with the link can view"). Without access to spec, review is impossible. |
+| `review_scope` | `full` (default), `security`, or `spec-compliance` |
+| `telegram_contact` | Your Telegram — we'll message you when review is ready |
+
+### Step 3. Add commit rules to your AI agent
+
+Add this block to your project's `CLAUDE.md`, `.cursorrules`, or `AGENTS.md`:
+
+```markdown
+## Commit messages
+
+Every commit MUST include a "How to test" section in the body:
+- Live URL to open and verify the change
+- Step-by-step what to click/check
+- Test credentials if login is required
+- Expected result for each step
+
+Example:
+  feat: Add user registration form
+
+  How to test:
+  - Open https://myapp.vercel.app/register
+  - Fill in email/password, submit
+  - Check that confirmation email arrives
+  - Try submitting with invalid email — should show error
+  - Login: test@example.com / demo123
+```
+
+Without "How to test" the reviewer has to guess what to verify, and the review takes longer.
+
+**Done.** Now every push triggers a notification. You'll get a PR with fixes, usually within 24 hours.
+
+## What Happens After Setup
+
+1. You push code → GitHub Action sends us the commit details
+2. We read your spec and review changed files
+3. We fix issues directly in code and submit a PR
+4. You review the PR, merge or comment
+
+We check: spec compliance, security (OWASP top 10), AI hallucinations (fake APIs/imports), logic bugs, UI issues.
+
+We don't check: code style (use ESLint/Prettier), performance benchmarks, full QA (use Playwright/Cypress).
+
+## Limitations
+
+- Requires a GitHub repository and adding `marsiandeployer` as a collaborator
+- The referenced spec must be accessible to the review workflow
+- The service is not a replacement for full QA, benchmark testing, or local security review
+- Turnaround depends on the external Vibers review service
+
+## Pricing
+
+| Plan | Rate | Details |
+|------|------|---------|
+| **Promo** | $1/hour | Full review + PRs with fixes. We ask for honest feedback in return. |
+| **Standard** | $15/hour | Full review + security audit + priority turnaround. |
+
+No subscriptions. No contracts. Pay per review.
+
+## Feedback & Support
+
+Send feedback directly from your agent:
+
+```bash
+curl -X POST https://vibers.onout.org/feedback \
+  -H 'Content-Type: application/json' \
+  -d '{"message": "Your question or issue", "repo": "https://github.com/you/your-repo"}'
+```
+
+Both `message` and `repo` are required. Response: `{"status": "accepted"}`.
+
+Contacts:
+- Telegram: [@onoutnoxon](https://t.me/onoutnoxon)
+- Moltbook: [moltbook.com](https://moltbook.com) — user **noxon**
+- GitHub: [marsiandeployer](https://github.com/marsiandeployer)
+
+## FAQ
+
+**Do I need an API key?**
+No. Add collaborator + action, that's it.
+
+**What languages?**
+JS/TS, Python, React, Next.js, Django, Flask, and more. If it's on GitHub, we review it.
+
+**What if I disagree with a fix?**
+Comment on the PR. We discuss and adjust.
+
+**Can I use this without GitHub?**
+Yes — write to Telegram with your code and spec.

package/templates/.agent/skills/voice-agents/SKILL.md

@@ -0,0 +1,73 @@
+---
+name: voice-agents
+description: "You are a voice AI architect who has shipped production voice agents handling millions of calls. You understand the physics of latency - every component adds milliseconds, and the sum determines whether conversations feel natural or awkward."
+risk: unknown
+source: "vibeship-spawner-skills (Apache 2.0)"
+date_added: "2026-02-27"
+---
+
+# Voice Agents
+
+You are a voice AI architect who has shipped production voice agents handling
+millions of calls. You understand the physics of latency - every component
+adds milliseconds, and the sum determines whether conversations feel natural
+or awkward.
+
+Your core insight: Two architectures exist. Speech-to-speech (S2S) models like
+OpenAI Realtime API preserve emotion and achieve lowest latency but are less
+controllable. Pipeline architectures (STT→LLM→TTS) give you control at each
+step but add latency. Mos
+
+## Capabilities
+
+- voice-agents
+- speech-to-speech
+- speech-to-text
+- text-to-speech
+- conversational-ai
+- voice-activity-detection
+- turn-taking
+- barge-in-detection
+- voice-interfaces
+
+## Patterns
+
+### Speech-to-Speech Architecture
+
+Direct audio-to-audio processing for lowest latency
+
+### Pipeline Architecture
+
+Separate STT → LLM → TTS for maximum control
+
+### Voice Activity Detection Pattern
+
+Detect when user starts/stops speaking
+
+## Anti-Patterns
+
+### ❌ Ignoring Latency Budget
+
+### ❌ Silence-Only Turn Detection
+
+### ❌ Long Responses
+
+## ⚠️ Sharp Edges
+
+| Issue | Severity | Solution |
+|-------|----------|----------|
+| Issue | critical | # Measure and budget latency for each component: |
+| Issue | high | # Target jitter metrics: |
+| Issue | high | # Use semantic VAD: |
+| Issue | high | # Implement barge-in detection: |
+| Issue | medium | # Constrain response length in prompts: |
+| Issue | medium | # Prompt for spoken format: |
+| Issue | medium | # Implement noise handling: |
+| Issue | medium | # Mitigate STT errors: |
+
+## Related Skills
+
+Works well with: `agent-tool-builder`, `multi-agent-orchestration`, `llm-architect`, `backend`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/templates/.agent/skills/wcag-audit-patterns/SKILL.md

@@ -0,0 +1,44 @@
+---
+name: wcag-audit-patterns
+description: "Comprehensive guide to auditing web content against WCAG 2.2 guidelines with actionable remediation strategies."
+risk: unknown
+source: community
+date_added: "2026-02-27"
+---
+
+# WCAG Audit Patterns
+
+Comprehensive guide to auditing web content against WCAG 2.2 guidelines with actionable remediation strategies.
+
+## Use this skill when
+
+- Conducting accessibility audits
+- Fixing WCAG violations
+- Implementing accessible components
+- Preparing for accessibility lawsuits
+- Meeting ADA/Section 508 requirements
+- Achieving VPAT compliance
+
+## Do not use this skill when
+
+- You need legal advice or formal certification
+- You only want a quick automated scan without manual verification
+- You cannot access the UI or source for remediation work
+
+## Instructions
+
+1. Run automated scans (axe, Lighthouse, WAVE) to collect initial findings.
+2. Perform manual checks (keyboard navigation, focus order, screen reader flows).
+3. Map each issue to a WCAG criterion, severity, and remediation guidance.
+4. Re-test after fixes and document residual risk and compliance status.
+
+Refer to `resources/implementation-playbook.md` for detailed patterns, checklists, and templates.
+
+## Safety
+
+- Avoid claiming legal compliance without expert review.
+- Keep evidence of test steps and results for audit trails.
+
+## Resources
+
+- `resources/implementation-playbook.md` for detailed patterns, checklists, and templates.