john/claude-engineering-plugin
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Rename /codify to /compound and codify-docs to compound-docs

Browse Source 
The new names better reflect the compounding engineering philosophy:
each documented solution compounds your team's knowledge.

- /codify → /compound (old command shows deprecation notice)
- codify-docs → compound-docs skill
- Updated all docs, philosophy sections, and references

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
Kieran Klaassen
2025-11-27 14:13:00 -08:00
parent 852b0b8920
commit dbdd9c6676
15 changed files with 245 additions and 213 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
docs/index.html
View File

@@ -272,14 +272,14 @@
<div class="pillar">
<div class="pillar-icon"><i class="fa-solid fa-book"></i></div>
<div class="pillar-content">
<h3>Codify</h3>
<h3>Compound</h3>
<p class="pillar-tagline">Make sure you never solve the same bug twice</p>
<p class="pillar-description">
Remember that CORS issue you debugged for three hours last month? Neither do I. That's the problem. Run <code>/codify</code> right after you fix something and it captures the solution as searchable documentation with YAML frontmatter. Next time someone hits the same issue, they grep for "CORS production" and find your answer in five seconds instead of re-debugging for three hours. That's how you compound.
Remember that CORS issue you debugged for three hours last month? Neither do I. That's the problem. Run <code>/compound</code> right after you fix something and it captures the solution as searchable documentation with YAML frontmatter. Next time someone hits the same issue, they grep for "CORS production" and find your answer in five seconds instead of re-debugging for three hours. That's how you compound.
</p>
<div class="pillar-tools">
<span class="tool-tag">/codify</span>
<span class="tool-tag">codify-docs skill</span>
<span class="tool-tag">/compound</span>
<span class="tool-tag">compound-docs skill</span>
<span class="tool-tag">file-todos skill</span>
</div>
</div>
@@ -557,10 +557,10 @@
</div>
<div class="command-card">
<div class="command-header">
<code class="command-name">/codify</code>
<code class="command-name">/compound</code>
<span class="command-type-badge">core</span>
</div>
<p class="command-description">Document solved problems for the knowledge base. Turn learnings into reusable patterns.</p>
<p class="command-description">Document solved problems to compound team knowledge. Turn learnings into reusable patterns.</p>
</div>
</div>
</div>
@@ -736,11 +736,11 @@
</div>
<div class="skill-card">
<div class="skill-header">
<span class="skill-name">codify-docs</span>
<span class="skill-name">compound-docs</span>
<span class="skill-badge">Docs</span>
</div>
<p class="skill-description">Capture solved problems as categorized documentation with YAML schema.</p>
<code class="skill-usage">skill: codify-docs</code>
<code class="skill-usage">skill: compound-docs</code>
</div>
</div>
</div>

10
docs/pages/commands.html
View File

@@ -208,12 +208,12 @@
</div>
</div>
<div class="command-detail" id="workflows-codify">
<div class="command-detail" id="workflows-compound">
<div class="command-detail-header">
<code class="command-detail-name">/codify</code>
<code class="command-detail-name">/compound</code>
</div>
<p class="command-detail-description">
Just fixed a gnarly bug? This captures the solution before you forget it. Seven agents analyze what you did, why it worked, and how to prevent it next time. Your future self will thank you.
Just fixed a gnarly bug? This captures the solution before you forget it. Seven agents analyze what you did, why it worked, and how to prevent it next time. Each documented solution compounds your team's knowledge.
</p>
<h4>Arguments</h4>
<p><code>[optional: brief context about the fix]</code></p>
@@ -236,8 +236,8 @@
<h4>Auto-Triggers</h4>
<p>Phrases: "that worked", "it's fixed", "working now", "problem solved"</p>
<div class="card-code-block">
<pre><code>/codify
/codify N+1 query optimization</code></pre>
<pre><code>/compound
/compound N+1 query optimization</code></pre>
</div>
</div>
</section>

2
docs/pages/getting-started.html
View File

@@ -335,7 +335,7 @@ claude agent git-history-analyzer "Show changes to user model"</code></pre>
/plan
/review 123
/work
/codify
/compound
# Utility commands
/changelog

8
docs/pages/skills.html
View File

@@ -298,13 +298,13 @@ skill: create-agent-skills</code></pre>
</div>
</div>
<div class="skill-detail" id="codify-docs">
<div class="skill-detail" id="compound-docs">
<div class="skill-detail-header">
<h3>codify-docs</h3>
<h3>compound-docs</h3>
<span class="skill-badge">Docs</span>
</div>
<p class="skill-detail-description">
You just fixed a weird build error after an hour of debugging. Tomorrow you'll forget how you fixed it. This skill automatically detects when you solve something (phrases like "that worked" or "it's fixed") and documents it with YAML frontmatter so you can find it again. Think of it as a photographic memory for solved problems.
You just fixed a weird build error after an hour of debugging. Tomorrow you'll forget how you fixed it. This skill automatically detects when you solve something (phrases like "that worked" or "it's fixed") and documents it with YAML frontmatter so you can find it again. Each documented solution compounds your team's knowledge.
</p>
<h4>Auto-Triggers</h4>
<p>Phrases: "that worked", "it's fixed", "working now", "problem solved"</p>
@@ -328,7 +328,7 @@ skill: create-agent-skills</code></pre>
<li><code>security-issues/</code></li>
</ul>
<div class="card-code-block">
<pre><code>skill: codify-docs</code></pre>
<pre><code>skill: compound-docs</code></pre>
</div>
</div>
</section>