@ryuenn3123/agentic-senior-core 2.0.19 → 2.0.21

package/lib/cli/templates/api-contract.md.tmpl

@@ -0,0 +1,143 @@
+# API Contract: {{projectName}}
+
+Generated by Agentic-Senior-Core CLI v{{cliVersion}}
+Generated at: {{generatedAt}}
+Template version: {{templateVersion}}
+
+---
+
+## API Design Principles
+
+Per `.agent-context/rules/api-docs.md`:
+- OpenAPI 3.1 specification is mandatory for all HTTP APIs.
+- Every endpoint must have documented request/response schemas.
+- Error responses use typed error codes, never raw strings.
+- Input validation is mandatory on every endpoint.
+
+## Base URL
+
+```
+{{baseUrl}}
+```
+
+---
+
+## Endpoints
+
+### Health Check
+
+```
+GET /health
+```
+
+Response `200`:
+```json
+{
+  "status": "ok",
+  "version": "1.0.0",
+  "timestamp": "2026-01-01T00:00:00Z"
+}
+```
+
+{{#if hasAuth}}
+### Authentication
+
+```
+POST /auth/register
+```
+Request:
+```json
+{
+  "email": "user@example.com",
+  "password": "secure-password",
+  "displayName": "User Name"
+}
+```
+
+```
+POST /auth/login
+```
+Request:
+```json
+{
+  "email": "user@example.com",
+  "password": "secure-password"
+}
+```
+Response `200`:
+```json
+{
+  "token": "jwt-token-here",
+  "expiresIn": 3600
+}
+```
+
+{{/if}}
+### Feature Endpoints
+
+Based on the defined project features, plan these endpoint groups:
+
+{{#each features}}
+#### {{this}}
+
+```
+GET    /api/[resource]         — List
+GET    /api/[resource]/:id     — Detail
+POST   /api/[resource]         — Create
+PUT    /api/[resource]/:id     — Update
+DELETE /api/[resource]/:id     — Delete
+```
+
+{{/each}}
+
+---
+
+## Error Response Format
+
+All error responses follow this structure:
+
+```json
+{
+  "error": {
+    "code": "VALIDATION_ERROR",
+    "message": "Human-readable description",
+    "details": []
+  }
+}
+```
+
+Standard error codes:
+- `VALIDATION_ERROR` (400)
+- `UNAUTHORIZED` (401)
+- `FORBIDDEN` (403)
+- `NOT_FOUND` (404)
+- `CONFLICT` (409)
+- `INTERNAL_ERROR` (500)
+
+---
+
+## Pagination
+
+List endpoints use cursor-based or offset-based pagination:
+
+```
+GET /api/[resource]?page=1&limit=20
+```
+
+Response includes:
+```json
+{
+  "data": [],
+  "pagination": {
+    "page": 1,
+    "limit": 20,
+    "total": 100,
+    "totalPages": 5
+  }
+}
+```
+
+---
+
+This document is a living reference. Update it as API endpoints are implemented.
+Maintain a corresponding OpenAPI 3.1 specification file alongside this document.

package/lib/cli/templates/architecture-decision-record.md.id.tmpl

@@ -0,0 +1,106 @@
+# Catatan Keputusan Arsitektur: {{projectName}}
+
+Dibuat oleh Agentic-Senior-Core CLI v{{cliVersion}}
+Dibuat pada: {{generatedAt}}
+Versi template: {{templateVersion}}
+
+---
+
+## ADR-001: Pemilihan Stack Teknologi
+
+**Status**: Disetujui
+**Tanggal**: {{generatedDate}}
+
+### Konteks
+
+Proyek ini membutuhkan solusi {{primaryDomain}}. Tim mengevaluasi profil stack dan blueprint dari repository governance Agentic-Senior-Core.
+
+### Keputusan
+
+- **Bahasa/Runtime**: {{stackDisplayName}} (sumber: `.agent-context/stacks/{{stackFileName}}`)
+- **Blueprint arsitektur**: {{blueprintDisplayName}} (sumber: `.agent-context/blueprints/{{blueprintFileName}}`)
+- **Database**: {{databaseChoice}}
+- **Autentikasi**: {{authStrategy}}
+
+### Alasan
+
+Stack {{stackDisplayName}} dipilih karena:
+- Selaras dengan domain proyek ({{primaryDomain}}).
+- Repository governance menyediakan blueprint tervalidasi untuk stack ini.
+- Tim memiliki skill pack yang relevan untuk teknologi ini.
+
+### Konsekuensi
+
+- Semua kode harus mengikuti konvensi di `.agent-context/stacks/{{stackFileName}}`.
+- Batas modul harus mengikuti `.agent-context/blueprints/{{blueprintFileName}}`.
+- Akses database harus mengikuti `.agent-context/rules/database-design.md`.
+- Kontrak API harus mengikuti `.agent-context/rules/api-docs.md`.
+
+---
+
+## ADR-002: Pola Arsitektur
+
+**Status**: Disetujui
+**Tanggal**: {{generatedDate}}
+
+### Konteks
+
+Proyek membutuhkan pemisahan concern yang jelas agar tetap mudah dirawat saat skala bertambah.
+
+### Keputusan
+
+Gunakan arsitektur berlapis **Transport - Service - Repository** seperti di `.agent-context/rules/architecture.md`.
+
+{{#if hasDatabase}}
+### Lapisan Database
+
+- Database utama: {{databaseChoice}}
+- Strategi ORM/query: ikuti konvensi stack yang dipilih.
+- Strategi migrasi: migrasi aman dan reversible sesuai `.agent-context/rules/database-design.md`.
+{{/if}}
+
+{{#if hasAuth}}
+### Lapisan Autentikasi
+
+- Strategi: {{authStrategy}}
+- Manajemen secret: tidak boleh hardcoded sesuai `.agent-context/rules/security.md`.
+- Validasi input: wajib di semua endpoint auth sesuai `.agent-context/rules/security.md`.
+{{/if}}
+
+### Konsekuensi
+
+- Setiap modul harus menjaga pemisahan tiga lapis.
+- Import lintas lapis dilarang (transport tidak boleh akses repository langsung).
+- Logic bersama dipindah ke modul shared, bukan di handler transport.
+
+---
+
+## ADR-003: Struktur Proyek
+
+**Status**: Disetujui
+**Tanggal**: {{generatedDate}}
+
+### Keputusan
+
+Struktur direktori proyek mengikuti blueprint terpilih (`{{blueprintDisplayName}}`). Direktori utama:
+
+```
+{{projectName}}/
+  src/
+    modules/          - modul fitur (masing-masing berisi transport, service, repository)
+    shared/           - utilitas, tipe, konstanta bersama
+    config/           - konfigurasi environment dan aplikasi
+  docs/               - dokumentasi proyek (direktori ini)
+  tests/              - test suites
+  .agent-context/     - aturan dan kebijakan governance
+```
+
+### Konsekuensi
+
+- Fitur baru ditambahkan sebagai modul mandiri.
+- Kode shared diekstrak jika dipakai oleh dua modul atau lebih.
+- Konfigurasi dipusatkan dan divalidasi saat startup.
+
+---
+
+Tambahkan ADR baru di bawah ini saat ada keputusan arsitektur baru.

package/lib/cli/templates/architecture-decision-record.md.tmpl

@@ -0,0 +1,106 @@
+# Architecture Decision Record: {{projectName}}
+
+Generated by Agentic-Senior-Core CLI v{{cliVersion}}
+Generated at: {{generatedAt}}
+Template version: {{templateVersion}}
+
+---
+
+## ADR-001: Technology Stack Selection
+
+**Status**: Accepted
+**Date**: {{generatedDate}}
+
+### Context
+
+This project requires a {{primaryDomain}} solution. The team evaluated available stack profiles and blueprints from the Agentic-Senior-Core governance repository.
+
+### Decision
+
+- **Language/Runtime**: {{stackDisplayName}} (source: `.agent-context/stacks/{{stackFileName}}`)
+- **Architecture blueprint**: {{blueprintDisplayName}} (source: `.agent-context/blueprints/{{blueprintFileName}}`)
+- **Database**: {{databaseChoice}}
+- **Auth**: {{authStrategy}}
+
+### Rationale
+
+The {{stackDisplayName}} stack was selected because:
+- It matches the project domain ({{primaryDomain}}).
+- The governance repository provides a verified blueprint for this stack.
+- The team has access to skill packs covering this technology.
+
+### Consequences
+
+- All code must follow the conventions in `.agent-context/stacks/{{stackFileName}}`.
+- Module boundaries must follow `.agent-context/blueprints/{{blueprintFileName}}`.
+- Database access must follow `.agent-context/rules/database-design.md`.
+- API contracts must follow `.agent-context/rules/api-docs.md`.
+
+---
+
+## ADR-002: Architecture Pattern
+
+**Status**: Accepted
+**Date**: {{generatedDate}}
+
+### Context
+
+The project needs a clear separation of concerns to remain maintainable as it grows.
+
+### Decision
+
+Follow the **Transport - Service - Repository** layered architecture as defined in `.agent-context/rules/architecture.md`.
+
+{{#if hasDatabase}}
+### Database Layer
+
+- Primary database: {{databaseChoice}}
+- ORM/query strategy: follow stack-specific conventions from the selected stack profile.
+- Migration strategy: safe, reversible migrations per `.agent-context/rules/database-design.md`.
+{{/if}}
+
+{{#if hasAuth}}
+### Authentication Layer
+
+- Strategy: {{authStrategy}}
+- Secrets management: no hardcoded secrets per `.agent-context/rules/security.md`.
+- Input validation: mandatory on all auth endpoints per `.agent-context/rules/security.md`.
+{{/if}}
+
+### Consequences
+
+- Every module must respect the three-layer separation.
+- Cross-layer imports are forbidden (no repository calls from transport layer).
+- Shared logic lives in a dedicated shared module, never in transport handlers.
+
+---
+
+## ADR-003: Project Structure
+
+**Status**: Accepted
+**Date**: {{generatedDate}}
+
+### Decision
+
+The project directory structure follows the selected blueprint (`{{blueprintDisplayName}}`). Key directories:
+
+```
+{{projectName}}/
+  src/
+    modules/          — feature modules (each with transport, service, repository)
+    shared/           — shared utilities, types, constants
+    config/           — environment and app configuration
+  docs/               — project documentation (this directory)
+  tests/              — test suites
+  .agent-context/     — governance rules and policies
+```
+
+### Consequences
+
+- New features are added as self-contained modules.
+- Shared code is extracted only when used by two or more modules.
+- Configuration is centralized and validated at startup.
+
+---
+
+Add new ADR entries below as architectural decisions are made during development.

package/lib/cli/templates/database-schema.md.id.tmpl

@@ -0,0 +1,74 @@
+# Skema Database: {{projectName}}
+
+Dibuat oleh Agentic-Senior-Core CLI v{{cliVersion}}
+Dibuat pada: {{generatedAt}}
+Versi template: {{templateVersion}}
+
+---
+
+## Teknologi Database
+
+**Tipe**: {{databaseChoice}}
+**Strategi autentikasi**: {{authStrategy}}
+
+## Prinsip Desain Skema
+
+Mengacu ke `.agent-context/rules/database-design.md`:
+- Gunakan Third Normal Form (3NF) sebagai default kecuali ada bukti performa untuk denormalisasi.
+- Gunakan migrasi aman dan reversible untuk setiap perubahan skema.
+- Jangan gunakan raw SQL tanpa parameterized query.
+- Tambahkan index berdasarkan pola query terukur, bukan asumsi.
+
+---
+
+## Tabel Inti
+
+{{#if hasAuth}}
+### users
+
+| Kolom | Tipe | Constraint | Catatan |
+|------|------|------------|---------|
+| id | UUID / BIGINT | PK, NOT NULL | Identifier utama |
+| email | VARCHAR(255) | UNIQUE, NOT NULL | Kredensial login |
+| password_hash | VARCHAR(255) | NOT NULL | Hash bcrypt/argon2 |
+| display_name | VARCHAR(100) | NOT NULL | Nama tampilan |
+| role | VARCHAR(50) | NOT NULL, DEFAULT 'user' | Role akses |
+| created_at | TIMESTAMP | NOT NULL, DEFAULT NOW() | Waktu buat |
+| updated_at | TIMESTAMP | NOT NULL, DEFAULT NOW() | Waktu ubah |
+
+{{/if}}
+### [Definisikan tabel domain Anda di sini]
+
+Berdasarkan fitur proyek:
+{{#each features}}
+- **{{this}}** - tentukan data apa yang perlu disimpan, dibaca, dan di-query.
+{{/each}}
+
+| Kolom | Tipe | Constraint | Catatan |
+|------|------|------------|---------|
+| id | UUID / BIGINT | PK, NOT NULL | Identifier utama |
+| ... | ... | ... | Definisikan sesuai kebutuhan fitur |
+| created_at | TIMESTAMP | NOT NULL, DEFAULT NOW() | Waktu buat |
+| updated_at | TIMESTAMP | NOT NULL, DEFAULT NOW() | Waktu ubah |
+
+---
+
+## Strategi Migrasi
+
+1. **Create**: buat file migrasi baru untuk setiap perubahan skema.
+2. **Test**: uji migrasi di lokal/staging sebelum produksi.
+3. **Rollback**: setiap migrasi wajib punya script down/rollback.
+4. **Review**: perubahan skema wajib review sesuai `.agent-context/review-checklists/pr-checklist.md`.
+
+## Index
+
+Tambahkan index berdasarkan pola query yang benar-benar muncul selama development:
+
+| Tabel | Kolom | Tipe | Alasan |
+|-------|-------|------|--------|
+| users | email | UNIQUE | Lookup login |
+| ... | ... | ... | Tambahkan saat pola query muncul |
+
+---
+
+Dokumen ini adalah referensi hidup. Perbarui saat model data berkembang.

package/lib/cli/templates/database-schema.md.tmpl

@@ -0,0 +1,74 @@
+# Database Schema: {{projectName}}
+
+Generated by Agentic-Senior-Core CLI v{{cliVersion}}
+Generated at: {{generatedAt}}
+Template version: {{templateVersion}}
+
+---
+
+## Database Technology
+
+**Type**: {{databaseChoice}}
+**Auth strategy**: {{authStrategy}}
+
+## Schema Design Principles
+
+Per `.agent-context/rules/database-design.md`:
+- Default to Third Normal Form (3NF) unless performance evidence justifies denormalization.
+- Use safe, reversible migrations for every schema change.
+- Never use raw SQL in application code without parameterized queries.
+- Add indexes based on measured query patterns, not assumptions.
+
+---
+
+## Core Tables
+
+{{#if hasAuth}}
+### users
+
+| Column | Type | Constraints | Notes |
+|--------|------|-------------|-------|
+| id | UUID / BIGINT | PK, NOT NULL | Primary identifier |
+| email | VARCHAR(255) | UNIQUE, NOT NULL | Login credential |
+| password_hash | VARCHAR(255) | NOT NULL | Hashed with bcrypt/argon2 |
+| display_name | VARCHAR(100) | NOT NULL | Public display name |
+| role | VARCHAR(50) | NOT NULL, DEFAULT 'user' | Role-based access |
+| created_at | TIMESTAMP | NOT NULL, DEFAULT NOW() | Record creation |
+| updated_at | TIMESTAMP | NOT NULL, DEFAULT NOW() | Last modification |
+
+{{/if}}
+### [Define your domain tables here]
+
+Based on the project features:
+{{#each features}}
+- **{{this}}** — consider what data this feature needs to store, read, and query.
+{{/each}}
+
+| Column | Type | Constraints | Notes |
+|--------|------|-------------|-------|
+| id | UUID / BIGINT | PK, NOT NULL | Primary identifier |
+| ... | ... | ... | Define based on feature requirements |
+| created_at | TIMESTAMP | NOT NULL, DEFAULT NOW() | Record creation |
+| updated_at | TIMESTAMP | NOT NULL, DEFAULT NOW() | Last modification |
+
+---
+
+## Migration Strategy
+
+1. **Create**: Write a new migration file for every schema change.
+2. **Test**: Run migration on a local/staging database before production.
+3. **Rollback**: Every migration must have a corresponding down/rollback script.
+4. **Review**: Schema changes require review per `.agent-context/review-checklists/pr-checklist.md`.
+
+## Indexes
+
+Add indexes based on actual query patterns observed during development:
+
+| Table | Column(s) | Type | Rationale |
+|-------|-----------|------|-----------|
+| users | email | UNIQUE | Login lookup |
+| ... | ... | ... | Add as query patterns emerge |
+
+---
+
+This document is a living reference. Update it as the data model evolves.

package/lib/cli/templates/flow-overview.md.id.tmpl

@@ -0,0 +1,118 @@
+# Ikhtisar Flow: {{projectName}}
+
+Dibuat oleh Agentic-Senior-Core CLI v{{cliVersion}}
+Dibuat pada: {{generatedAt}}
+Versi template: {{templateVersion}}
+
+---
+
+## Ikhtisar Sistem
+
+**Proyek**: {{projectName}}
+**Domain**: {{primaryDomain}}
+**Stack**: {{stackDisplayName}}
+**Blueprint**: {{blueprintDisplayName}}
+
+## Arsitektur Tingkat Tinggi
+
+```
++-------------+     +--------------+     +--------------+
+|   Client    |---->|  Transport   |---->|   Service    |
+| (Browser/   |<----|   Layer      |<----|    Layer     |
+| Mobile/CLI) |     | (Routes/     |     | (Business    |
+|             |     |  Handlers)   |     |  Logic)      |
++-------------+     +--------------+     +------+-------+
+                                                |
+                                         +------+-------+
+                                         |  Repository  |
+                                         |    Layer     |
+                                         | (Data Access)|
+                                         +------+-------+
+                                                |
+                                         +------+-------+
+                                         |   Database   |
+                                         | {{databaseChoice}} |
+                                         +--------------+
+```
+
+## Flow Request
+
+### Siklus Request Standar
+
+1. **Client** mengirim HTTP request (atau input CLI, atau event trigger).
+2. **Transport layer** menerima request, memvalidasi format input, lalu routing ke handler yang tepat.
+3. **Service layer** menerapkan business logic, orkestrasi operasi domain, dan enforcement aturan.
+4. **Repository layer** melakukan akses data (read/write ke database atau layanan eksternal).
+5. **Response** kembali dari Service ke Transport lalu ke Client.
+
+### Tanggung Jawab Layer
+
+| Layer | Melakukan | Tidak melakukan |
+|-------|-----------|-----------------|
+| Transport | Parse input, validasi shape, routing, format response | Business logic, akses database |
+| Service | Business rules, orkestrasi, validasi domain | Parse HTTP, format response, menjalankan SQL |
+| Repository | Akses data, query, caching | Business logic, validasi input |
+
+{{#if hasAuth}}
+## Flow Autentikasi
+
+```
++--------+     +-----------+     +-----------+     +-----------+
+| Client |---->|  Auth     |---->|  Token    |---->| Protected |
+|        |     | Endpoint  |     |  Verify   |     | Resource  |
+|        |<----|           |<----| ({{authStrategy}}) |<----|       |
++--------+     +-----------+     +-----------+     +-----------+
+```
+
+1. Client mengirim kredensial ke endpoint auth.
+2. Service memvalidasi kredensial terhadap data tersimpan.
+3. Jika sukses, service mengeluarkan token {{authStrategy}}.
+4. Client menyertakan token di request berikutnya.
+5. Middleware memverifikasi token sebelum request diteruskan ke handler terproteksi.
+
+{{/if}}
+## Flow Fitur
+
+Untuk setiap fitur kunci, definisikan flow data dan kontrol:
+
+{{#each features}}
+### {{this}}
+
+**Aktor**: [siapa yang memulai flow ini]
+**Trigger**: [apa yang memulai flow ini]
+**Langkah**:
+1. [Langkah 1]
+2. [Langkah 2]
+3. [Langkah 3]
+
+**Hasil sukses**: [apa yang terjadi saat flow selesai]
+**Penanganan error**: [apa yang terjadi jika gagal]
+
+---
+
+{{/each}}
+
+## Diagram Aliran Data
+
+```
+  Input Data                Proses                 Output
+  ----------              -----------             ----------
+                   +--------------------+
+  User Input ----->|   Validation       |
+                   |   (Transport)      |
+                   +---------+----------+
+                             |
+                   +---------v----------+
+                   |   Business Logic   |
+                   |   (Service)        |
+                   +---------+----------+
+                             |
+                   +---------v----------+
+                   |   Data Persist     |-------> Stored Data
+                   |   (Repository)     |
+                   +--------------------+
+```
+
+---
+
+Dokumen ini adalah referensi hidup. Perbarui flow saat fitur diimplementasikan dan disempurnakan.