mcp-software-design 0.1.2 → 0.1.3

package/README.md

@@ -7,11 +7,12 @@
 
 An [MCP](https://modelcontextprotocol.io) server that teaches and helps apply
 **software-design guidance** — the SOLID principles, the OOP pillars, DRY /
-KISS / YAGNI / meaningful naming, and the 23 Gang-of-Four design patterns —
+KISS / YAGNI / meaningful naming / clean code, and the 23 Gang-of-Four design
+patterns —
 plus pattern scaffolding and heuristic code-smell detection.
 
 It's the companion to
-[`mcp-udacity-commit`](../mcp-udacity-commit): same stack (TypeScript, the MCP
+[`mcp-udacity-commit`](https://github.com/qwertymuzaffar/mcp-udacity-commit): same stack (TypeScript, the MCP
 SDK, stdio transport), same shape (pure logic modules + thin server wiring).
 
 ## Install
@@ -101,25 +102,14 @@ npm test           # builds, then runs the unit tests
 npm run test:client  # end-to-end check against the built server
 ```
 
-Then register the local build with Claude Code:
+Then register it the same way as [Install](#install) above — both the
+`claude mcp add` command and the MCP-client-config form work — but point at
+your local build instead of `npx`:
 
 ```bash
 claude mcp add software-design -- node /absolute/path/to/mcp-software-design/build/index.js
 ```
 
-Or in an MCP client config:
-
-```json
-{
-  "mcpServers": {
-    "software-design": {
-      "command": "node",
-      "args": ["/absolute/path/to/mcp-software-design/build/index.js"]
-    }
-  }
-}
-```
-
 ## Layout
 
 ```

package/build/catalog.js

@@ -189,6 +189,29 @@ export const PRINCIPLES = [
         ],
         related: ["kiss", "single-responsibility", "separation-of-concerns"],
     },
+    {
+        slug: "clean-code",
+        name: "Clean Code",
+        category: "principle",
+        aka: ["readability", "craftsmanship"],
+        summary: "Code is read far more than it's written — optimize for the reader.",
+        intent: "Clean Code is an umbrella habit, not a single rule: write code a later " +
+            "reader (usually you) can understand quickly and change safely. It's the " +
+            "sum of the concrete principles here — intention-revealing names, small " +
+            "single-purpose units, no duplication, and the simplest thing that works — " +
+            "rather than a separate technique of its own.",
+        whenToUse: [
+            "You hesitate to touch a file because you don't understand it.",
+            "Reviewers keep asking 'what does this do?' about the same code.",
+            "Reading the change takes longer than making it.",
+        ],
+        tradeoffs: [
+            "'Clean' is contextual — a throwaway script and a core library deserve different bars.",
+            "Endless renaming/extracting has diminishing returns; stop once it reads clearly.",
+            "Cleanliness is not correctness — clean code can still be wrong; tests decide behavior.",
+        ],
+        related: ["meaningful-names", "single-responsibility", "dry", "kiss"],
+    },
     {
         slug: "composition-over-inheritance",
         name: "Composition Over Inheritance",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mcp-software-design",
-  "version": "0.1.2",
+  "version": "0.1.3",
   "description": "MCP server that teaches and applies software-design guidance: SOLID/OOP/DRY principles, the 23 GoF design patterns, pattern scaffolding, and heuristic code-smell detection.",
   "type": "module",
   "license": "MIT",