docs/SKILL.md
# Arc Skills > Pre-built skills for AI coding assistants working with Arc ## Available Skills ### arc-diagram Create and modify Arc architecture diagrams. **Trigger**: When user asks to create, edit, or work with architecture diagrams **Capabilities**: - Generate ArcDiagramData from natural language descriptions - Add/remove/modify nodes and connectors - Apply themes and styling - Convert between JSON and TypeScript formats **Context to provide**: ``` Arc diagram format: JSON with layout,
npx skillsauth add arach/arc docsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Pre-built skills for AI coding assistants working with Arc
Create and modify Arc architecture diagrams.
Trigger: When user asks to create, edit, or work with architecture diagrams
Capabilities:
Context to provide:
Arc diagram format: JSON with layout, nodes, nodeData, connectors, connectorStyles
Valid colors: violet, emerald, blue, amber, sky, zinc, rose, orange
Valid sizes: s, m, l
Valid anchors: left, right, top, bottom, topLeft, topRight, bottomLeft, bottomRight
Icons: Any Lucide icon name (Server, Database, Monitor, Cloud, etc.)
Develop and debug the Arc editor codebase.
Trigger: When working on Arc editor source code
Context to provide:
Arc Editor Structure:
- Entry: src/main.jsx → App.jsx
- Editor: src/components/editor/DiagramEditor.jsx
- State: EditorProvider.jsx + editorReducer.js (useReducer pattern)
- Canvas: DiagramCanvas.jsx (pointer events)
- Nodes: EditableNode.jsx (drag with pointer capture)
- Connectors: ConnectorLayer.jsx (SVG paths)
- Icons: src/utils/iconRegistry.js
- Constants: src/utils/constants.js (COLORS, NODE_SIZES)
Commands: pnpm dev | pnpm build | pnpm lint
Stack: React 19, Vite 7, TailwindCSS 4, Lucide icons
Export Arc diagrams to various formats.
Trigger: When user wants to export or integrate Arc diagrams
Capabilities:
Example output (TypeScript):
import type { ArcDiagramData } from '@arach/arc'
export const systemArchitecture: ArcDiagramData = {
layout: { width: 700, height: 400 },
nodes: { /* ... */ },
nodeData: { /* ... */ },
connectors: [ /* ... */ ],
connectorStyles: { /* ... */ }
}
Add to your project's CLAUDE.md:
## Arc Diagram Context
When working with Arc diagrams:
- Format: JSON with layout, nodes, nodeData, connectors, connectorStyles
- Colors: violet, emerald, blue, amber, sky, zinc, rose, orange
- Sizes: s, m, l
- Anchors: left, right, top, bottom, topLeft, topRight, bottomLeft, bottomRight
- Icons: Lucide icon names (Server, Database, Monitor, etc.)
Key files:
- Editor: src/components/editor/
- State: EditorProvider.jsx + editorReducer.js
- Utils: src/utils/constants.js, iconRegistry.js
Add to .cursorrules or project instructions:
Arc is a visual diagram editor. Diagrams are JSON configs with:
- layout: { width, height }
- nodes: positions by ID
- nodeData: icon, name, color by ID
- connectors: from/to with anchors
- connectorStyles: color, strokeWidth, label
Use @arach/arc for React, @arach/arc-iso for isometric rendering.
Copy the contents of /llm.txt into your conversation context.
Create an Arc diagram showing [SYSTEM DESCRIPTION].
Include nodes for [COMPONENTS] connected via [RELATIONSHIPS].
Use the Arc JSON format with proper types.
Update this Arc diagram: [PASTE CONFIG]
Changes: [DESCRIBE CHANGES]
Return the complete updated config.
Debug Arc editor issue: [PROBLEM]
Check these files: EditorProvider.jsx, editorReducer.js, [RELEVANT_FILE]
The state shape is: { diagram, editor, meta, history }
development
Create architecture diagrams using Arc's JSON format. Use when asked to "create an architecture diagram", "draw a system diagram", "visualize the architecture", or "make a diagram of".
development
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
development
Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.
development
Run, watch, debug, and extend OpenClaw QA testing with qa-lab and qa-channel. Use when Codex needs to execute the repo-backed QA suite, inspect live QA artifacts, debug failing scenarios, add new QA scenarios, or explain the OpenClaw QA workflow. Prefer the live OpenAI lane with regular openai/gpt-5.4 in fast mode; do not use gpt-5.4-pro or gpt-5.4-mini unless the user explicitly overrides that policy.