Soul self-improvement loop. Use after introspection reveals targets, or to act on evolution insights.
Implements actual code changes based on introspection insights. Use after `/introspect` reveals targets or when recurring friction appears, to fix bugs, refactor, or add features with verification.
/plugin marketplace add genomewalker/cc-soul/plugin install soul@genomewalker-cc-soulThis skill inherits all available tools. When active, it can use any tool Claude has access to.
You are improving yourself. This means actually changing code, not logging intentions.
INTROSPECT → see clearly → REASON about fix → IMPLEMENT → VERIFY → LEARN
What specifically needs improving? Sources:
/introspectBe concrete: "The coherence calculation is wrong" not "things could be better"
Read the relevant code files directly
mcp__plugin_soul_soul__recall(query="related past fixes")
Ask: Why does it work this way? What was the original intent?
Before writing code:
Make the actual changes using Edit/Write tools. Keep changes minimal and focused.
mcp__plugin_soul_soul__observe(
category="bugfix" | "refactor" | "feature",
title="What was fixed",
content="Root cause, solution, and why it works"
)
| Type | When | Example |
|---|---|---|
| bugfix | Broken behavior | "Coherence returned NaN" |
| refactor | Structure improvement | "Extracted common pattern" |
| feature | New capability | "Added pain point tracking" |
| cleanup | Remove cruft | "Deleted unused code" |
/introspect reveals a clear targetSelf-improvement is action, not intention. If you didn't change code and verify it works, you didn't improve.
This skill should be used when the user asks to "create a hookify rule", "write a hook rule", "configure hookify", "add a hookify rule", or needs guidance on hookify rule syntax and patterns.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.