upd feature trigger

home-claude/settings.json

@@ -50,7 +50,6 @@
     ],
     "defaultMode": "acceptEdits"
   },
-  "model": "sonnet",
   "enabledPlugins": {
     "csharp-lsp@claude-plugins-official": true,
     "frontend-design@claude-plugins-official": true,
@@ -62,7 +61,6 @@
   },
   "language": "German",
   "alwaysThinkingEnabled": true,
-  "effortLevel": "low",
   "mcpServers": {
     "playwright": {
       "command": "npx",
@@ -81,5 +79,6 @@
         "postgresql://krah:krah_dev_pw@localhost:5432/krah_prodb"
       ]
     }
-  }
+  },
+  "effortLevel": "high"
 }

memory/projects/ISMS-DB/MEMORY.md

@@ -1,5 +1,12 @@
 # ISMS-DB Project Memory
 
+## Feature-Session Workflow
+- `zum Feature [topic]` / `Feature [topic]` / `wir arbeiten an [topic]` → immediately read `docs/feature-[topic].md` (case-insensitive), summarize, confirm context
+- If not found: inform user, suggest creating it
+- Session end `aktualisiere deine Feature-Beschreibung` → update the doc with decisions/findings
+- Filename always: `docs/feature-[camelCase].md` (never without `feature-` prefix)
+- See: [feedback_feature_session_workflow.md](feedback_feature_session_workflow.md)
+
 ## Skill Triggers
 - "aktualisiere unser ISMS", "ISMS aktualisieren", "ISMS updaten" → ALWAYS invoke Skill `isms-update`
 - This skill runs: Fetch-Data.ps1 → edit JSON → Upload-Data.ps1

memory/projects/ISMS-DB/feedback_feature_session_workflow.md

@@ -0,0 +1,30 @@
+---
+name: Feature-Session Workflow
+description: Trigger and action rules for loading feature docs at session start
+type: feedback
+---
+
+## Feature-Session Workflow
+
+**TRIGGER** (any phrasing at session start that references a feature/topic):
+- `Feature [topic]`
+- `zum Feature [topic]`
+- `wir arbeiten an [topic]`
+- any similar phrasing indicating a feature or topic context
+
+**ACTION — always execute immediately on trigger:**
+1. Look for `docs/feature-[topic].md` in project root (case-insensitive match)
+2. If found: read it, confirm context loaded, summarize key points briefly
+3. If not found: inform user that no feature doc exists yet, suggest creating one
+
+**CRITICAL: Do NOT wait to be explicitly asked. Load the feature doc proactively.**
+
+When user says `aktualisiere deine Feature-Beschreibung` at session end:
+1. Locate the relevant `docs/feature-[topic].md`
+2. Update it with key insights, decisions, and findings from the current session
+3. Keep it structured: Goal, Context, Key Decisions, Open Questions, Progress
+
+File naming: `docs/feature-[featureName].md` (camelCase featureName, e.g. `feature-jobSystem.md`)
+
+**CRITICAL**: When creating a new feature doc, the filename MUST start with `feature-`.
+Never create docs like `jobSystem.md` or `job-system.md` — always `feature-jobSystem.md`.