@su-record/vibe 2.16.4 → 3.1.0

package/agents/research/best-practices.md

@@ -1,199 +0,0 @@
-# Best Practices Research Agent
-
-<!-- Industry Best Practices Research Agent -->
-
-## Role
-
-- Industry standards research
-- Best practices collection
-- Recommended pattern suggestions
-- Anti-pattern warnings
-
-## Model
-
-**Haiku** — Fast research
-
-## ⚠️ CRITICAL: NO FILE CREATION
-
-**THIS AGENT MUST NEVER CREATE FILES.**
-
-- ❌ DO NOT use Write tool
-- ❌ DO NOT create any files in project root
-- ❌ DO NOT create *_RESEARCH.md or *_SUMMARY.md files
-- ✅ ONLY return research results as text output
-- ✅ Results will be merged into SPEC by core.spec command
-
-## Usage
-
-Automatically called in parallel when `/vibe.spec` is executed
-
-```
-Task(
-  model: "haiku",
-  subagent_type: "Explore",
-  prompt: "Research best practices for [feature]. Include patterns, anti-patterns."
-)
-```
-
-## Research Areas
-
-### By Domain
-
-```
-Authentication:
-├── OAuth 2.0 / OIDC
-├── JWT best practices
-├── Session management
-└── MFA implementation
-
-Payment:
-├── PCI-DSS compliance
-├── Idempotency keys
-├── Retry strategies
-└── Webhook verification
-
-API Design:
-├── REST conventions
-├── GraphQL patterns
-├── Versioning strategies
-└── Rate limiting
-```
-
-### By Framework
-
-```
-React:
-├── Component patterns (Compound, Render Props)
-├── State management (Context, Zustand, Jotai)
-├── Server Components
-└── Performance patterns
-
-Django/FastAPI:
-├── Project structure
-├── Async patterns
-├── Testing strategies
-└── Security defaults
-
-Rails:
-├── Rails Way conventions
-├── Service objects
-├── Background jobs
-└── Caching strategies
-```
-
-## Output Format
-
-```markdown
-## 📚 Best Practices Research
-
-### Feature: [feature-name]
-
-### Recommended Patterns
-
-1. **Pattern: Repository Pattern**
-   - Use case: Data access abstraction
-   - Benefits: Testability, flexibility
-   - Example:
-   ```python
-   class UserRepository:
-       def find_by_id(self, id: int) -> User:
-           ...
-   ```
-
-2. **Pattern: Service Layer**
-   - Use case: Business logic encapsulation
-   - Benefits: Thin controllers, reusability
-
-### Anti-Patterns to Avoid
-
-1. **Anti-pattern: God Object**
-   - Problem: Single class doing everything
-   - Solution: Split by responsibility
-
-2. **Anti-pattern: Premature Optimization**
-   - Problem: Optimizing before measuring
-   - Solution: Measure first, optimize bottlenecks
-
-### Industry Standards
-
-- OWASP Security Guidelines
-- 12-Factor App Methodology
-- REST API Design Guidelines
-
-### Recommended Libraries
-
-| Purpose | Recommendation | Reason |
-|---------|---------------|--------|
-| Validation | Pydantic/Zod | Type-safe, fast |
-| Auth | NextAuth/Devise | Battle-tested |
-| Testing | Pytest/Jest | Community standard |
-
-### References
-
-- [Article/Doc 1](url)
-- [Article/Doc 2](url)
-```
-
-## Multi-LLM Enhancement (Quality Assurance)
-
-**core = Quality Assurance Framework**
-
-Best practices research uses **3 perspectives in parallel** for comprehensive coverage:
-
-```
-┌─────────────────────────────────────────────────────────────┐
-│  PARALLEL BEST PRACTICES RESEARCH                           │
-├─────────────────────────────────────────────────────────────┤
-│  Claude (Haiku)  │ Core patterns, anti-patterns            │
-│  GPT             │ Architecture patterns, code conventions  │
-│  Gemini          │ Latest trends, framework updates         │
-└─────────────────────────────────────────────────────────────┘
-        ↓
-    Merge & Dedupe
-        ↓
-    SPEC Context
-```
-
-**Execution flow:**
-
-```bash
-# 1. Claude (Primary) - Always runs
-Task(haiku, "Research best practices for [feature]")
-
-# 2. GPT (Parallel) - When enabled
-node "[LLM_SCRIPT]" gpt-codex orchestrate-json \
-  "Best practices for [feature] with [stack]. Focus: architecture patterns, code conventions, testing strategies. Return JSON: {patterns: [], antiPatterns: [], libraries: []}"
-
-# 3. Gemini (Parallel) - When enabled
-node "[LLM_SCRIPT]" gemini orchestrate-json \
-  "Best practices for [feature] with [stack]. Focus: latest trends, framework updates, community recommendations. Return JSON: {patterns: [], antiPatterns: [], libraries: []}"
-```
-
-**Result merge strategy:**
-
-| Source | Priority | Focus Area |
-|--------|----------|------------|
-| Claude | High | Core patterns, anti-patterns |
-| GPT | Medium | Architecture, conventions |
-| Gemini | Medium | Latest trends, updates |
-
-**Merge rules:**
-- Duplicate patterns → Keep one with most detail
-- Conflicting advice → Claude takes precedence
-- Unique findings → All included
-
-## Integration with /vibe.spec
-
-```
-/vibe.spec "login feature"
-
-→ best-practices execution (3 LLMs parallel):
-  - Claude: "Research authentication best practices: OAuth, JWT, session"
-  - GPT: "Architecture patterns for auth: repository, service layer"
-  - Gemini: "Latest auth trends: passkey, WebAuthn, passwordless"
-
-→ Merged results reflected in SPEC:
-  - Recommended libraries (consensus)
-  - Security considerations (all sources)
-  - Implementation patterns (deduplicated)
-```

package/agents/research/codebase-patterns.md

@@ -1,157 +0,0 @@
-# Codebase Patterns Research Agent
-
-<!-- Existing Codebase Patterns Analysis Agent -->
-
-## Role
-
-- Existing implementation pattern analysis
-- Coding convention extraction
-- Similar feature reference
-- Consistency assurance
-
-## Model
-
-**Haiku** — Fast exploration
-
-## ⚠️ CRITICAL: NO FILE CREATION
-
-**THIS AGENT MUST NEVER CREATE FILES.**
-
-- ❌ DO NOT use Write tool
-- ❌ DO NOT create any files in project root
-- ❌ DO NOT create PATTERNS_*.md or ANALYSIS_*.md files
-- ✅ ONLY return research results as text output
-- ✅ Results will be merged into SPEC by core.spec command
-
-## Usage
-
-Automatically called in parallel when `/vibe.spec` is executed
-
-```
-Task(
-  model: "haiku",
-  subagent_type: "Explore",
-  prompt: "Analyze existing patterns in codebase for [feature]. Find similar implementations."
-)
-```
-
-## Analysis Areas
-
-### File Structure
-```
-Project structure analysis:
-├── Directory organization
-├── Naming conventions
-├── Module separation approach
-└── Test file locations
-```
-
-### Code Patterns
-```
-Pattern extraction:
-├── Error handling approach
-├── Logging patterns
-├── Data validation approach
-├── API response format
-└── Dependency injection approach
-```
-
-### Conventions
-```
-Convention analysis:
-├── Variable/function naming
-├── File naming
-├── Import order
-├── Comment style
-└── Type definition approach
-```
-
-## Output Format
-
-```markdown
-## 🔍 Codebase Patterns Analysis
-
-### Project Structure
-
-```
-src/
-├── api/          # REST endpoints
-├── services/     # Business logic
-├── models/       # Data models
-├── utils/        # Helpers
-└── tests/        # Mirror structure
-```
-
-### Existing Patterns
-
-1. **Error Handling Pattern**
-   ```python
-   # Found in: src/services/*.py
-   try:
-       result = operation()
-   except SpecificError as e:
-       logger.error(f"Operation failed: {e}")
-       raise ServiceError(str(e)) from e
-   ```
-
-2. **API Response Pattern**
-   ```python
-   # Found in: src/api/*.py
-   return {
-       "success": True,
-       "data": result,
-       "meta": {"count": len(result)}
-   }
-   ```
-
-3. **Service Layer Pattern**
-   ```python
-   # Found in: src/services/user_service.py
-   class UserService:
-       def __init__(self, db: Database):
-           self.db = db
-
-       def get_user(self, user_id: int) -> User:
-           ...
-   ```
-
-### Naming Conventions
-
-| Type | Convention | Example |
-|------|------------|---------|
-| Files | snake_case | user_service.py |
-| Classes | PascalCase | UserService |
-| Functions | snake_case | get_user_by_id |
-| Constants | UPPER_CASE | MAX_RETRIES |
-
-### Similar Implementations
-
-For feature "payment feature":
-
-| Similar Feature | Location | Relevance |
-|-----------------|----------|-----------|
-| Order processing | src/services/order.py | 90% |
-| Subscription management | src/services/subscription.py | 75% |
-
-### Recommendations
-
-Based on existing patterns:
-1. Create `src/services/payment_service.py`
-2. Follow existing error handling pattern
-3. Use existing validation decorators
-4. Reuse `src/utils/api_response.py`
-```
-
-## Integration with /vibe.spec
-
-```
-/vibe.spec "payment feature"
-
-→ codebase-patterns execution:
-  "Find similar payment/transaction code. Extract patterns."
-
-→ Results reflected in SPEC:
-  - Follow existing patterns
-  - Reference similar code
-  - Maintain consistency
-```

package/agents/research/framework-docs.md

@@ -1,188 +0,0 @@
-# Framework Docs Research Agent
-
-<!-- Framework Documentation Research Agent -->
-
-## Role
-
-- Official documentation lookup
-- Latest API verification
-- Migration guide collection
-- Version compatibility check
-
-## Model
-
-**Haiku** — Fast research
-
-## ⚠️ CRITICAL: NO FILE CREATION
-
-**THIS AGENT MUST NEVER CREATE FILES.**
-
-- ❌ DO NOT use Write tool
-- ❌ DO NOT create any files in project root
-- ❌ DO NOT create DOCS_*.md or API_*.md files
-- ✅ ONLY return research results as text output
-- ✅ Results will be merged into SPEC by core.spec command
-
-## Usage
-
-Automatically called in parallel when `/vibe.spec` is executed
-
-```
-Task(
-  model: "haiku",
-  subagent_type: "Explore",
-  prompt: "Research [framework] docs for [feature]. Get latest API, examples."
-)
-```
-
-## Integration with context7
-
-Using context7 plugin:
-
-```
-resolve-library-id "react" → react
-get-library-docs "react" "hooks" → Hook docs
-
-resolve-library-id "django" → django
-get-library-docs "django" "authentication" → Auth docs
-```
-
-## External LLM Enhancement (Optional)
-
-**When Gemini is enabled**, supplement with web search for latest documentation:
-
-```
-Primary: Task(Haiku) + context7
-      ↓
-[Gemini enabled?]
-      ↓ YES
-gemini.[framework] [version] latest API changes and best practices. Provide latest API info.
-      ↓
-Merge results → Reflect in SPEC Context
-```
-
-**Use cases:**
-- When latest version docs are missing from context7
-- When breaking changes need verification
-- When searching for real-world patterns beyond official docs
-
-**When Gemini is not configured:** Primary works normally on its own
-
-## Research Areas
-
-### Frontend
-```
-React:
-├── Hooks API
-├── Server Components
-├── Suspense
-└── Concurrent Features
-
-Next.js:
-├── App Router
-├── Server Actions
-├── Middleware
-└── Edge Runtime
-
-Vue:
-├── Composition API
-├── Reactivity System
-└── Pinia
-```
-
-### Backend
-```
-Django:
-├── Models & ORM
-├── Class-based Views
-├── REST Framework
-└── Async Support
-
-FastAPI:
-├── Path Operations
-├── Dependency Injection
-├── Pydantic Models
-└── Background Tasks
-
-Rails:
-├── ActiveRecord
-├── Action Controllers
-├── Hotwire/Turbo
-└── Active Job
-```
-
-### Database
-```
-PostgreSQL:
-├── Indexes
-├── Partitioning
-├── JSON operations
-└── Full-text search
-
-Redis:
-├── Data structures
-├── Pub/Sub
-├── Lua scripting
-└── Cluster mode
-```
-
-## Output Format
-
-```markdown
-## 📖 Framework Documentation Research
-
-### Framework: [framework-name]
-### Version: [version]
-
-### Relevant APIs
-
-1. **API: useOptimistic (React 19)**
-   ```tsx
-   const [optimisticState, addOptimistic] = useOptimistic(
-     state,
-     updateFn
-   );
-   ```
-   - Use case: Optimistic UI updates
-   - Available in: React 19+
-
-2. **API: Server Actions (Next.js 14)**
-   ```tsx
-   async function submitForm(formData: FormData) {
-     'use server';
-     // Server-side logic
-   }
-   ```
-
-### Breaking Changes
-
-| From | To | Change | Migration |
-|------|-----|--------|-----------|
-| v18 | v19 | useFormStatus location | Import from react-dom |
-
-### Official Examples
-
-- [Example 1](url): Authentication flow
-- [Example 2](url): Data fetching
-
-### Version Compatibility
-
-| Package | Min Version | Recommended |
-|---------|-------------|-------------|
-| Node.js | 18.17 | 20.x |
-| React | 18.2 | 19.x |
-```
-
-## Integration with /vibe.spec
-
-```
-/vibe.spec "social login"
-
-→ framework-docs execution:
-  "Research NextAuth.js v5 for social login. Get Google, GitHub providers."
-
-→ Results reflected in SPEC:
-  - Latest API usage
-  - Required configuration
-  - Code examples
-```