Skill: ByteRover

Owner: byteroverinc

Summary: Manages project knowledge using ByteRover context tree. Provides two operations: query (retrieve knowledge) and curate (store knowledge). Invoke when user requests information lookup, pattern discovery, or knowledge persistence. Developed by ByteRover Inc. (https://byterover.dev/)

Tags: latest:1.2.2

Version history:

v1.2.2 | 2026-01-27T15:05:52.095Z | user

• Added author and version metadata to the SKILL.md file.
• Updated description to include developer attribution and website link: ByteRover Inc. (https://byterover.dev/).
• No changes to functionality or file structure.

v1.2.1 | 2026-01-27T10:13:25.216Z | user

ByteRover Agent Skill change summary:

• Added comprehensive SKILL.md documentation covering query and curate operations, usage scenarios, quality guidelines, and best practices.
• Included examples and command references for improved onboarding and usage clarity.
• Outlined context curation standards and troubleshooting instructions.
• Linked to additional resources for workflows and troubleshooting.

Archive index:

Archive v1.2.2: 4 files, 7121 bytes

Files: SKILL.md (3708b), TROUBLESHOOTING.md (1360b), WORKFLOWS.md (10495b), _meta.json (128b)

File v1.2.2:SKILL.md

---

name: byterover description: "Manages project knowledge using ByteRover context tree. Provides two operations: query (retrieve knowledge) and curate (store knowledge). Invoke when user requests information lookup, pattern discovery, or knowledge persistence. Developed by ByteRover Inc. (https://byterover.dev/)" metadata: author: ByteRover Inc. (https://byterover.dev/) version: "1.2.1"

ByteRover Context Tree

A project-level knowledge repository that persists across sessions. Use it to avoid re-discovering patterns, conventions, and decisions.

Why Use ByteRover

• Query before working: Get existing knowledge about patterns, conventions, and past decisions before implementing
• Curate after learning: Capture insights, decisions, and bug fixes so future sessions start informed

Quick Reference

| Command | When | Example | |---------|------|---------| | brv query "question" | Before starting work | brv query "How is auth implemented?" | | brv curate "context" -f file | After completing work | brv curate "JWT 24h expiry" -f auth.ts | | brv status | To check prerequisites | brv status |

When to Use

Query when you need to understand something:

• "How does X work in this codebase?"
• "What patterns exist for Y?"
• "Are there conventions for Z?"

Curate when you learned or created something valuable:

• Implemented a feature using specific patterns
• Fixed a bug and found root cause
• Made an architecture decision

Curate Quality

Context must be specific and actionable:

# Good - specific, explains where and why
brv curate "Auth uses JWT 24h expiry, tokens in httpOnly cookies" -f src/auth.ts

# Bad - too vague
brv curate "Fixed auth"

Note: Context argument must come before -f flags. Max 5 files.

Best Practices

1. Break down large contexts - Run multiple brv curate commands for complex topics rather than one massive context. Smaller chunks are easier to retrieve and update.

2. Let ByteRover read files - Don't read files yourself before curating. Use -f flags to let ByteRover read them directly:

   # Good - ByteRover reads the files
   brv curate "Auth implementation details" -f src/auth.ts -f src/middleware/jwt.ts
   
   # Wasteful - reading files twice
   # [agent reads files] then brv curate "..." -f same-files
   

3. Be specific in queries - Queries block your workflow. Use precise questions to get faster, more relevant results:

   # Good - specific
   brv query "What validation library is used for API request schemas?"
   
   # Bad - vague, slow
   brv query "How is validation done?"
   

4. Signal outdated context - When curating updates that replace existing knowledge, explicitly tell ByteRover to clean up:

   brv curate "OUTDATED: Previous auth used sessions. NEW: Now uses JWT with refresh tokens. Clean up old session-based auth context." -f src/auth.ts
   

5. Specify structure expectations - Guide ByteRover on how to organize the knowledge:

   # Specify topics/domains
   brv curate "Create separate topics for: 1) JWT validation, 2) refresh token flow, 3) logout handling" -f src/auth.ts
   
   # Specify detail level
   brv curate "Document the error handling patterns in detail (at least 30 lines covering all error types)" -f src/errors/
   

Prerequisites

Run brv status first. If errors occur, the agent cannot fix them—instruct the user to take action in their brv terminal. See TROUBLESHOOTING.md for details.

---

See also: WORKFLOWS.md for detailed patterns and examples, TROUBLESHOOTING.md for error handling

File v1.2.2:_meta.json

{ "ownerId": "kn73aw5gqbhxdqygjachxpd401800y76", "slug": "byterover", "version": "1.2.2", "publishedAt": 1769526352095 }

File v1.2.2:TROUBLESHOOTING.md

ByteRover Troubleshooting

Quick Diagnosis

brv status

User Action Required

These errors require user intervention (agent cannot fix):

| Error | User Action | |-------|-------------| | "No ByteRover instance is running" | Start brv in separate terminal | | "Not authenticated" | Run /login in brv REPL | | "Project not initialized" | Run /init in brv REPL | | "Connection failed" | Restart brv (Ctrl+C, then brv) |

Template response:

Please [action] in your brv terminal, then I'll retry the command.

Agent-Fixable Errors

| Error | Fix | |-------|-----| | "Context argument required" | Add text before -f: brv curate "text" -f file | | "Maximum 5 files allowed" | Reduce to 5 or fewer -f flags | | "File not found" | Verify path with ls, use relative paths from project root | | "No relevant context found" | Try different query phrasing, or curate knowledge first |

Architecture

ByteRover uses client-server architecture:

• User runs brv to start server (interactive REPL)
• Agent commands (query, curate, status) connect to server
• Server must be running for commands to work

Exit Codes

| Code | Meaning | |------|---------| | 0 | Success | | 1 | General error | | 2 | Connection error |

Getting Help

• Email: [email protected]
• Discord: https://discord.com/invite/UMRrpNjh5W

File v1.2.2:WORKFLOWS.md

ByteRover Workflows

Pattern 1: Research Before Implementation

Use when starting new features or working in unfamiliar areas.

Workflow:

Query existing knowledge → Implement following patterns → Curate new decisions

Example: Adding a new API endpoint

# 1. Query for existing patterns
# Be SPECIFIC to get faster, more relevant results
brv query "What middleware chain is used for authenticated API endpoints?"
brv query "What is the standard error response format for API routes?"

# 2. Implement following discovered patterns
# ... write code ...

# 3. Curate decisions made
# Don't read the file first - let ByteRover read it via -f flag
brv curate "Added /api/users/profile endpoint. Uses authMiddleware for JWT validation, returns UserProfileDTO. Error handling follows ApiError pattern" -f src/api/routes/users.ts

Example: Implementing a new React component

# 1. Query patterns - specific questions save time
brv query "What data fetching hook pattern is used in list components?"
brv query "Are CSS modules or styled-components used for component styling?"

# 2. Implement
# ... write component ...

# 3. Curate with file reference - ByteRover reads the file
brv curate "Created UserAvatar component. Uses React Query for data fetching, CSS modules for styling. Follows existing pattern in src/components/common/" -f src/components/UserAvatar.tsx

Pattern 2: Debug and Document

Use when fixing bugs to capture learnings and prevent recurrence.

Workflow:

Query known issues → Debug and fix → Curate root cause and solution

Example: Fixing a race condition

# 1. Query for context - be specific about the symptom
brv query "Are there known race condition patterns or AbortController usage in data fetching hooks?"

# 2. Debug and fix
# ... investigate, find root cause, implement fix ...

# 3. Curate the learning with structured format
brv curate "Bug: stale data after rapid navigation. Cause: useEffect cleanup not cancelling requests. Fix: AbortController with cleanup. Pattern: always abort fetch in useEffect cleanup" -f src/hooks/useUserData.ts

Example: Fixing an authentication issue

# 1. Specific query about the problem area
brv query "How are credentials and cookies configured in the API client fetch calls?"

# 2. Fix
# ... debug and fix ...

# 3. Curate with emphasis on the gotcha
brv curate "Bug: unexpected logouts. Cause: fetch missing credentials option. Fix: added 'credentials: include' to fetch config. IMPORTANT: all API calls must include credentials for cookie-based auth" -f src/lib/api-client.ts

Pattern 3: Multi-File Changes

Use when changes span multiple files to maintain context.

Example: Adding a new feature across layers

# 1. Query architecture - specific about the layers
brv query "How are full-stack features organized across API routes, service layer, and React components?"

# 2. Implement across files
# ... write code ...

# 3. Curate with multiple files (max 5)
# Let ByteRover read all files - don't read them yourself first
# Specify the topics you want created
brv curate "Added user notifications feature. Create separate topics for: 1) API endpoint structure, 2) NotificationService business logic, 3) useNotifications React hook pattern, 4) NotificationBell UI component" -f src/api/notifications.ts -f src/services/NotificationService.ts -f src/hooks/useNotifications.ts -f src/components/NotificationBell.tsx

Example: Database schema change with migrations

# 1. Query migration patterns
brv query "What is the migration naming convention and how are schema changes tested?"

# 2. Implement
# ... create migration, update models, update queries ...

# 3. Multiple curates for different concerns - break down large context
brv curate "Added user_preferences table with JSONB settings column. Migration: 20240115_add_user_preferences" -f migrations/20240115_add_user_preferences.ts

brv curate "UserPreferences model with type-safe JSONB access. Includes validation for theme, notifications, locale settings" -f src/models/UserPreferences.ts

brv curate "Updated UserService to load/save preferences. Uses transaction for atomic updates with user record" -f src/services/UserService.ts

Pattern 4: Updating Existing Knowledge

Use when changes make previous context outdated.

Example: Refactoring authentication system

# 1. Query current documented state
brv query "What is currently documented about authentication implementation and token handling?"

# 2. Implement refactor
# ... refactor code ...

# 3. Curate with explicit cleanup signal
# Tell ByteRover to clean up outdated context
brv curate "OUTDATED: Previous auth used session cookies stored in Redis. NEW: Migrated to JWT with refresh tokens. Access token in memory (15min), refresh token in httpOnly cookie (7d). Remove/update any session-based auth context in the tree" -f src/auth/jwt.ts -f src/auth/refresh.ts

Example: Replacing a library

# 1. Query what's documented about the old library
brv query "What patterns are documented for moment.js date handling?"

# 2. Implement replacement
# ... replace library usage ...

# 3. Curate the replacement with cleanup signal
brv curate "REPLACED: Removed moment.js (bloated, mutable). Now using date-fns (tree-shakeable, immutable). Clean up any moment.js context. New patterns: format(date, 'yyyy-MM-dd'), parseISO(string), differenceInDays(date1, date2)" -f src/utils/dates.ts

Example: API versioning change

# Curate with explicit version context
brv curate "OUTDATED: API v1 endpoints deprecated. NEW: All endpoints now v2 with breaking changes. v2 uses camelCase response keys, pagination via cursor (not offset), errors include requestId. Update any v1 API context" -f src/api/v2/routes.ts

Pattern 5: Comprehensive Documentation

Use when documenting complex systems that need detailed breakdown.

Example: Documenting a payment module

# Break into multiple curates - don't try to capture everything in one
# Specify structure and detail level for each topic

# Overview first
brv curate "Payment module overview: Stripe integration with webhooks for subscription management. Create 4 separate detailed topics covering the full payment lifecycle" -f src/payments/

# Topic 1 - detailed with line count guidance
brv curate "Topic: Payment checkout flow. Cover: 1) cart validation, 2) createPaymentIntent call, 3) client-side confirmation, 4) success/failure handling. Include error scenarios. At least 50 lines of detailed documentation" -f src/payments/checkout.ts -f src/payments/intent.ts

# Topic 2 - webhook handling
brv curate "Topic: Stripe webhook handling. Cover: 1) signature verification with STRIPE_WEBHOOK_SECRET, 2) idempotency with processed_events table, 3) event types (payment_intent.succeeded, payment_intent.failed, customer.subscription.*). At least 40 lines" -f src/payments/webhooks.ts

# Topic 3 - subscription management
brv curate "Topic: Subscription lifecycle. Cover: trial period handling, upgrade/downgrade proration, cancellation with grace period, reactivation flow" -f src/payments/subscriptions.ts

# Topic 4 - error handling
brv curate "Topic: Payment error handling. Cover: StripeError types (CardError, InvalidRequestError, APIError), retry logic for transient failures, user-facing error messages mapping" -f src/payments/errors.ts

Example: Documenting a state management system

# Multiple focused curates instead of one massive one

brv curate "State management overview: Using Zustand with persistence middleware. Create topics for: store structure, async actions, persistence, devtools integration" -f src/store/

brv curate "Topic: Store structure. Separate stores per domain (userStore, cartStore, uiStore). Each store follows pattern: state interface, actions, selectors. No cross-store dependencies" -f src/store/userStore.ts -f src/store/cartStore.ts

brv curate "Topic: Async actions. Pattern: set loading -> try/catch -> set data/error -> clear loading. All API calls go through apiClient. Optimistic updates for cart operations" -f src/store/cartStore.ts -f src/store/actions/

brv curate "Topic: Persistence. userStore persisted to localStorage (excluding sensitive data). cartStore persisted to sessionStorage. Custom serializer excludes functions and timestamps" -f src/store/middleware/persist.ts

Pattern 6: Exploratory Documentation

Use when you need to document an unfamiliar codebase area.

Example: Understanding and documenting an existing module

# 1. Query what's already known
brv query "What is documented about the notification system and real-time updates?"

# 2. Explore the code (agent reads files to understand)
# ... read and understand the code ...

# 3. Curate in chunks as you understand different parts
# First curate: high-level architecture
brv curate "Notification system uses WebSocket for real-time delivery with Redis pub/sub for horizontal scaling. Three components: NotificationService (creation/storage), NotificationGateway (WebSocket), NotificationWorker (background processing)" -f src/notifications/

# Second curate: specific implementation detail
brv curate "WebSocket authentication: JWT token passed in connection query params, validated on connect, stored in socket.data. Rooms: user_{id} for personal, team_{id} for team broadcasts" -f src/notifications/NotificationGateway.ts

# Third curate: gotchas discovered
brv curate "Notification gotchas: 1) Must call gateway.joinRoom after auth, 2) Unread count cached in Redis (5min TTL) - call invalidateUnreadCount after marking read, 3) Batch notifications throttled to max 10/second per user" -f src/notifications/NotificationService.ts

What to Curate

Do curate:

• Architecture decisions: "Chose Redis for sessions because of horizontal scaling"
• Patterns: "All forms use react-hook-form with zod. Pattern in LoginForm.tsx"
• Non-obvious conventions: "File uploads go to /tmp first, then S3 after validation"
• Bug root causes: "Memory leak from event listeners not removed on unmount"
• Gotchas: "PostgreSQL JSONB queries need explicit casting for arrays"
• Replacements: "OUTDATED: X, NEW: Y" when refactoring

Don't curate:

• Obvious facts: "Uses TypeScript", "Has a README"
• Temporary states: "Currently debugging X"
• Personal preferences: "I prefer tabs"
• Trivial changes: "Fixed typo in comment"

Archive v1.2.1: 4 files, 7065 bytes

Files: SKILL.md (3576b), TROUBLESHOOTING.md (1360b), WORKFLOWS.md (10495b), _meta.json (128b)

File v1.2.1:SKILL.md

---

name: byterover description: "Manages project knowledge using ByteRover context tree. Provides two operations: query (retrieve knowledge) and curate (store knowledge). Invoke when user requests information lookup, pattern discovery, or knowledge persistence."

ByteRover Context Tree

A project-level knowledge repository that persists across sessions. Use it to avoid re-discovering patterns, conventions, and decisions.

Why Use ByteRover

• Query before working: Get existing knowledge about patterns, conventions, and past decisions before implementing
• Curate after learning: Capture insights, decisions, and bug fixes so future sessions start informed

Quick Reference

| Command | When | Example | |---------|------|---------| | brv query "question" | Before starting work | brv query "How is auth implemented?" | | brv curate "context" -f file | After completing work | brv curate "JWT 24h expiry" -f auth.ts | | brv status | To check prerequisites | brv status |

When to Use

Query when you need to understand something:

• "How does X work in this codebase?"
• "What patterns exist for Y?"
• "Are there conventions for Z?"

Curate when you learned or created something valuable:

• Implemented a feature using specific patterns
• Fixed a bug and found root cause
• Made an architecture decision

Curate Quality

Context must be specific and actionable:

# Good - specific, explains where and why
brv curate "Auth uses JWT 24h expiry, tokens in httpOnly cookies" -f src/auth.ts

# Bad - too vague
brv curate "Fixed auth"

Note: Context argument must come before -f flags. Max 5 files.

Best Practices

1. Break down large contexts - Run multiple brv curate commands for complex topics rather than one massive context. Smaller chunks are easier to retrieve and update.

2. Let ByteRover read files - Don't read files yourself before curating. Use -f flags to let ByteRover read them directly:

   # Good - ByteRover reads the files
   brv curate "Auth implementation details" -f src/auth.ts -f src/middleware/jwt.ts
   
   # Wasteful - reading files twice
   # [agent reads files] then brv curate "..." -f same-files
   

3. Be specific in queries - Queries block your workflow. Use precise questions to get faster, more relevant results:

   # Good - specific
   brv query "What validation library is used for API request schemas?"
   
   # Bad - vague, slow
   brv query "How is validation done?"
   

4. Signal outdated context - When curating updates that replace existing knowledge, explicitly tell ByteRover to clean up:

   brv curate "OUTDATED: Previous auth used sessions. NEW: Now uses JWT with refresh tokens. Clean up old session-based auth context." -f src/auth.ts
   

5. Specify structure expectations - Guide ByteRover on how to organize the knowledge:

   # Specify topics/domains
   brv curate "Create separate topics for: 1) JWT validation, 2) refresh token flow, 3) logout handling" -f src/auth.ts
   
   # Specify detail level
   brv curate "Document the error handling patterns in detail (at least 30 lines covering all error types)" -f src/errors/
   

Prerequisites

Run brv status first. If errors occur, the agent cannot fix them—instruct the user to take action in their brv terminal. See TROUBLESHOOTING.md for details.

---

See also: WORKFLOWS.md for detailed patterns and examples, TROUBLESHOOTING.md for error handling

File v1.2.1:_meta.json

{ "ownerId": "kn73aw5gqbhxdqygjachxpd401800y76", "slug": "byterover", "version": "1.2.1", "publishedAt": 1769508805216 }

File v1.2.1:TROUBLESHOOTING.md

ByteRover Troubleshooting

Quick Diagnosis

brv status

User Action Required

These errors require user intervention (agent cannot fix):

| Error | User Action | |-------|-------------| | "No ByteRover instance is running" | Start brv in separate terminal | | "Not authenticated" | Run /login in brv REPL | | "Project not initialized" | Run /init in brv REPL | | "Connection failed" | Restart brv (Ctrl+C, then brv) |

Template response:

Please [action] in your brv terminal, then I'll retry the command.

Agent-Fixable Errors

| Error | Fix | |-------|-----| | "Context argument required" | Add text before -f: brv curate "text" -f file | | "Maximum 5 files allowed" | Reduce to 5 or fewer -f flags | | "File not found" | Verify path with ls, use relative paths from project root | | "No relevant context found" | Try different query phrasing, or curate knowledge first |

Architecture

ByteRover uses client-server architecture:

• User runs brv to start server (interactive REPL)
• Agent commands (query, curate, status) connect to server
• Server must be running for commands to work

Exit Codes

| Code | Meaning | |------|---------| | 0 | Success | | 1 | General error | | 2 | Connection error |

Getting Help

• Email: [email protected]
• Discord: https://discord.com/invite/UMRrpNjh5W

File v1.2.1:WORKFLOWS.md

ByteRover Workflows

Pattern 1: Research Before Implementation

Use when starting new features or working in unfamiliar areas.

Workflow:

Query existing knowledge → Implement following patterns → Curate new decisions

Example: Adding a new API endpoint

# 1. Query for existing patterns
# Be SPECIFIC to get faster, more relevant results
brv query "What middleware chain is used for authenticated API endpoints?"
brv query "What is the standard error response format for API routes?"

# 2. Implement following discovered patterns
# ... write code ...

# 3. Curate decisions made
# Don't read the file first - let ByteRover read it via -f flag
brv curate "Added /api/users/profile endpoint. Uses authMiddleware for JWT validation, returns UserProfileDTO. Error handling follows ApiError pattern" -f src/api/routes/users.ts

Example: Implementing a new React component

# 1. Query patterns - specific questions save time
brv query "What data fetching hook pattern is used in list components?"
brv query "Are CSS modules or styled-components used for component styling?"

# 2. Implement
# ... write component ...

# 3. Curate with file reference - ByteRover reads the file
brv curate "Created UserAvatar component. Uses React Query for data fetching, CSS modules for styling. Follows existing pattern in src/components/common/" -f src/components/UserAvatar.tsx

Pattern 2: Debug and Document

Use when fixing bugs to capture learnings and prevent recurrence.

Workflow:

Query known issues → Debug and fix → Curate root cause and solution

Example: Fixing a race condition

# 1. Query for context - be specific about the symptom
brv query "Are there known race condition patterns or AbortController usage in data fetching hooks?"

# 2. Debug and fix
# ... investigate, find root cause, implement fix ...

# 3. Curate the learning with structured format
brv curate "Bug: stale data after rapid navigation. Cause: useEffect cleanup not cancelling requests. Fix: AbortController with cleanup. Pattern: always abort fetch in useEffect cleanup" -f src/hooks/useUserData.ts

Example: Fixing an authentication issue

# 1. Specific query about the problem area
brv query "How are credentials and cookies configured in the API client fetch calls?"

# 2. Fix
# ... debug and fix ...

# 3. Curate with emphasis on the gotcha
brv curate "Bug: unexpected logouts. Cause: fetch missing credentials option. Fix: added 'credentials: include' to fetch config. IMPORTANT: all API calls must include credentials for cookie-based auth" -f src/lib/api-client.ts

Pattern 3: Multi-File Changes

Use when changes span multiple files to maintain context.

Example: Adding a new feature across layers

# 1. Query architecture - specific about the layers
brv query "How are full-stack features organized across API routes, service layer, and React components?"

# 2. Implement across files
# ... write code ...

# 3. Curate with multiple files (max 5)
# Let ByteRover read all files - don't read them yourself first
# Specify the topics you want created
brv curate "Added user notifications feature. Create separate topics for: 1) API endpoint structure, 2) NotificationService business logic, 3) useNotifications React hook pattern, 4) NotificationBell UI component" -f src/api/notifications.ts -f src/services/NotificationService.ts -f src/hooks/useNotifications.ts -f src/components/NotificationBell.tsx

Example: Database schema change with migrations

# 1. Query migration patterns
brv query "What is the migration naming convention and how are schema changes tested?"

# 2. Implement
# ... create migration, update models, update queries ...

# 3. Multiple curates for different concerns - break down large context
brv curate "Added user_preferences table with JSONB settings column. Migration: 20240115_add_user_preferences" -f migrations/20240115_add_user_preferences.ts

brv curate "UserPreferences model with type-safe JSONB access. Includes validation for theme, notifications, locale settings" -f src/models/UserPreferences.ts

brv curate "Updated UserService to load/save preferences. Uses transaction for atomic updates with user record" -f src/services/UserService.ts

Pattern 4: Updating Existing Knowledge

Use when changes make previous context outdated.

Example: Refactoring authentication system

# 1. Query current documented state
brv query "What is currently documented about authentication implementation and token handling?"

# 2. Implement refactor
# ... refactor code ...

# 3. Curate with explicit cleanup signal
# Tell ByteRover to clean up outdated context
brv curate "OUTDATED: Previous auth used session cookies stored in Redis. NEW: Migrated to JWT with refresh tokens. Access token in memory (15min), refresh token in httpOnly cookie (7d). Remove/update any session-based auth context in the tree" -f src/auth/jwt.ts -f src/auth/refresh.ts

Example: Replacing a library

# 1. Query what's documented about the old library
brv query "What patterns are documented for moment.js date handling?"

# 2. Implement replacement
# ... replace library usage ...

# 3. Curate the replacement with cleanup signal
brv curate "REPLACED: Removed moment.js (bloated, mutable). Now using date-fns (tree-shakeable, immutable). Clean up any moment.js context. New patterns: format(date, 'yyyy-MM-dd'), parseISO(string), differenceInDays(date1, date2)" -f src/utils/dates.ts

Example: API versioning change

# Curate with explicit version context
brv curate "OUTDATED: API v1 endpoints deprecated. NEW: All endpoints now v2 with breaking changes. v2 uses camelCase response keys, pagination via cursor (not offset), errors include requestId. Update any v1 API context" -f src/api/v2/routes.ts

Pattern 5: Comprehensive Documentation

Use when documenting complex systems that need detailed breakdown.

Example: Documenting a payment module

# Break into multiple curates - don't try to capture everything in one
# Specify structure and detail level for each topic

# Overview first
brv curate "Payment module overview: Stripe integration with webhooks for subscription management. Create 4 separate detailed topics covering the full payment lifecycle" -f src/payments/

# Topic 1 - detailed with line count guidance
brv curate "Topic: Payment checkout flow. Cover: 1) cart validation, 2) createPaymentIntent call, 3) client-side confirmation, 4) success/failure handling. Include error scenarios. At least 50 lines of detailed documentation" -f src/payments/checkout.ts -f src/payments/intent.ts

# Topic 2 - webhook handling
brv curate "Topic: Stripe webhook handling. Cover: 1) signature verification with STRIPE_WEBHOOK_SECRET, 2) idempotency with processed_events table, 3) event types (payment_intent.succeeded, payment_intent.failed, customer.subscription.*). At least 40 lines" -f src/payments/webhooks.ts

# Topic 3 - subscription management
brv curate "Topic: Subscription lifecycle. Cover: trial period handling, upgrade/downgrade proration, cancellation with grace period, reactivation flow" -f src/payments/subscriptions.ts

# Topic 4 - error handling
brv curate "Topic: Payment error handling. Cover: StripeError types (CardError, InvalidRequestError, APIError), retry logic for transient failures, user-facing error messages mapping" -f src/payments/errors.ts

Example: Documenting a state management system

# Multiple focused curates instead of one massive one

brv curate "State management overview: Using Zustand with persistence middleware. Create topics for: store structure, async actions, persistence, devtools integration" -f src/store/

brv curate "Topic: Store structure. Separate stores per domain (userStore, cartStore, uiStore). Each store follows pattern: state interface, actions, selectors. No cross-store dependencies" -f src/store/userStore.ts -f src/store/cartStore.ts

brv curate "Topic: Async actions. Pattern: set loading -> try/catch -> set data/error -> clear loading. All API calls go through apiClient. Optimistic updates for cart operations" -f src/store/cartStore.ts -f src/store/actions/

brv curate "Topic: Persistence. userStore persisted to localStorage (excluding sensitive data). cartStore persisted to sessionStorage. Custom serializer excludes functions and timestamps" -f src/store/middleware/persist.ts

Pattern 6: Exploratory Documentation

Use when you need to document an unfamiliar codebase area.

Example: Understanding and documenting an existing module

# 1. Query what's already known
brv query "What is documented about the notification system and real-time updates?"

# 2. Explore the code (agent reads files to understand)
# ... read and understand the code ...

# 3. Curate in chunks as you understand different parts
# First curate: high-level architecture
brv curate "Notification system uses WebSocket for real-time delivery with Redis pub/sub for horizontal scaling. Three components: NotificationService (creation/storage), NotificationGateway (WebSocket), NotificationWorker (background processing)" -f src/notifications/

# Second curate: specific implementation detail
brv curate "WebSocket authentication: JWT token passed in connection query params, validated on connect, stored in socket.data. Rooms: user_{id} for personal, team_{id} for team broadcasts" -f src/notifications/NotificationGateway.ts

# Third curate: gotchas discovered
brv curate "Notification gotchas: 1) Must call gateway.joinRoom after auth, 2) Unread count cached in Redis (5min TTL) - call invalidateUnreadCount after marking read, 3) Batch notifications throttled to max 10/second per user" -f src/notifications/NotificationService.ts

What to Curate

Do curate:

• Architecture decisions: "Chose Redis for sessions because of horizontal scaling"
• Patterns: "All forms use react-hook-form with zod. Pattern in LoginForm.tsx"
• Non-obvious conventions: "File uploads go to /tmp first, then S3 after validation"
• Bug root causes: "Memory leak from event listeners not removed on unmount"
• Gotchas: "PostgreSQL JSONB queries need explicit casting for arrays"
• Replacements: "OUTDATED: X, NEW: Y" when refactoring

Don't curate:

• Obvious facts: "Uses TypeScript", "Has a README"
• Temporary states: "Currently debugging X"
• Personal preferences: "I prefer tabs"
• Trivial changes: "Fixed typo in comment"