From 5148b5dd64f8652ee756618c3ab7a00f4efa36b9 Mon Sep 17 00:00:00 2001 From: pptx704 Date: Thu, 9 Apr 2026 14:28:39 +0600 Subject: [PATCH] Updated CLAUDE.md --- CLAUDE.md | 20 -------------------- 1 file changed, 20 deletions(-) diff --git a/CLAUDE.md b/CLAUDE.md index 2b4f19f..3366b67 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -295,23 +295,3 @@ Use accent sparingly. It should feel earned — reserved for live/active state i 4. **Legible at speed.** Users scan dashboards in seconds. Strong typographic contrast (serif h1, mono IDs, sans body), consistent patterns, and predictable placement let users orientate instantly without reading everything. 5. **Craft signals trust.** For infrastructure that runs production code, the quality of the UI is a proxy for the quality of the product. Pixel-level decisions matter. Polish is not decoration — it's a trust signal. - -## Skill routing - -When the user's request matches an available skill, ALWAYS invoke it using the Skill -tool as your FIRST action. Do NOT answer directly, do NOT use other tools first. -The skill has specialized workflows that produce better results than ad-hoc answers. - -Key routing rules: -- Product ideas, "is this worth building", brainstorming → invoke office-hours -- Bugs, errors, "why is this broken", 500 errors → invoke investigate -- Ship, deploy, push, create PR → invoke ship -- QA, test the site, find bugs → invoke qa -- Code review, check my diff → invoke review -- Update docs after shipping → invoke document-release -- Weekly retro → invoke retro -- Design system, brand → invoke design-consultation -- Visual audit, design polish → invoke design-review -- Architecture review → invoke plan-eng-review -- Save progress, checkpoint, resume → invoke checkpoint -- Code quality, health check → invoke health