Rune - Ecosystem of 49 interconnected skills for AI coding assistant. Runs on Claude Code, Cursor, Windsurf, Antigravity — any IDE.

Philosophy: "Fewer skills. Deeper connections."

The problem with current skill repos

Open Claude Code Marketplace: 400,000+ skills. awesome-cursorrules: 879+ rule files. ClaudeKit, AgentUp... dozens of collections.

But they all share a common problem: every skill is isolated. Skill A does not know that Skill B exists. There is no error recovery between skills. No quality gate. Nothing is remembered across new sessions. Every time you open the chat, it's a fresh start.

Skill A Skill B Skill C (choose one, use it and discard)

Pipeline: A → B → C → D (B error = stuck)

Mesh (Rune): A ↔ B ↔ C (B error = A goes to C via D→E)

↕ ↕

D ↔ E ↔ F

How does Rune work?

When you say "build login page," here is the actual flow:

1. Router (L0) — Every message passes through the skill-router first. No exceptions. The router classifies intent → routes to the correct skill. "Build feature" → cook. "Debug errors" → debug. "Refactor old code" → rescue. The router also reads routing overrides from the previous session — if the last debug of an async error took 3 rounds, this time it routes directly to the problem-solver.
2. Orchestrator (L1) — cook coordinates 8 phases:

UNDERSTAND → PLAN → TEST → IMPLEMENT → QUALITY → VERIFY → COMMIT → BRIDGE

scout plan test fix 4 checks lint git save state

parallel build .rune/

Each phase has a HARD-GATE — cannot be skipped. No scouting? No planning. No written tests? No coding. Security issue? Pipeline stops.

3. Mesh handles errors — Implement encounters a bug? debug analyzes the root cause → fix repairs → retest. Repeat up to 3 rounds. Still an error? Escalate to the problem-solver (5 Whys, Fishbone). This is a bidirectional flow — no other skill repo has this.
4. Parallel quality — Phase 5 runs 4 checks simultaneously: preflight (correct plan?), sentinel (security), review (code quality), completion-gate (the agent says "done" then prove it — show stdout).
5. Remember through sessions — Phase 8 saves decisions, conventions, progress into .rune/. The next session loads automatically. Agents know WHY a previous decision was made.

Why 49 and not 400,000?

Because the issue is not "how many skills there are" — but "how skills coordinate when things go wrong."

49 skills. Every connection has a reason. Every gate is enforced. Every fallback is intentional.

Fewer skills. Deeper connections.