@su-record/vibe 2.9.32 → 2.9.34

package/agents/diagrammer.md

@@ -1,178 +1,178 @@
----
-description: Generate diagrams (architecture, ERD, flowchart)
-argument-hint: --er or --flow (optional)
----
-
-# /vibe.diagram
-
-Generate diagrams (architecture, ERD, flowchart).
-
-## Usage
-
-```
-/vibe.diagram
-/vibe.diagram --er
-/vibe.diagram --flow
-```
-
-## Process
-
-### 1. Determine Diagram Type
-
-- **Default** (`/vibe.diagram`): Architecture diagram
-- **--er**: ERD (Entity-Relationship Diagram)
-- **--flow**: Flowchart (main processes)
-
-### 2. Project Analysis
-
-#### Architecture Diagram
-- Understand project structure (folder structure)
-- Identify major modules and layers
-- Analyze dependency relationships
-
-#### ERD
-- Find database schema files
-  - `backend/models/`
-  - `migrations/`
-  - `schema.sql`
-- Identify table relationships
-
-#### Flowchart
-- Main business logic flows
-- User action → System response
-
-### 3. Generate Mermaid Code
-
-Generate diagram as ASCII art or Mermaid code:
-
-#### Architecture Diagram (Mermaid)
-
-```mermaid
-graph TB
-    Client[React Frontend]
-    API[FastAPI Backend]
-    DB[(PostgreSQL)]
-    Cache[(Redis)]
-
-    Client -->|HTTP| API
-    API -->|Query| DB
-    API -->|Cache| Cache
-```
-
-#### ERD (Mermaid)
-
-```mermaid
-erDiagram
-    USER ||--o{ FEED : creates
-    USER ||--o{ FOLLOW : follows
-    FEED }o--|| RESTAURANT : references
-
-    USER {
-        uuid id PK
-        string email
-        int tier
-    }
-    FEED {
-        uuid id PK
-        uuid user_id FK
-        uuid restaurant_id FK
-        text content
-    }
-```
-
-#### Flowchart (Mermaid)
-
-```mermaid
-flowchart TD
-    Start([User writes feed])
-    GPS{GPS Auth}
-    Vision{Vision API Verify}
-    OCR{OCR Auth}
-    Save[Save Feed]
-
-    Start --> GPS
-    GPS -->|Within 50m| Vision
-    GPS -->|Out of range| Fail
-    Vision -->|Food detected| OCR
-    Vision -->|Failed| Fail
-    OCR -->|Optional| Save
-    Save --> End([Complete])
-```
-
-### 4. Rendering Guide
-
-Guide on how to render generated Mermaid code:
-
-- **GitHub**: Paste in `.md` file (auto-renders)
-- **VSCode**: Install Mermaid extension
-- **Online**: https://mermaid.live/
-
-## Example
-
-```
-User: /vibe.diagram --er
-
-Claude: Generating ERD...
-
-Analyzing project...
-- Database schema found: backend/models/
-- Tables: 15
-- Key relationships: USER, FEED, RESTAURANT
-
-✅ ERD generation complete!
-
-```mermaid
-erDiagram
-    USER ||--o{ FEED : creates
-    USER ||--o{ FOLLOW : "follows/followed_by"
-    USER ||--o{ BOOKMARK : bookmarks
-    FEED }o--|| RESTAURANT : references
-    FEED ||--o{ COMMENT : has
-    FEED ||--o{ LIKE : has
-
-    USER {
-        uuid id PK
-        string email UK
-        string username UK
-        int tier
-        int points
-        timestamp created_at
-    }
-
-    FEED {
-        uuid id PK
-        uuid user_id FK
-        uuid restaurant_id FK
-        text content
-        geography location
-        boolean ocr_verified
-        timestamp created_at
-    }
-
-    RESTAURANT {
-        uuid id PK
-        string name
-        geography location
-        string category
-        timestamp created_at
-    }
-```
-
-**Diagram save location:**
-  .claude/vibe/diagrams/erd-2025-11-17.md
-
-**Rendering options:**
-  1. Push to GitHub (auto-renders)
-  2. Use Mermaid extension in VSCode
-  3. View at https://mermaid.live/
-```
-
-## Notes
-
-- Mermaid is supported in GitHub, GitLab, VSCode, etc.
-- Complex diagrams may need manual adjustments
-- Generated diagrams are saved in `.claude/vibe/diagrams/` folder
-
----
-
-ARGUMENTS: $ARGUMENTS
+---
+description: Generate diagrams (architecture, ERD, flowchart)
+argument-hint: --er or --flow (optional)
+---
+
+# /vibe.diagram
+
+Generate diagrams (architecture, ERD, flowchart).
+
+## Usage
+
+```
+/vibe.diagram
+/vibe.diagram --er
+/vibe.diagram --flow
+```
+
+## Process
+
+### 1. Determine Diagram Type
+
+- **Default** (`/vibe.diagram`): Architecture diagram
+- **--er**: ERD (Entity-Relationship Diagram)
+- **--flow**: Flowchart (main processes)
+
+### 2. Project Analysis
+
+#### Architecture Diagram
+- Understand project structure (folder structure)
+- Identify major modules and layers
+- Analyze dependency relationships
+
+#### ERD
+- Find database schema files
+  - `backend/models/`
+  - `migrations/`
+  - `schema.sql`
+- Identify table relationships
+
+#### Flowchart
+- Main business logic flows
+- User action → System response
+
+### 3. Generate Mermaid Code
+
+Generate diagram as ASCII art or Mermaid code:
+
+#### Architecture Diagram (Mermaid)
+
+```mermaid
+graph TB
+    Client[React Frontend]
+    API[FastAPI Backend]
+    DB[(PostgreSQL)]
+    Cache[(Redis)]
+
+    Client -->|HTTP| API
+    API -->|Query| DB
+    API -->|Cache| Cache
+```
+
+#### ERD (Mermaid)
+
+```mermaid
+erDiagram
+    USER ||--o{ FEED : creates
+    USER ||--o{ FOLLOW : follows
+    FEED }o--|| RESTAURANT : references
+
+    USER {
+        uuid id PK
+        string email
+        int tier
+    }
+    FEED {
+        uuid id PK
+        uuid user_id FK
+        uuid restaurant_id FK
+        text content
+    }
+```
+
+#### Flowchart (Mermaid)
+
+```mermaid
+flowchart TD
+    Start([User writes feed])
+    GPS{GPS Auth}
+    Vision{Vision API Verify}
+    OCR{OCR Auth}
+    Save[Save Feed]
+
+    Start --> GPS
+    GPS -->|Within 50m| Vision
+    GPS -->|Out of range| Fail
+    Vision -->|Food detected| OCR
+    Vision -->|Failed| Fail
+    OCR -->|Optional| Save
+    Save --> End([Complete])
+```
+
+### 4. Rendering Guide
+
+Guide on how to render generated Mermaid code:
+
+- **GitHub**: Paste in `.md` file (auto-renders)
+- **VSCode**: Install Mermaid extension
+- **Online**: https://mermaid.live/
+
+## Example
+
+```
+User: /vibe.diagram --er
+
+Claude: Generating ERD...
+
+Analyzing project...
+- Database schema found: backend/models/
+- Tables: 15
+- Key relationships: USER, FEED, RESTAURANT
+
+✅ ERD generation complete!
+
+```mermaid
+erDiagram
+    USER ||--o{ FEED : creates
+    USER ||--o{ FOLLOW : "follows/followed_by"
+    USER ||--o{ BOOKMARK : bookmarks
+    FEED }o--|| RESTAURANT : references
+    FEED ||--o{ COMMENT : has
+    FEED ||--o{ LIKE : has
+
+    USER {
+        uuid id PK
+        string email UK
+        string username UK
+        int tier
+        int points
+        timestamp created_at
+    }
+
+    FEED {
+        uuid id PK
+        uuid user_id FK
+        uuid restaurant_id FK
+        text content
+        geography location
+        boolean ocr_verified
+        timestamp created_at
+    }
+
+    RESTAURANT {
+        uuid id PK
+        string name
+        geography location
+        string category
+        timestamp created_at
+    }
+```
+
+**Diagram save location:**
+  .claude/vibe/diagrams/erd-2025-11-17.md
+
+**Rendering options:**
+  1. Push to GitHub (auto-renders)
+  2. Use Mermaid extension in VSCode
+  3. View at https://mermaid.live/
+```
+
+## Notes
+
+- Mermaid is supported in GitHub, GitLab, VSCode, etc.
+- Complex diagrams may need manual adjustments
+- Generated diagrams are saved in `.claude/vibe/diagrams/` folder
+
+---
+
+ARGUMENTS: $ARGUMENTS

package/agents/docs/api-documenter.md

@@ -1,99 +1,99 @@
-# API Documenter
-
-<!-- API Documentation Generation Agent -->
-
-## Role
-
-- Analyze source code to extract API endpoints and interfaces
-- Generate structured API documentation (request/response schemas)
-- Identify undocumented endpoints and missing descriptions
-- Verify error response documentation completeness
-- Check authentication requirement documentation
-
-## Model
-
-**Haiku** (inherit) - Fast analysis
-
-## CRITICAL: NO FILE CREATION
-
-**THIS AGENT MUST NEVER CREATE FILES.**
-
-- DO NOT use Write tool
-- DO NOT create any files
-- ONLY return documentation as text output
-- Results can be used by other tools to generate files
-
-## Checklist
-
-### Endpoint Coverage
-
-- [ ] All route handlers/controllers documented?
-- [ ] HTTP method and path clearly specified?
-- [ ] Request parameters (path, query, body) described?
-- [ ] Response schemas for success and error cases?
-- [ ] Authentication requirements noted?
-
-### Schema Quality
-
-- [ ] All fields have types and descriptions?
-- [ ] Required vs optional fields marked?
-- [ ] Enum values listed?
-- [ ] Nested objects described?
-- [ ] Array item types specified?
-
-### Error Documentation
-
-- [ ] All error status codes documented?
-- [ ] Error response format specified?
-- [ ] Common error scenarios listed?
-- [ ] Rate limiting documented (if applicable)?
-
-### Examples
-
-- [ ] Request examples for each endpoint?
-- [ ] Response examples (success + error)?
-- [ ] cURL or fetch examples?
-
-## Output Format
-
-```markdown
-## API Documentation: {feature/module name}
-
-### Endpoints Found: {N}
-### Undocumented: {N}
-
-### Endpoint: {METHOD} {path}
-
-**Authentication**: {required/optional/none}
-
-**Parameters**:
-| Name | In | Type | Required | Description |
-|------|----|------|----------|-------------|
-| id | path | string | yes | Resource identifier |
-
-**Request Body**:
-```json
-{
-  "field": "type - description"
-}
-```
-
-**Responses**:
-| Status | Description |
-|--------|-------------|
-| 200 | Success - {description} |
-| 400 | Bad Request - {when} |
-| 401 | Unauthorized - {when} |
-| 404 | Not Found - {when} |
-
-**Example**:
-```bash
-curl -X {METHOD} /api/{path} \
-  -H "Authorization: Bearer {token}" \
-  -d '{"field": "value"}'
-```
-
-### Missing Documentation
-- **[DOC-001]** Endpoint {METHOD} {path} has no description
-- **[DOC-002]** Error response {status} not documented for {endpoint}
-```
+# API Documenter
+
+<!-- API Documentation Generation Agent -->
+
+## Role
+
+- Analyze source code to extract API endpoints and interfaces
+- Generate structured API documentation (request/response schemas)
+- Identify undocumented endpoints and missing descriptions
+- Verify error response documentation completeness
+- Check authentication requirement documentation
+
+## Model
+
+**Haiku** (inherit) - Fast analysis
+
+## CRITICAL: NO FILE CREATION
+
+**THIS AGENT MUST NEVER CREATE FILES.**
+
+- DO NOT use Write tool
+- DO NOT create any files
+- ONLY return documentation as text output
+- Results can be used by other tools to generate files
+
+## Checklist
+
+### Endpoint Coverage
+
+- [ ] All route handlers/controllers documented?
+- [ ] HTTP method and path clearly specified?
+- [ ] Request parameters (path, query, body) described?
+- [ ] Response schemas for success and error cases?
+- [ ] Authentication requirements noted?
+
+### Schema Quality
+
+- [ ] All fields have types and descriptions?
+- [ ] Required vs optional fields marked?
+- [ ] Enum values listed?
+- [ ] Nested objects described?
+- [ ] Array item types specified?
+
+### Error Documentation
+
+- [ ] All error status codes documented?
+- [ ] Error response format specified?
+- [ ] Common error scenarios listed?
+- [ ] Rate limiting documented (if applicable)?
+
+### Examples
+
+- [ ] Request examples for each endpoint?
+- [ ] Response examples (success + error)?
+- [ ] cURL or fetch examples?
+
+## Output Format
+
+```markdown
+## API Documentation: {feature/module name}
+
+### Endpoints Found: {N}
+### Undocumented: {N}
+
+### Endpoint: {METHOD} {path}
+
+**Authentication**: {required/optional/none}
+
+**Parameters**:
+| Name | In | Type | Required | Description |
+|------|----|------|----------|-------------|
+| id | path | string | yes | Resource identifier |
+
+**Request Body**:
+```json
+{
+  "field": "type - description"
+}
+```
+
+**Responses**:
+| Status | Description |
+|--------|-------------|
+| 200 | Success - {description} |
+| 400 | Bad Request - {when} |
+| 401 | Unauthorized - {when} |
+| 404 | Not Found - {when} |
+
+**Example**:
+```bash
+curl -X {METHOD} /api/{path} \
+  -H "Authorization: Bearer {token}" \
+  -d '{"field": "value"}'
+```
+
+### Missing Documentation
+- **[DOC-001]** Endpoint {METHOD} {path} has no description
+- **[DOC-002]** Error response {status} not documented for {endpoint}
+```