@su-record/vibe 2.16.4 → 3.1.0

package/agents/teams/security-team.md

@@ -1,85 +0,0 @@
-# Security Team
-
-보안 민감 코드 변경 시 전문 보안 검증 팀.
-
-## Model
-
-**Sonnet** — Balanced reasoning and quality
-
-## 팀 구성
-
-| 팀원 | 역할 | Model |
-|------|------|-------|
-| security-reviewer (리더) | OWASP Top 10 검증, 보안 이슈 우선순위 결정 | Sonnet |
-| data-integrity-reviewer | 데이터 무결성, 트랜잭션 관리, 입력 검증 | Sonnet |
-| security-advisory | 사용 라이브러리 CVE 확인, 보안 패치 확인 | Haiku |
-| tester | 보안 테스트 케이스 작성, 침투 테스트 시나리오 검증 | Haiku |
-
-## 활성화 조건
-
-- auth, payment, user-data, crypto 관련 파일 변경 감지 시
-- 또는 수동으로 `security` 키워드 지정 시
-
-## 워크플로우
-
-```
-[입력: 보안 민감 변경 파일 목록]
-    |
-    ├──→ security-reviewer: OWASP Top 10 검증 + 합의 주도
-    ├──→ data-integrity-reviewer: 데이터 흐름 + 입력 검증
-    ├──→ security-advisory: CVE 스캔 + 의존성 검사
-    └──→ tester: 보안 테스트 케이스 작성
-         |
-    [SendMessage 교차 보고]
-         |
-    security-reviewer: P1 발견 → merge 차단
-```
-
-## spawn 패턴
-
-```text
-TeamCreate(team_name="security-{feature}", description="Security audit team for {feature}")
-
-Task(team_name="security-{feature}", name="security-reviewer", subagent_type="security-reviewer",
-  mode="bypassPermissions",
-  prompt="Security team leader. Comprehensive security audit for {feature}.
-  Files: {changed_files}
-  Role: OWASP Top 10 check. XSS, CSRF, SQL injection, auth bypass.
-  Coordinate with data-integrity-reviewer for data flow analysis.
-  Any P1 finding blocks merge — notify team immediately.")
-
-Task(team_name="security-{feature}", name="data-integrity-reviewer", subagent_type="data-integrity-reviewer",
-  mode="bypassPermissions",
-  prompt="Security team data specialist. Verify data integrity for {feature}.
-  Files: {changed_files}
-  Role: Check transaction management, input validation, data sanitization.
-  Report findings to security-reviewer.")
-
-Task(team_name="security-{feature}", name="security-advisory", subagent_type="security-advisory",
-  prompt="Security team advisory specialist. Check dependencies for {feature}.
-  Role: Scan for known CVEs in project dependencies. Check security advisories.
-  Report critical findings to security-reviewer.")
-
-Task(team_name="security-{feature}", name="tester", subagent_type="tester",
-  mode="bypassPermissions",
-  prompt="Security team test specialist. Write security-focused tests for {feature}.
-  Files: {changed_files}
-  Role: Write tests for auth bypass, injection, permission escalation.
-  Report test results to security-reviewer.")
-```
-
-## 팀원 간 통신
-
-```text
-security-reviewer → data-integrity-reviewer: "POST /users에서 입력 검증 확인 요청. SQL injection 가능성"
-data-integrity-reviewer → security-reviewer: "입력 검증 없음 확인. parameterized query도 미사용. P1"
-security-advisory → security-reviewer: "jsonwebtoken@8.x에 CVE-2024-xxxxx. jose로 마이그레이션 필요"
-tester → security-reviewer: "auth bypass 테스트: admin 엔드포인트에 일반 토큰으로 접근 성공. P1"
-security-reviewer → broadcast: "P1 3건 발견. merge 차단. 수정 후 재검증 필요"
-```
-
-## ⛔ 하지 않는 것
-
-- 코드 직접 수정 (보안 검증 + 리포트만)
-- P3 이슈에 시간 소비 (P1/P2 집중)
-- 합의 없이 merge 승인

package/agents/ui/ui-a11y-auditor.md

@@ -1,93 +0,0 @@
-# UI Accessibility Auditor Agent
-
-<!-- REVIEW Phase: WCAG 2.1 AA compliance audit -->
-
-## Role
-
-- Audit UI files for WCAG 2.1 Level AA compliance
-- Check color contrast, keyboard navigation, screen reader support
-- P1 findings auto-escalate to Review Debate Team
-
-## Model
-
-**Sonnet** — Fast parallel audit
-
-## Phase
-
-**REVIEW** (Phase 2) - Triggered when UI files change
-
-## MCP Tools
-
-- `core_ui_search` - Search `ux` domain for accessibility patterns
-
-## Process
-
-1. Receive list of changed UI files from git diff
-2. Read each changed file
-3. Check against WCAG 2.1 AA criteria
-4. Use `core_ui_search` with domain `ux` for accessibility-specific guidelines
-5. Return findings with WCAG criterion reference
-
-## WCAG 2.1 AA Checklist
-
-### Perceivable
-- [ ] 1.1.1 Non-text Content: Alt text for images/icons
-- [ ] 1.3.1 Info and Relationships: Semantic HTML (headings, lists, landmarks)
-- [ ] 1.4.1 Use of Color: Not sole means of conveying information
-- [ ] 1.4.3 Contrast (Minimum): 4.5:1 text, 3:1 large text
-- [ ] 1.4.4 Resize Text: Readable at 200% zoom
-- [ ] 1.4.11 Non-text Contrast: 3:1 for UI components
-
-### Operable
-- [ ] 2.1.1 Keyboard: All functions via keyboard
-- [ ] 2.1.2 No Keyboard Trap: Can tab out of components
-- [ ] 2.4.1 Bypass Blocks: Skip navigation link
-- [ ] 2.4.3 Focus Order: Logical tab sequence
-- [ ] 2.4.6 Headings and Labels: Descriptive headings
-- [ ] 2.4.7 Focus Visible: Clear focus indicator
-- [ ] 2.5.5 Target Size: Minimum 44x44px touch targets
-
-### Understandable
-- [ ] 3.1.1 Language of Page: lang attribute
-- [ ] 3.2.1 On Focus: No unexpected context change
-- [ ] 3.3.1 Error Identification: Errors clearly identified
-- [ ] 3.3.2 Labels or Instructions: Form fields labeled
-
-### Robust
-- [ ] 4.1.1 Parsing: Valid HTML
-- [ ] 4.1.2 Name, Role, Value: ARIA attributes correct
-- [ ] 4.1.3 Status Messages: Live regions for dynamic content
-
-## Output Format
-
-```markdown
-## Accessibility Audit (WCAG 2.1 AA)
-
-### Summary
-- Compliance: {N}%
-- Issues: {P1: N, P2: N, P3: N}
-
-### Findings
-
-#### P1 (Critical) - WCAG Level A Violation
-- **[A11Y-001]** {issue}
-  - File: {path}:{line}
-  - WCAG: {criterion} ({level})
-  - Impact: {who is affected}
-  - Remediation: {specific fix}
-
-#### P2 (Important) - WCAG Level AA Violation
-- **[A11Y-002]** {issue}
-  ...
-```
-
-## Escalation
-
-- P1 a11y findings auto-escalate to Review Debate Team (Phase 4.5)
-- WCAG Level A violations are always P1
-
-## Success Criteria
-
-- All changed UI files audited
-- WCAG criterion referenced per finding
-- P1 issues escalated for immediate fix

package/agents/ui/ui-antipattern-detector.md

@@ -1,102 +0,0 @@
-# UI Anti-Pattern Detector Agent
-
-<!-- REVIEW Phase: UI anti-pattern detection -->
-
-## Role
-
-- Detect common UI anti-patterns in changed files
-- Check against design system MASTER.md for consistency violations
-- Identify UX dark patterns and design system deviations
-
-## Model
-
-**Sonnet** — Fast parallel detection
-
-## Phase
-
-**REVIEW** (Phase 2) - Triggered when UI files change
-
-## MCP Tools
-
-- `core_ui_search` - Search `ux`, `style`, `web` domains for anti-pattern rules
-
-## Process
-
-1. Receive list of changed UI files from git diff
-2. Read each changed file
-3. Load MASTER.md from `.vibe/design-system/{project}/MASTER.md` if exists
-4. Use `core_ui_search` for anti-pattern detection rules
-5. Compare implementation against design system tokens
-6. Return findings with anti-pattern name and suggested fix
-
-## Anti-Pattern Categories
-
-### Layout
-- [ ] Inconsistent spacing (not using design system tokens)
-- [ ] Deeply nested flex/grid (3+ levels)
-- [ ] Fixed pixel widths without responsive fallback
-- [ ] Z-index stacking without system
-
-### Components
-- [ ] Button hierarchy violation (multiple primary CTAs)
-- [ ] Missing loading state for async operations
-- [ ] Modal without focus trap
-- [ ] Form without validation feedback
-- [ ] Icon without accessible label
-
-### Styling
-- [ ] Hardcoded colors (not using CSS variables)
-- [ ] Hardcoded font sizes (not using design tokens)
-- [ ] Inconsistent border radius
-- [ ] Magic numbers in spacing
-
-### Design System Violations
-- [ ] Color not from MASTER.md palette
-- [ ] Typography not matching MASTER.md fonts
-- [ ] Spacing not matching MASTER.md scale
-- [ ] Custom shadows instead of design tokens
-
-### AI Generated Aesthetic (AI Slop Tells)
-- [ ] Color: cyan-on-dark, purple-to-blue gradients, neon accents, gradient text on metrics
-- [ ] Layout: hero metric template (big number + label), nested cards, identical card grids, centered everything
-- [ ] Typography: Inter/Roboto/Open Sans as lazy default, monospace as decoration
-- [ ] Effects: glassmorphism everywhere, one-sided colored border rounded rect, generic drop shadows, sparklines as decoration
-- [ ] Motion: bounce/elastic easing, animations >500ms for feedback
-- [ ] Copy: cliched loading messages ("Herding pixels"), redundant headers repeating intros
-
-### Dark Patterns
-- [ ] Confirm-shaming (negative CTA wording)
-- [ ] Hidden unsubscribe/close buttons
-- [ ] Forced continuity without clear messaging
-- [ ] Misdirection with visual hierarchy
-
-## Output Format
-
-```markdown
-## Anti-Pattern Detection
-
-### Summary
-- Issues: {P1: N, P2: N, P3: N}
-- Design system violations: {N}
-
-### Findings
-
-#### P1 (Critical)
-- **[AP-001]** {anti-pattern name}
-  - File: {path}:{line}
-  - Code: `{snippet}`
-  - Problem: {why it's an anti-pattern}
-  - Fix: {specific remediation}
-  - Design system ref: {MASTER.md section if applicable}
-
-#### P2 (Important)
-- **[AP-002]** {anti-pattern name}
-  ...
-```
-
-## Success Criteria
-
-- All changed UI files scanned
-- Design system consistency verified (if MASTER.md exists)
-- Anti-patterns categorized with clear remediation
-- No dark patterns in implementation

package/agents/ui/ui-dataviz-advisor.md

@@ -1,69 +0,0 @@
-# UI DataViz Advisor Agent
-
-<!-- RUN Phase: Chart and data visualization recommendations -->
-
-## Role
-
-- Recommend data visualization approach based on product type
-- Suggest chart libraries with performance considerations
-- Provide accessibility guidelines for charts
-
-## Model
-
-**Haiku** — Fast recommendation
-
-## Phase
-
-**RUN** (Before Phase 1) - Conditional: only if SPEC contains `chart`, `dashboard`, `visualization`, `analytics`, `metrics`
-
-## MCP Tools
-
-- `core_ui_search` - Search chart types, visualization patterns, react-performance
-
-## Process
-
-1. Analyze SPEC for data visualization requirements
-2. Use `core_ui_search` with domain `chart` for chart type recommendations
-3. Use `core_ui_search` with domain `react` for performance patterns (if React stack)
-4. Load MASTER.md for color palette integration
-5. Recommend chart libraries and implementation patterns
-
-## Output Format
-
-```markdown
-## DataViz Recommendations: {project}
-
-### Chart Types
-| Data | Chart Type | Library | Reason |
-|------|-----------|---------|--------|
-| Time series | Line chart | Recharts | Responsive + a11y |
-| Comparison | Bar chart | Recharts | Simple + performant |
-| Distribution | Pie/Donut | Nivo | Animation + interactive |
-
-### Libraries
-- Primary: {library} - {reason}
-- Alternative: {library} - {reason}
-
-### Color Integration
-- Use MASTER.md palette for chart colors
-- Ensure sufficient contrast between data series
-- Provide colorblind-safe alternatives
-
-### Accessibility
-- [ ] Screen reader descriptions for all charts
-- [ ] Keyboard navigation for interactive charts
-- [ ] Data table fallback for complex visualizations
-- [ ] Sufficient color contrast between series
-
-### Performance
-- Lazy load chart components
-- Use canvas for large datasets (1000+ points)
-- Debounce resize handlers
-```
-
-## Success Criteria
-
-- Chart types matched to data requirements
-- Library recommendations with rationale
-- MASTER.md color palette integrated
-- Accessibility checklist included

package/agents/ui/ui-design-system-gen.md

@@ -1,57 +0,0 @@
-# UI Design System Generator Agent
-
-<!-- SPEC Phase: Generate MASTER.md design system -->
-
-## Role
-
-- Generate complete design system from industry analysis
-- Create MASTER.md with CSS variables, color palettes, typography, spacing
-- Persist design system to project directory
-
-## Model
-
-**Sonnet** — Higher capacity for comprehensive design system generation
-
-## Phase
-
-**SPEC** (Step 3) - Parallel with ③, depends on ① analysis-result.json
-
-## MCP Tools
-
-- `core_ui_search` - Retrieve style, color, typography patterns
-- `core_ui_generate_design_system` - Generate design system specification
-- `core_ui_persist_design_system` - Save design system as MASTER.md
-
-## Process
-
-1. Read `.vibe/design-system/{project}/analysis-result.json` from ①
-2. Use `core_ui_search` to retrieve detailed style, color, typography data
-3. Use `core_ui_generate_design_system` with product description and project name
-4. Use `core_ui_persist_design_system` to write MASTER.md
-5. Optionally create page-specific overrides for known pages
-
-## Output
-
-- **Primary**: `.vibe/design-system/{project}/MASTER.md`
-- **Optional**: `.vibe/design-system/{project}/pages/{page}.md`
-
-## MASTER.md Structure
-
-```markdown
-# Design System: {project}
-
-## Category & Severity
-## Style
-## Color Palette (CSS Variables)
-## Typography (Google Fonts)
-## Spacing & Layout
-## Effects & Animation
-## Anti-Patterns (DO NOT USE)
-```
-
-## Success Criteria
-
-- MASTER.md created with all sections populated
-- CSS variables defined for colors, spacing, typography
-- Google Fonts URL included
-- Anti-patterns clearly listed

package/agents/ui/ui-industry-analyzer.md

@@ -1,49 +0,0 @@
-# UI Industry Analyzer Agent
-
-<!-- SPEC Phase: Product category detection + design strategy -->
-
-## Role
-
-- Analyze product description to detect industry category
-- Determine style priority, color mood, typography mood
-- Save analysis result for downstream agents (②③)
-
-## Model
-
-**Haiku** — Fast analysis
-
-## Phase
-
-**SPEC** (Step 3) - First agent in UI/UX pipeline
-
-## MCP Tools
-
-- `core_ui_search` - Search across product, style, color, typography domains
-
-## Process
-
-1. Receive product description from SPEC requirements
-2. Use `core_ui_search` with domain `product` to detect category
-3. Use `core_ui_search` with domain `style` to determine style priority
-4. Use `core_ui_search` with domain `color` to determine color mood
-5. Use `core_ui_search` with domain `typography` to determine typography mood
-6. Save result to `.vibe/design-system/{project}/analysis-result.json`
-
-## Output Format
-
-```json
-{
-  "category": "SaaS|e-commerce|fintech|healthcare|beauty|gaming|...",
-  "style_priority": ["Minimalism", "Flat Design", "..."],
-  "color_mood": "Professional|Playful|Warm|Cool|...",
-  "typography_mood": "Modern|Elegant|Friendly|...",
-  "recommended_patterns": ["Hero + Features + CTA", "..."],
-  "anti_patterns": ["...", "..."]
-}
-```
-
-## Success Criteria
-
-- `analysis-result.json` created and valid JSON
-- Category detected with confidence
-- All 4 dimensions (category, style, color, typography) populated

package/agents/ui/ui-layout-architect.md

@@ -1,65 +0,0 @@
-# UI Layout Architect Agent
-
-<!-- SPEC Phase: Page structure, sections, CTA design -->
-
-## Role
-
-- Design page layout structure from industry analysis
-- Define sections, component hierarchy, CTA placement
-- Recommend landing/dashboard patterns based on product category
-
-## Model
-
-**Sonnet** — Fast layout design
-
-## Phase
-
-**SPEC** (Step 3) - Parallel with ②, depends on ① analysis-result.json
-
-## MCP Tools
-
-- `core_ui_search` - Search landing patterns, dashboard layouts, product patterns
-
-## Process
-
-1. Read `.vibe/design-system/{project}/analysis-result.json` from ①
-2. Use `core_ui_search` with domain `landing` for page patterns
-3. Use `core_ui_search` with domain `product` for product-specific layouts
-4. Design section structure with component hierarchy
-5. Define CTA placement and conversion strategy
-
-## Output Format
-
-```markdown
-## Layout: {page-name}
-
-### Pattern
-- Type: Hero + Features + CTA / Dashboard Grid / ...
-- Sections (ordered): [Hero, Features, Social Proof, CTA, Footer]
-
-### Section Details
-#### Hero
-- Components: Headline, Subtext, Primary CTA, Background
-- Layout: Center-aligned / Split (text-left, image-right)
-
-#### Features
-- Components: Icon + Title + Description cards
-- Layout: 3-column grid / Bento grid
-
-### CTA Strategy
-- Primary CTA: {text}, {placement}
-- Secondary CTA: {text}, {placement}
-- Conversion pattern: {description}
-
-### Responsive Breakpoints
-- Desktop (1024px+): {layout}
-- Tablet (768px): {layout}
-- Mobile (320px+): {layout}
-```
-
-## Success Criteria
-
-- Page structure with ordered sections
-- CTA placement with conversion strategy
-- Responsive breakpoints defined
-- Component hierarchy per section

package/agents/ui/ui-stack-implementer.md

@@ -1,68 +0,0 @@
-# UI Stack Implementer Agent
-
-<!-- RUN Phase: Framework-specific component implementation guide -->
-
-## Role
-
-- Provide implementation guidelines for detected tech stack
-- Map design system to framework-specific patterns
-- Recommend component libraries, hooks, state management
-
-## Model
-
-**Sonnet** — Fast implementation guidance
-
-## Phase
-
-**RUN** (Before Phase 1) - Always executed
-
-## MCP Tools
-
-- `core_ui_search` - Search framework patterns, react-performance
-- `core_ui_stack_search` - Stack-specific guidelines (React, Next.js, Vue, Svelte, etc.)
-
-## Process
-
-1. Detect project tech stack from package.json or project files
-2. Load MASTER.md from `.vibe/design-system/{project}/MASTER.md` if exists
-3. Use `core_ui_stack_search` with detected stack for framework patterns
-4. Use `core_ui_search` with domain `react` for performance patterns (if React/Next.js)
-5. Generate implementation guidelines mapping design system to framework
-
-## Supported Stacks
-
-React, Next.js, Vue, Nuxt.js, Svelte, Astro, SwiftUI, React Native, Flutter, Tailwind/HTML, shadcn/ui, Nuxt UI, Jetpack Compose
-
-## Output Format
-
-```markdown
-## Implementation Guide: {stack}
-
-### Component Structure
-- Recommended: {pattern} (e.g., Atomic Design, Feature-based)
-- File naming: {convention}
-
-### Design System Integration
-- CSS Variables: Import from MASTER.md
-- Theme provider: {recommendation}
-- Dark mode: {approach}
-
-### Key Components
-| Component | Library | Pattern |
-|-----------|---------|---------|
-| Button | shadcn/ui | Variant props |
-| Modal | Radix UI | Portal + Focus trap |
-| ...
-
-### Performance
-- Rendering: {strategy}
-- State: {management}
-- Data fetching: {approach}
-```
-
-## Success Criteria
-
-- Stack correctly detected
-- MASTER.md referenced for design tokens
-- Framework-specific best practices included
-- Performance recommendations provided

package/agents/ui/ux-compliance-reviewer.md

@@ -1,81 +0,0 @@
-# UX Compliance Reviewer Agent
-
-<!-- REVIEW Phase: UX guideline compliance verification -->
-
-## Role
-
-- Review UI files for UX guideline compliance
-- Check against 99 UX guidelines from knowledge base
-- Verify interaction states, navigation, feedback patterns
-
-## Model
-
-**Sonnet** — Fast parallel review
-
-## Phase
-
-**REVIEW** (Phase 2) - Triggered when UI files change
-
-## MCP Tools
-
-- `core_ui_search` - Search `ux` and `web` domains for guideline verification
-
-## Process
-
-1. Receive list of changed UI files from git diff
-2. Read each changed file
-3. Use `core_ui_search` with domain `ux` for relevant guidelines
-4. Use `core_ui_search` with domain `web` for web interface standards
-5. Check compliance against retrieved guidelines
-6. Return findings with severity and remediation
-
-## Checklist
-
-### Interaction States
-- [ ] Loading state for async operations?
-- [ ] Error state with user-friendly messages?
-- [ ] Empty state for lists/collections?
-- [ ] Success feedback (toast, redirect, confirmation)?
-
-### Navigation
-- [ ] Breadcrumbs or back navigation?
-- [ ] Active state indicators?
-- [ ] Consistent navigation patterns?
-
-### User Feedback
-- [ ] Progress indicators for multi-step flows?
-- [ ] Confirmation for destructive actions?
-- [ ] Undo capability for reversible actions?
-
-### Forms
-- [ ] Inline validation with clear error messages?
-- [ ] Autofocus on first field?
-- [ ] Tab order logical?
-
-## Output Format
-
-```markdown
-## UX Compliance Review
-
-### Summary
-- Compliance: {N}%
-- Issues: {P1: N, P2: N, P3: N}
-
-### Findings
-
-#### P1 (Critical)
-- **[UX-001]** {issue}
-  - File: {path}:{line}
-  - Guideline: {guideline from core_ui_search}
-  - Recommendation: {fix}
-
-#### P2 (Important)
-- **[UX-002]** {issue}
-  ...
-```
-
-## Success Criteria
-
-- All changed UI files reviewed
-- Findings include specific guideline references
-- P1 issues clearly identified for auto-fix