arcgramlisted

# Arcgram — Interactive Architectural Diagram (v2) > **For any AI agent — Arcgram is agent-neutral, not a Claude-only skill.** The block above is ordinary YAML frontmatter: Claude's skill system reads `name`/`description` to auto-trigger it, and any other agent (GPT · Gemini · Cline · Continue.dev · Cursor · Aider · local) just reads the plain-markdown body — no rejection, no Claude dependency. This is the **v2** skill — engine `template-v2.html`, fields in `schema.md`, per-platform install in `USAGE.md`. ## What this is Arcgram is a human↔AI collaboration substrate: the AI externalizes its reasoning as a typed node-and-edge graph the human audits and adjusts, converging on ground truth that survives across turns, sessions, and agents. **The AI draws, the human audits.** (Full positioning: `README.md`.) **Three guards keep the drawing honest** — internalize them before you build: - A **node** is a diagram element — a component, step, decision, artifact, or tool. It is **not** an HTML/DOM/React node, and **not** an argument-map "claim." An **edge** carries flow or dependency — **not** "supports/contradicts." - **The gap signal:** if a step can't be drawn as explicit nodes and edges, that's reasoning with a gap to expose — not a formality to skip. - **Drawing exposes gaps; it does not certify correctness.** A graph you can draw can still be wrong. --- ## When to use Reach for Arcgram when the structure of a thing — or of your reasoning about it — gets hard to hold in pla