sad-mcp 2.2.2 → 2.2.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "sad-mcp",
-  "version": "2.2.2",
+  "version": "2.2.4",
   "description": "MCP server for Software Analysis and Design course materials at BGU",
   "type": "module",
   "bin": {

package/skills/uml-use-case-diagram/SKILL.md

@@ -31,7 +31,7 @@ The shared files prepended to this prompt define the layout recipes, model shape
 8. **UC labels describe actions WITH the information system, not physical real-world actions.** See §3 for the full rule and verb list.
 9. **Every system-time / cron actor association MUST carry a timing label** (e.g., "פעם ביום", "כל 5 דקות"). See §2 and §8 for rendering.
 10. **No "send-only" use cases.** If a UC's entire behavior is sending a message / notification / alert / email / SMS, it is not a UC — it is a step inside the UC that *decided* to send it. See §3.
-11. **All narrative UC documentation must be in Hebrew.** Description, preconditions, postconditions, every scenario flow-step text and extension text, user stories (role / want / so), assumptions, and open questions must all contain Hebrew. Identifier strings (`id`, `primaryActor: 'customer'`) stay ASCII. The validator (§12) rejects narrative fields that contain zero Hebrew characters.
+11. **All narrative UC documentation must be in Hebrew.** Description, preconditions, postconditions, every scenario flow-step text and extension text, user stories (`role` / `want` / `so` fields), assumptions, and open questions must all be written in Hebrew. User stories are rendered as "בתור [role], אני רוצה [want], כדי ש[so]" — write the field values in Hebrew accordingly. Identifier strings (`id`, `primaryActor: 'customer'`) stay ASCII. The validator (§12) rejects narrative fields that contain zero Hebrew characters.
 
 ---
 
@@ -162,20 +162,28 @@ UC documentation: [uc-id]
     - ___________________
 
   scenarios:
-    - id: sc-happy, name: "מסלול מרכזי (Happy Path)"
+    - id: sc-happy, name: "מסלול מרכזי"
       flow:
         1. [actor:primaryActor] ___________________
         2. [system] ___________________
         3. [include:uc-xxx]    ___________________    (only if §4.2 gate passed)
         4. [actor:secondary]   ___________________
-      extensions:
-        2a. if ___________ then ___________
-        4a. if ___________ then ___________
-    - id: sc-alt-1, name: "מסלול חלופי: ___" (optional additional scenarios)
+      extensions:                                     (error/exception handling — one per step where failure is realistic)
+        2a. אם ___________ — המערכת ___________ (e.g. wrong input, not found, timeout)
+        4a. אם ___________ — המערכת ___________
+
+    Additional scenarios — add one when the SAME GOAL is achieved via a meaningfully different PATH or TRIGGER.
+    Rule: same "what", different "how" or different starting condition → new scenario.
+    Examples: "רישום רגיל" vs "רישום מאוחר עם קנס"; "תשלום בכרטיס" vs "תשלום בקופון".
+    Do NOT add a scenario just for a different error outcome — that belongs in extensions of the main scenario.
+
+    - id: sc-alt-1, name: "מסלול חלופי: ___"
+      flow: ...
+      extensions: ...
 
   userStories:   (as many as the UC warrants — one per distinct stakeholder need; not a fixed number)
-    - As a [role], I want [want], so that [benefit].
-    - As a [different role OR same role different goal], I want [...], so that [...].
+    - בתור [תפקיד], אני רוצה [מה], כדי ש[למה].
+    - בתור [תפקיד שונה או אותו תפקיד עם מטרה שונה], אני רוצה [...], כדי ש[...].
     - ... (keep adding until every user-facing goal tied to this UC is represented)
 
   wireframe?:  (optional — only where the UC benefits from a UI mock; see §WF)
@@ -235,6 +243,35 @@ endpoint = { x: cx + rx * Math.cos(angle), y: cy + ry * Math.sin(angle) };
 
 **No legend.** Do not add a legend bar to the diagram.
 
+### «include» / «extend» arrow template
+
+Define markers once in `<defs>` using `<polyline>` (NOT `<polygon>` — polygon closes the triangle, producing a double-headed appearance):
+
+```svg
+<defs>
+  <marker id="arrow-include" markerWidth="10" markerHeight="7" refX="9" refY="3.5" orient="auto">
+    <polyline points="0 0, 9 3.5, 0 7" fill="none" stroke="#7c3aed" stroke-width="1.2"/>
+  </marker>
+  <marker id="arrow-extend" markerWidth="10" markerHeight="7" refX="9" refY="3.5" orient="auto">
+    <polyline points="0 0, 9 3.5, 0 7" fill="none" stroke="#7c3aed" stroke-width="1.2"/>
+  </marker>
+</defs>
+```
+
+For each «include»/«extend» line, add a `<text>` with `data-label-for="{from-id} {to-id}"` — `fixLayout` reads this and repositions the label to the line midpoint automatically:
+
+```svg
+<line data-conn-from="uc-a" data-conn-to="uc-b"
+      x1="0" y1="0" x2="0" y2="0"
+      stroke="#7c3aed" stroke-width="1.6" stroke-dasharray="6 4"
+      marker-end="url(#arrow-include)"/>
+<text data-label-for="uc-a uc-b" x="0" y="0"
+      text-anchor="middle" font-size="9.5" fill="#7c3aed"
+      font-family="'IBM Plex Mono',monospace">«include»</text>
+```
+
+**Never write `«include target»` or any annotation inside a UC ellipse group.**
+
 ---
 
 ## 6. Layout
@@ -541,8 +578,8 @@ const useCaseDocs = {
       }
     ],
     userStories: [
-      { role: 'לקוח', want: 'להזמין מוצר במהירות', so: 'שאקבל אותו תוך 48 שעות.' }
-    ],
+      { role: 'לקוח', want: 'להזמין מוצר במהירות', so: 'שאקבל אותו תוך 48 שעות' }
+    ],    // rendered as: "בתור לקוח, אני רוצה להזמין מוצר במהירות, כדי ששאקבל אותו תוך 48 שעות"
     wireframe: ''   // optional per §WF
   }
   // ... one entry per UC