create-vasvibe 1.1.0 → 1.2.0

package/template/agent/workflows/sysarch.md

@@ -174,106 +174,39 @@ Jika ada yang tidak yakin, saya akan memberikan rekomendasi berdasarkan best pra
 
 **Step 6: Calculate Resource Requirements**
 
-Based on user input, calculate:
-
-#### **Database Sizing:**
-```python
-# Example calculation
-total_users = user_input['target_users_1year']
-bookings_per_user_per_year = 2  # average
-total_bookings = total_users * bookings_per_user_per_year
-
-# Estimate database size
-db_rows_estimate = {
-    'users': total_users,
-    'bookings': total_bookings,
-    'payments': total_bookings * 1.5,  # DP + pelunasan
-    'ships': 10,
-    'pricing': 100,
-    'seasonal_pricing': 200,
-    'audit_logs': total_bookings * 5,
-}
-
-# Database size (rough estimate)
-avg_row_size_kb = 2  # KB per row
-total_rows = sum(db_rows_estimate.values())
-db_size_gb = (total_rows * avg_row_size_kb) / 1024 / 1024
-db_size_with_indexes = db_size_gb * 1.5  # indexes + overhead
-recommended_db_storage = db_size_with_indexes * 3  # growth buffer
-```
+Gunakan rules of thumb berikut untuk menghitung estimasi dari jawaban user di Step 4:
 
-#### **File Storage Sizing:**
-```python
-files_per_day = user_input['file_uploads_per_day']
-avg_file_size_mb = user_input['avg_file_size_mb']
-retention_years = user_input['retention_years']
+#### **Database Storage**
+- Estimasi total rows: jumlah users + (users × 2 bookings/tahun) + (bookings × 1.5 payments) + audit logs
+- Ukuran per row rata-rata: ~2 KB
+- Tambahkan 1.5× untuk indexes dan overhead
+- Tambahkan 3× buffer untuk pertumbuhan
+- **Formula singkat:** `(total_rows × 2 KB × 1.5 × 3) / (1024²) = GB`
 
-daily_storage_mb = files_per_day * avg_file_size_mb
-yearly_storage_gb = (daily_storage_mb * 365) / 1024
-total_storage_gb = yearly_storage_gb * retention_years
-recommended_file_storage = total_storage_gb * 1.3  # buffer
-```
+#### **File Storage**
+- `(files_per_day × avg_size_MB × 365 × retention_years × 1.3) / 1024 = GB`
 
-#### **Memory (RAM) Sizing:**
-```python
-# Application server
-concurrent_users = user_input['concurrent_users_peak']
-ram_per_user_mb = 2  # Next.js + session
-app_ram_base = 512  # Base Next.js process
-app_ram_total = app_ram_base + (concurrent_users * ram_per_user_mb)
-
-# Database server
-db_connections = concurrent_users * 1.5
-ram_per_connection_mb = 5
-db_ram_base = 1024  # PostgreSQL base
-db_ram_total = db_ram_base + (db_connections * ram_per_connection_mb)
-
-# Redis cache
-redis_ram = 512  # MB for session + cache
-
-total_ram_gb = (app_ram_total + db_ram_total + redis_ram) / 1024
-recommended_ram = total_ram_gb * 1.5  # headroom
-```
+#### **RAM**
+- App server: 512 MB base + (concurrent_users × 2 MB)
+- DB server: 1024 MB base + (concurrent_users × 1.5 connections × 5 MB/connection)
+- Redis: 512 MB flat
+- Total × 1.5 headroom → round up ke tier terdekat (4/8/16/32 GB)
 
-#### **CPU Sizing:**
-```python
-api_requests_per_minute = user_input['api_requests_per_minute']
-cpu_intensive_operations = ['pdf_generation', 'excel_export', 'image_processing']
-
-# Rule of thumb: 1 vCPU handles ~100 req/min for standard CRUD
-# 1 vCPU handles ~20 req/min for CPU-intensive operations
-base_vcpu = 2
-vcpu_for_api = api_requests_per_minute / 100
-vcpu_total = max(base_vcpu, vcpu_for_api)
-recommended_vcpu = vcpu_total * 1.5  # buffer
-```
+#### **CPU (vCPU)**
+- Standard CRUD API: 1 vCPU per 100 req/min
+- CPU-intensive (PDF, export, image): 1 vCPU per 20 req/min
+- Minimum 2 vCPU, tambahkan 1.5× buffer
 
-#### **Bandwidth Calculation:**
-```python
-avg_page_size_kb = 500  # KB
-avg_api_response_kb = 50  # KB
-daily_page_views = concurrent_users * 20  # pages per user per day
-daily_api_calls = api_requests_per_minute * 60 * 24
-
-daily_bandwidth_gb = (
-    (daily_page_views * avg_page_size_kb) +
-    (daily_api_calls * avg_api_response_kb) +
-    (files_per_day * avg_file_size_mb * 1024)  # uploads
-) / 1024 / 1024
-
-monthly_bandwidth_gb = daily_bandwidth_gb * 30
-recommended_bandwidth = monthly_bandwidth_gb * 1.5  # buffer
-```
+#### **Bandwidth (per bulan)**
+- `(page_views/day × 500 KB + api_calls/day × 50 KB + uploads/day × avg_size) × 30 × 1.5 / (1024²) = GB`
 
 **Step 7: Document Calculations**
-```markdown
-Create: `architecture/capacity_planning.md`
-- User input summary
-- Calculation formulas
-- Resource estimates
-- Growth projections (6 months, 1 year, 2 years)
-- Peak vs normal load comparison
-```
+
+Buat file `architecture/capacity_planning.md` yang berisi:
+- Ringkasan jawaban user
+- Estimasi resource (DB, storage, RAM, CPU, bandwidth) dengan angka aktual
+- Proyeksi pertumbuhan 6 bulan, 1 tahun, 2 tahun
+- Perbandingan beban normal vs peak season
 
 ---
 
@@ -350,5 +283,16 @@ Specs:
     - Type: Cloud LB or Nginx
   
   Estimated Cost: $[amount]/month
+```
+
+## Work Depth
+> 📎 Baca level aktif di `project_overview.md` → `WORK_DEPTH`. Detail: `agent/workflows/_shared/work-depth.md`
+
+| Level | Behavior |
+|-------|----------|
+| **fast** | Arsitektur dasar, skip capacity planning detail |
+| **standard** | Arsitektur lengkap + capacity planning |
+| **deep** | + Disaster recovery plan, multi-region consideration, security architecture review |
+
 ## State Management
 > 📎 **BACA DAN IKUTI** panduan di `agent/workflows/_shared/state-management.md`

package/template/agent/workflows/tester.md

@@ -1,5 +1,5 @@
-**ACT AS:** QA Automation Engineer.
-**CONTEXT:** Membuat dan menjalankan automated Playwright End-to-End (E2E) dan unit test.
+**ACT AS:** E2E Test Automation Engineer.
+**CONTEXT:** Membuat dan menjalankan automated Playwright End-to-End (E2E) test berdasarkan spesifikasi yang sudah diapprove. Berbeda dari QA Agent yang melakukan static review — agent ini mengeksekusi test scenario secara otomatis di browser.
 
 **INSTRUCTION STEPS:**
 1.  **Load Context:**
@@ -84,5 +84,14 @@
 
 **INPUT SAYA:**
 "Buat dan jalankan tes untuk file code: [NAMA FILE CODE]"
+## Work Depth
+> 📎 Baca level aktif di `project_overview.md` → `WORK_DEPTH`. Detail: `agent/workflows/_shared/work-depth.md`
+
+| Level | Behavior |
+|-------|----------|
+| **fast** | Happy path E2E saja, skip edge cases |
+| **standard** | Full E2E test suite sesuai spec |
+| **deep** | + Edge cases, negative tests, performance assertion dasar |
+
 ## State Management
 > 📎 **BACA DAN IKUTI** panduan di `agent/workflows/_shared/state-management.md`

package/template/project_overview_example.md

@@ -38,4 +38,18 @@
 - **Responsive Strategy:** (e.g., Mobile-First approach)
 
 ## 6. Constraints & Compliance
-*(Opsional: GDPR, Offline First, High Performance requirement, dll)*
+*(Opsional: GDPR, Offline First, High Performance requirement, dll)*
+
+## 7. Project Settings
+
+- **WORK_DEPTH:** {{workDepth}}  <!-- fast | standard | deep -->
+
+> **Penjelasan Work Depth:**
+> - `fast` — Prototype/MVP: agent mengerjakan inti fitur saja, skip output optional (unit test, full docs, edge cases). Cocok untuk eksplorasi cepat.
+> - `standard` — Development normal: semua step agent dijalankan sesuai template. **Default yang disarankan.**
+> - `deep` — Produksi kritikal: semua validasi, security review, dan edge cases wajib. Cocok untuk fitur pembayaran, autentikasi, atau sistem high-stakes.
+>
+> **Di mana bisa diubah:**
+> 1. **File ini** (`project_overview.md`) — ubah nilai `WORK_DEPTH:` untuk mengubah default seluruh project.
+> 2. **Orchestrator command** — tambah parameter `depth=` saat memanggil pipeline, contoh: `/start-feature "Login" depth=fast`. Override untuk satu pipeline saja.
+> 3. **Langsung ke agent** — instruksikan agent secara eksplisit, contoh: `"gunakan mode: deep"`. Override tertinggi.

package/template/schemas/changelog.template.md

@@ -0,0 +1,34 @@
+# CHANGELOG
+
+All notable changes to this project will be documented in this file.
+
+Format: [Semantic Versioning](https://semver.org/) — `MAJOR.MINOR.PATCH`
+- **MAJOR**: Breaking change atau perubahan arsitektur besar
+- **MINOR**: Fitur baru yang backward-compatible
+- **PATCH**: Bug fix
+
+---
+
+## [Unreleased]
+
+### Added
+- (Fitur baru yang belum di-release)
+
+### Changed
+- (Perubahan behaviour yang sudah ada)
+
+### Fixed
+- (Bug fix)
+
+### Removed
+- (Fitur yang dihapus)
+
+---
+
+## [X.Y.Z] — YYYY-MM-DD
+
+### Added
+- TASK-XXX: [Nama fitur] — [deskripsi singkat]
+
+### Fixed
+- TASK-XXX: [Nama bug fix] — [deskripsi singkat]

package/template/schemas/dev_log.template.md

@@ -1,26 +1,20 @@
-# Development Log — TASK-XXX: [Task Name]
+# DEVELOPMENT LOG - TASK-XXX: [Task Name]
 
-## Session Info
-- **Agent:** Developer Agent
-- **Date:** [YYYY-MM-DD]
-- **Branch:** feature/[nama]
-- **Spec:** specifications/XXX_spec_*.md
+**Target Spec:** specifications/XXX_spec_*.md
+**Date:** [YYYY-MM-DD HH:MM]
+**Status:** [Completed / Partial]
 
-## Changes Made
-| File | Action | Description |
-|------|--------|-------------|
-| ... | Created/Modified/Deleted | ... |
+## 1. Implementation Summary
+(Jelaskan secara naratif logika apa saja yang baru saja dibangun. Bagaimana data mengalir?)
 
-## Decisions & Rationale
-...
+## 2. Files Created/Modified
+- `codes/src/...` (Sebutkan fungsi utama file ini)
+- `codes/components/...`
 
-## Issues Encountered
-...
+## 3. Technical Notes
+(Catatan untuk Developer lain atau QA. Misal: "Perlu set environment variable API_KEY dulu")
 
-## Self-Reflection
-- Security: ...
-- Performance: ...
-- Code Quality: ...
-
-## Status Update
-- [x] Task status updated: development → ready_to_test
+## 4. Revision History
+| Timestamp | Changes |
+|-----------|---------|
+| [YYYY-MM-DD HH:MM] | Initial development |

package/template/schemas/specification.template.md

@@ -9,19 +9,49 @@
 ## User Story
 Sebagai [role], saya ingin [action], sehingga [benefit].
 
+## Technical Flow
+1. [Langkah 1 — contoh: User submit form login]
+2. [Langkah 2 — contoh: Backend validasi credentials]
+3. [Langkah 3 — contoh: Return JWT token]
+
 ## Acceptance Criteria
 - [ ] ...
+- [ ] ...
 
 ## API Contract
 ### [METHOD] /api/endpoint
-**Request:** ...
-**Response:** ...
+**Request:**
+```json
+{}
+```
+**Response (200):**
+```json
+{}
+```
+**Response (Error):**
+```json
+{}
+```
 
 ## Database Changes
-...
+(Tabel baru, kolom baru, atau index yang dibutuhkan — atau tulis "None")
 
 ## UI/UX
-...
+(Screenshot mockup, deskripsi komponen, atau link ke desain — atau tulis "None")
 
 ## Edge Cases & Validation
-...
+- [ ] ...
+
+---
+
+## Human Approval
+
+**Human Approval Status:** pending | approved | revision_requested
+
+**Human Feedback:**
+> (Kosongkan jika belum ada feedback. Analyst Agent akan mengisi berdasarkan masukan reviewer.)
+
+## Revision History
+| Date | Author | Changes |
+|------|--------|---------|
+| [YYYY-MM-DD] | Analyst Agent | Initial draft |