Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Patterns for building AI agents that integrate with CopilotKit. Use when designing agent architecture, implementing AG-UI event streaming, managing shared st...
Patterns for building AI agents that integrate with CopilotKit. Use when designing agent architecture, implementing AG-UI event streaming, managing shared st...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Architecture and implementation patterns for building AI agents that connect to CopilotKit. Contains 20 rules across 5 categories, prioritized by impact.
Reference these guidelines when: Designing agent architecture for CopilotKit integration Implementing AG-UI protocol event streaming Managing state synchronization between agent and frontend Adding human-in-the-loop checkpoints to agent workflows Emitting tool calls that render generative UI in the frontend
PriorityCategoryImpactPrefix1Agent ArchitectureCRITICALarchitecture-2AG-UI ProtocolHIGHagui-3State ManagementHIGHstate-4Human-in-the-LoopMEDIUMhitl-5Generative UI EmissionMEDIUMgenui-
architecture-built-in-agent - Use BuiltInAgent from @copilotkit/runtime/v2 for simple agents architecture-model-resolution - Use provider/model string format for model selection architecture-max-steps - Set maxSteps to prevent infinite tool call loops architecture-mcp-servers - Configure MCP endpoints for external tool access
agui-event-ordering - Emit events in correct order (start -> content -> end) agui-text-streaming - Stream text incrementally, not as single blocks agui-tool-call-lifecycle - Follow the complete tool call event lifecycle agui-state-snapshot - Emit STATE_SNAPSHOT events for frontend sync agui-error-events - Always emit error events on failure
state-snapshot-frequency - Emit state snapshots at meaningful checkpoints state-minimal-payload - Keep state snapshots minimal and serializable state-conflict-resolution - Handle bidirectional state conflicts gracefully state-thread-isolation - Isolate state per thread, not per agent
hitl-approval-gates - Use tool calls for approval gates, not custom events hitl-timeout-fallback - Always set timeouts with fallback behavior hitl-context-in-prompt - Include sufficient context for user decisions hitl-resume-state - Preserve full state when resuming after approval
genui-tool-call-render - Emit tool calls that map to frontend useRenderTool genui-streaming-args - Stream tool args incrementally for real-time UI genui-activity-messages - Use text messages for non-tool status updates
Read individual rule files for detailed explanations and code examples: rules/architecture-built-in-agent.md rules/agui-event-ordering.md
For the complete guide with all rules expanded: AGENTS.md
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Largest current source with strong distribution and engagement signals.