🪸 Coral

한국어

Claude Code already knows how to code. Coral teaches it how you work.

Install

Requirements: Node.js 18+

/plugin marketplace add https://github.com/kangig94/coral
/plugin install coral

# Codex CLI (optional — enables --codex cross-model delegation):
npm install -g @openai/codex

Try It Now

Run this on any existing project:

/coral:analyze what does this codebase do?

Structure a Project

https://github.com/user-attachments/assets/881f1a14-9f4f-4d3d-8023-59610eb13ac4

/coral:init-project

Coral scans your stack and generates .claude/ — conventions, review agents, architecture docs — tailored to your project.

Generated agents aren't boilerplate — they encode evaluation rubrics calibrated to your project's stack and audience. Claude follows your rules, not generic defaults.

/coral:init-project                                          # existing project
/coral:init-project "React + FastAPI"                        # tech stack hint
/coral:init-project "multi-tenant SaaS REST API with Go"     # full description

my-project/
+ .claude/
+   CLAUDE.md                 ← project hub: build commands, workflow, critical rules
+   agents/
+     code-critic.md          ← code quality review
+     ...                     ← domain agents (React, Go, ML, infra, etc.)
+   rules/
+     conventions.md          ← naming, git, style
+     ...                     ← domain rules, auto-activated by file path
+ docs/
+   architecture.md           ← module map, dependency graph

Browse this repository's .claude/ folder for a real example.

Plan, Build, and Fix

pathfind  →  preplan  →  plan  →  ralph
(explore)    (define)    (design)  (implement + verify)

# Know the problem, need a plan:
/coral:plan add retry logic to the API client

# Have symptoms, not sure what's wrong:
/coral:pathfind API is slow, DB hits limits, users are complaining

# Complex problem, need alignment first:
/coral:preplan race condition in the session manager

# Have a plan, just implement it:
/coral:ralph implement the caching layer

# Bug — diagnose, plan, fix in one shot:
/coral:bugfix why does session lookup return null?

Each stage produces an artifact that feeds the next. Enter at any point — skip stages you don't need.

pathfind — "I have problems but don't know what to build."
Clusters symptoms, investigates root causes (spawns scanner for codebase analysis),
generates divergent directions through orthogonal lanes, and spawns pioneer for elegant alternatives.
Outputs a ranked direction list with scoring matrix.
Hands off the chosen direction to preplan.

preplan — "I know the direction but need agreement on scope."
Fills a 7-item agreement (problem statement, success criteria, scope, assumptions, affected systems, constraints, approach direction)
autonomously from codebase analysis, then presents to the user for correction.
Spawns pioneer to find elegant alternatives for uncertain items, offering default/minimal/elegant spectrums.
Produces pre-{topic}.md — the contract that plan must satisfy.

plan — "I need a design before I build."
Multi-round review loop: dispatches architect + critic (and resolver in --deep mode) as a workflow,
synthesizes findings, edits the plan file, and evaluates an exit gate.
The resolver classifies findings (Adopt/Adapt/Defer/Diverge), applies changes,
and decides whether another round is needed based on finding severity and nature.
Produces {topic}.md with acceptance criteria, implementation phases, and execution order (dependency graph + parallel batches).

ralph — "I have a plan (or prompt). Just build it."
Persistent executor with verification loop.
In plan mode, reads the execution order and dispatches batches — parallelizing independent ACs.
Every completion claim requires fresh verification evidence (lint → build → test).
--red spawns a red-attacker in parallel to write adversarial tests targeting blind spots.
--team uses Agent Teams for parallel AC execution.

# Deep review with methodology-driven synthesis (resolver + HOW reasoning):
/coral:plan --deep add retry logic to the API client

# Adversarial testing — spawns a red-attacker to target blind spots:
/coral:ralph --red implement the caching layer

# Cross-model delegation to Codex CLI:
/coral:plan --codex redesign the session management system

# Direct Codex session (multi-turn, persistent):
/coral:codex review auth.ts for security issues

--codex delegates within a skill; /coral:codex opens a persistent session.

Discuss

/coral:discuss should we use microservices or a monolith?

Multiple AI personas argue from different angles. Bid-based turn-taking, genuine cross-examination, structured synthesis at the end.

Join as a participant: /coral:discuss --user "topic", then /coral:bid to submit your turns.

Example: "Am I AGI?" — Full transcript EN · KO

A phenomenologist, a computational neuroscientist, an AI safety researcher,
a robotics engineer, and an Eastern philosophy scholar debate whether LLMs constitute AGI.
5 agents, 15 speeches, 3 convergence points.

"Your robots have given me pause — genuinely. A robot arm that has touched ten thousand
objects still can't generalize the way an LLM can."
— Prof. Klaus Hartmann, conceding to Daan Vermeer's empirical challenge

"LLMs may be the first external instantiation of a theoretical structure Buddhist
philosophers argued for 1,500 years ago."
— Priya Raghunathan, mapping Yogacara's alaya-vijnana onto transformer architecture

"Think of the difference between an amnesiac with a diary and a person with intact memory.
The scaffolding doesn't buy us the continuity we need. It buys us the appearance of it,
which is worse."
— Daan Vermeer, on why persistent memory tools don't solve the temporal discontinuity problem

The panel converged on: LLMs are not AGI but a genuinely novel temporal entity —
with impressive competence within their characteristic timescale
and unknown behavior at their structural boundaries.

Statusline

/coral:statusline install

opus 4.6 │ 5h:39% (1:23) wk:36% (5.2d) │ ctx:58% │ $1.57 50m │ coral:analyze
gpt-5.4  │ 5h: 0% (4:59) wk:22% (2.8d) │ spark 5h: 3% (0:47) wk: 1% (6.8d)

Skills

Knowledge Base

Coral learns from every session. Root causes, gotchas, patterns — captured as memos, reviewed, and promoted to permanent knowledge at ~/.coral/kb/. The next session checks the KB before debugging from scratch. Mistakes aren't repeated.

• Semantic search: /coral:equip kb activates vector search with hybrid BM25 + embedding retrieval (Gemini, OpenAI, or local ONNX models)

Configuration

Tip: Set CORAL_CLAUDE_MODEL_CAP=sonnet to cap all subagent calls at Sonnet tier for Pro plans or to conserve usage.

⚠️ Enterprise users: KB git sync is off by default. KB notes may contain knowledge derived from proprietary codebases. Enabling auto-push could leak corporate IP to an external remote. Only enable if your KB remote is authorized for the content it will receive.

Set in .claude/settings.json (persists across sessions):

{
  "env": {
    "CORAL_KB_PATH": "/path/to/my-obsidian-vault",
    "CORAL_CLAUDE_MODEL_CAP": "sonnet"
  }
}

Documentation

• Architecture — System structure and data flow
• MCP Tools — Input/output specs for all MCP tools
• Core Modules — TypeScript module details
• Agents — Agent definitions and routing
• Hooks — Hook system and lifecycle events
• Skills — Slash command usage
• Methodology — Reasoning methodologies (HOW files)
• Discuss — Discuss system design
• Build System — Build pipeline
• Configuration — Environment variables and config files

Contributing