ai-config

name	ai-config
description	Use when a task mentions ~/.config/ai, global or personal AI configuration, shared agent instructions, portable skills, harness-specific skills, or AI setup shared across OpenCode, Claude, and Codex. Don't use for normal application code or project-only AI configuration.

AI Config

Treat ~/.config/ai as the canonical source for the machine's shared AI setup. Read it before explaining or changing that setup instead of relying on memory or runtime copies.

Workflow

1. Open the source of truth. Use an explicitly supplied root when present; otherwise use ~/.config/ai. List the root, then read agents.md and tooling-inventory.md. Finish with the current policies and ownership boundaries understood.
2. Classify the task. Read only the relevant canonical area:
   • Shared behavior: agents.md
   • Portable skills: skills/<name>/SKILL.md
   • Runtime-only behavior: harness/<runtime>/
   • Knowledge-base work: knowledge-base/ and the matching KB skill
   • Adapted skill provenance: skills-sources.lock.json and the skill's references/sources.md
3. Consult the right skill guides. For creating, editing, adapting, or reviewing a skill, load both skill-authoring and skill-creator before drafting. When a change is runtime-specific, load an available runtime customization skill—for OpenCode, use customize-opencode—or inspect that runtime's canonical harness files when no such skill exists. Finish with the required metadata, provenance, and validation rules identified.
4. Trace deployment. Inspect current symlinks or runtime configuration before assuming where canonical files appear. Prefer for portable skills and for runtime-specific skills. Avoid editing generated, vendor-managed, or compatibility copies when a canonical source exists.