📦 deps(skills): sync thirdparty skills

skills/thirdparty/brooks-audit/SKILL.md

@@ -16,10 +16,12 @@ description: >
 
 ## Setup
 
-1. Read `../_shared/common.md` for the Iron Law, Project Config, Report Template, and Health Score rules
-2. Read `../_shared/source-coverage.md` for book-level coverage, exceptions, and tradeoffs
-3. Read `../_shared/decay-risks.md` for symptom definitions and source attributions
-4. Read `architecture-guide.md` in this directory for the audit framework
+Read in order:
+
+1. `../_shared/common.md` — Iron Law, Project Config, Report Template, Health Score
+2. `../_shared/source-coverage.md` — book coverage, exceptions, tradeoffs
+3. `../_shared/decay-risks.md` — symptom definitions and source attributions
+4. `architecture-guide.md` (this directory) — the audit framework
 
 ## Process
 
@@ -28,8 +30,8 @@ description: >
 directory and follow it instead of `architecture-guide.md`. This mode explains rather
 than diagnoses — no Health Score, no Iron Law findings.
 
-**If the user has not specified files or a directory to audit:** apply Auto Scope
-Detection from `../_shared/common.md` to determine the audit scope before proceeding.
+**Scope:** if the user did not specify files or a directory, apply Auto Scope Detection
+(`../_shared/common.md`) first.
 
 1. Gather codebase context and draw the module dependency graph as Mermaid (Steps 0–1 of the guide)
 2. Scan for each decay risk in the order specified (Steps 2–4 of the guide)

skills/thirdparty/brooks-audit/architecture-guide.md

@@ -54,7 +54,6 @@ Before evaluating any risk, map the dependencies as a Mermaid diagram. Use this
 graph TD
   subgraph UI
     WebApp
-    MobileApp
   end
 
   subgraph Domain
@@ -65,16 +64,12 @@ graph TD
 
   subgraph Infrastructure
     Database
-    MessageQueue
   end
 
   WebApp --> AuthService
   WebApp --> OrderService
-  MobileApp --> AuthService
-  MobileApp --> OrderService
   OrderService --> PaymentService
   OrderService --> Database
-  OrderService --> MessageQueue
   PaymentService --> Database
   AuthService -.->|circular| OrderService
 
@@ -84,14 +79,11 @@ graph TD
 
   class PaymentService critical
   class OrderService warning
-  class Database,MessageQueue,AuthService,WebApp,MobileApp clean
+  class Database,AuthService,WebApp clean
 ````
 
-Draw the graph structure first — nodes, subgraphs, and edges — without any `classDef` or
-`class` lines. You cannot assign colors until you have completed the risk scan in Steps 2–4.
-
-**After completing Step 4**, return to this graph and add the `classDef` and `class` lines
-based on findings. The example above shows the final colored output.
+The example shows the final colored output. Draw nodes, subgraphs, and edges first; the
+`classDef` and `class` lines can only be written after the risk scan (Rule 6 below).
 
 Rules:
 1. **Nodes** — Use top-level directories or services as nodes, not individual files