What problem does it solve? Integrating Velt's Activity Logs into React, Next.js, or other web apps involves many failure points: feeds returning null because logs were not enabled in the Velt Console, memory leaks from uncleaned subscriptions, noisy feeds from unbatched CRDT edits, and broken UI from conditionally rendering the VeltActivityLog web component. This Skill provides evidence-backed rules that prevent these mistakes. ## Core Features & Use Cases - Real-time activity feeds: Subscribe with useAllActivities or getAllActivities, with correct null loading-state handling, document/feature/action-type filtering, and subscription cleanup. - Custom activity records: Emit application events (deployments, status changes, escalations) via useActivityUtils or createActivity with displayMessageTemplate and template data. - Configuration & compliance: Configure CRDT debounce batching, enable immutability for SOX/SOC 2/HIPAA audit trails, and use exported action type constants for type-safe filtering. - UI customization: Compose the VeltActivityLogWireframe sub-component tree and bind slots with velt-data, velt-if, and velt-class template variables. - Use Case: Add a toggleable activity sidebar to a Next.js document page that shows all collaboration events, keeps the web component mounted with display:none, and logs custom task-status events into the same feed. ## Quick Start Ask the agent to add a Velt activity feed sidebar to your document page using the VeltActivityLog component with proper toggle behavior.
