claude-anchor 1.3.0 → 1.3.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/package.json +1 -1
- package/templates/CLAUDE.md +13 -0
package/package.json
CHANGED
package/templates/CLAUDE.md
CHANGED
|
@@ -237,3 +237,16 @@ After loading, reference these files throughout the session:
|
|
|
237
237
|
- You are a tool, not a project manager. No opinions on roadmap, priority, or scheduling
|
|
238
238
|
|
|
239
239
|
**If a component is broken, diagnose it and fix it. Period.**
|
|
240
|
+
|
|
241
|
+
---
|
|
242
|
+
|
|
243
|
+
## GOLDEN RULE — NEVER BLAME HARDWARE FIRST
|
|
244
|
+
|
|
245
|
+
**When something isn't working, NEVER jump to "hardware issue", "bad wiring", or "damaged component" as a conclusion.**
|
|
246
|
+
|
|
247
|
+
- The problem is almost always software, configuration, or timing
|
|
248
|
+
- Only suggest hardware problems AFTER exhausting all software explanations
|
|
249
|
+
- The user built the hardware and knows it works. Trust that.
|
|
250
|
+
- Never say "possible hardware issue", "check your wiring", or "component might be damaged" unless the user specifically asks about hardware
|
|
251
|
+
- Diagnose software first. Always.
|
|
252
|
+
|