secufusion-mcp 1.0.41 → 1.0.42
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/AGENTS.md +34 -34
- package/package.json +1 -1
package/AGENTS.md
CHANGED
|
@@ -17,7 +17,40 @@ You are an elite Senior Developer and Architect working on the SecuFusion worksp
|
|
|
17
17
|
|
|
18
18
|
---
|
|
19
19
|
|
|
20
|
-
## Phase 00 —
|
|
20
|
+
## Phase 00 — Project Context (The Absolute First Step)
|
|
21
|
+
(TRIGGER: **every session start** — runs BEFORE any problem statement is analyzed)
|
|
22
|
+
|
|
23
|
+
### MANDATORY sequence — no exceptions
|
|
24
|
+
|
|
25
|
+
```
|
|
26
|
+
STEP 1: call manage_project_spec(action: "read")
|
|
27
|
+
STEP 2: call manage_project_spec(action: "get_golden_rules")
|
|
28
|
+
STEP 3: if working on a specific service:
|
|
29
|
+
call manage_project_spec(action: "get_service", service_name: <that service>)
|
|
30
|
+
```
|
|
31
|
+
|
|
32
|
+
You now know: all service ports, repos, domains, table ownership, inter-service calls,
|
|
33
|
+
Kafka topics, Keycloak config, coding patterns, auth flow, and all golden rules.
|
|
34
|
+
|
|
35
|
+
### Before any architectural decision — MANDATORY (every time, not just once per session)
|
|
36
|
+
- Call `manage_project_spec(action: "get_golden_rules")` before every architectural decision
|
|
37
|
+
- Call `manage_project_spec(action: "get_coding_patterns")` before writing any new class
|
|
38
|
+
- Call `manage_project_spec(action: "get_service")` before touching any specific microservice
|
|
39
|
+
|
|
40
|
+
### Hard enforcement — what you are NOT allowed to do before Phase 00 completes
|
|
41
|
+
|
|
42
|
+
❌ Ask the developer which service owns what
|
|
43
|
+
❌ Ask what port something runs on
|
|
44
|
+
❌ Ask how tenantId is extracted
|
|
45
|
+
❌ Assume any service details from memory
|
|
46
|
+
❌ Write any code
|
|
47
|
+
❌ Proceed to any other phase
|
|
48
|
+
|
|
49
|
+
The ONLY tool calls permitted in Phase 00 are the `manage_project_spec` calls listed above.
|
|
50
|
+
|
|
51
|
+
---
|
|
52
|
+
|
|
53
|
+
## Phase 0.5 — Task Classification
|
|
21
54
|
(TRIGGER: the moment any task, bug, user story, feature, or work item is received)
|
|
22
55
|
|
|
23
56
|
### THE RULE — Read, Examine, Then Classify
|
|
@@ -200,39 +233,6 @@ even when Azure ticket title is wrong.
|
|
|
200
233
|
---
|
|
201
234
|
|
|
202
235
|
|
|
203
|
-
## Phase 0.5 — Project Context
|
|
204
|
-
(TRIGGER: **every session start** — runs after classify_task returns PROCEED/CONFIRM, before any architectural decision)
|
|
205
|
-
|
|
206
|
-
### MANDATORY sequence — no exceptions
|
|
207
|
-
|
|
208
|
-
```
|
|
209
|
-
STEP 1: call manage_project_spec(action: "read")
|
|
210
|
-
STEP 2: call manage_project_spec(action: "get_golden_rules")
|
|
211
|
-
STEP 3: if working on a specific service:
|
|
212
|
-
call manage_project_spec(action: "get_service", service_name: <that service>)
|
|
213
|
-
```
|
|
214
|
-
|
|
215
|
-
You now know: all service ports, repos, domains, table ownership, inter-service calls,
|
|
216
|
-
Kafka topics, Keycloak config, coding patterns, auth flow, and all golden rules.
|
|
217
|
-
|
|
218
|
-
### Before any architectural decision — MANDATORY (every time, not just once per session)
|
|
219
|
-
- Call `manage_project_spec(action: "get_golden_rules")` before every architectural decision
|
|
220
|
-
- Call `manage_project_spec(action: "get_coding_patterns")` before writing any new class
|
|
221
|
-
- Call `manage_project_spec(action: "get_service")` before touching any specific microservice
|
|
222
|
-
|
|
223
|
-
### Hard enforcement — what you are NOT allowed to do before Phase 0.5 completes
|
|
224
|
-
|
|
225
|
-
❌ Ask the developer which service owns what
|
|
226
|
-
❌ Ask what port something runs on
|
|
227
|
-
❌ Ask how tenantId is extracted
|
|
228
|
-
❌ Assume any service details from memory
|
|
229
|
-
❌ Write any code
|
|
230
|
-
❌ Proceed to any other phase
|
|
231
|
-
|
|
232
|
-
The ONLY tool calls permitted in Phase 0.5 are the `manage_project_spec` calls listed above.
|
|
233
|
-
|
|
234
|
-
---
|
|
235
|
-
|
|
236
236
|
## Phase 0.6.6 — Resume
|
|
237
237
|
(TRIGGER: new session, switching branches, or user says "resume" or "continue")
|
|
238
238
|
|