Shareable instruction files for Cursor, Claude Code, Copilot, Windsurf, and more — installed alongside your existing agent rules.
For your AI agents data to show up in the Sentry [AI Agents Insights](https://sentry.io/orgredirect/organizations/:orgslug/insights/ai/agents/), at least one of the AI spans needs to be created and have well-defined names and data attributes. If the required data (marked with MUST or required) is missing, the data will not show up in the Agents dashbboard.
This guide provides a practical, hands-on introduction to the **Agent Council** and the **`@thinkies` orchestrator**. This system is designed for users who want to leverage the cognitive power of the INDRA ecosystem using natural language, without needing to write or understand the INDRA protocol itself.
All agents MUST emit JSON conforming to this logical schema: "role": "Security | SRE | Platform | FinOps | Compliance | DevOps | Performance | Roadmap", "severity": "high | medium | low", "evidence": ["kb://... or doc://..."],
Config is inspired by LazyVim but does NOT use LazyVim directly. **Steps to upgrade:** 1. Clone LazyVim repo (if not already present): gh repo clone LazyVim/LazyVim 2. Check diff between commits to identify changes:
MCG is a Rust Cargo workspace for a browser-based card game. The frontend crate (`frontend`) compiles to WebAssembly with `wasm-pack` and renders using `egui`/`eframe`. The backend crate (`native_mcg`) exposes HTTP, WebSocket, and optional iroh QUIC transports, while the `shared` crate provides protocol and domain types used by both sides. Generated WASM artifacts live under the repository-root `pkg/` directory and are loaded by `index.html`; media assets are served from `media/`.
This document provides guidelines for AI coding agents working in the JSON Visualization codebase. > **💡 For comprehensive documentation**: See [`.agentskills/json-visualization-dev/`](.agentskills/json-visualization-dev/) for structured Agent Skills with detailed architecture, components, and state management references.
1. **Identify Task Layer**: Determine if the task is **Infrastructure** (Docker, Bash) or **Application** (React, Next.js). 2. **Load Targeted Context**: Read only the maps and rules relevant to your active layer (see `.agents/rules/how-to-scan-repository.md`).