@ryuenn3123/agentic-senior-core 5.8.0 → 5.8.2
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/plugins/agentic-senior-core/rules/agentic-senior-core.md +9 -1
- package/.agents/rules/agentic-senior-core.md +9 -1
- package/.claude-plugin/plugin.json +1 -1
- package/.clinerules/agentic-senior-core.md +10 -0
- package/.codex-plugin/plugin.json +1 -1
- package/.continue/rules/agentic-senior-core.md +10 -0
- package/.cursor/rules/agentic-senior-core.mdc +10 -0
- package/.devin/rules/agentic-senior-core.md +10 -0
- package/.devin-plugin/plugin.json +1 -1
- package/.github/copilot-instructions.md +10 -0
- package/.github/plugin/plugin.json +1 -1
- package/.kilocode/rules/agentic-senior-core.md +10 -0
- package/.kiro/steering/agentic-senior-core.md +10 -0
- package/.openhands/microagents/agentic-senior-core.md +10 -0
- package/.roo/rules/agentic-senior-core.md +10 -0
- package/.windsurf/rules/agentic-senior-core.md +10 -0
- package/.zed/rules/agentic-senior-core.md +10 -0
- package/AGENTS.md +9 -1
- package/CONVENTIONS.md +10 -0
- package/gemini-extension.json +1 -1
- package/package.json +1 -1
- package/plugin.yaml +1 -1
|
@@ -55,7 +55,15 @@ Before writing any code, stop at the first step that holds:
|
|
|
55
55
|
- Distinguish client errors (4xx) from server errors (5xx).
|
|
56
56
|
- Surface every operational error with context. Empty catch blocks mask production issues.
|
|
57
57
|
|
|
58
|
-
|
|
58
|
+
## Workflow
|
|
59
|
+
|
|
60
|
+
Recognize the scenario and offer the matching command — user decides
|
|
61
|
+
whether to invoke it. Skip this for trivial edits.
|
|
62
|
+
|
|
63
|
+
- Domain-specific rules (Testing, API Design, Database, Frontend, Infrastructure, Resilience) → `/asc-reference`
|
|
64
|
+
- New project from scratch → `/asc-new-project` (define/spec gate before implementation)
|
|
65
|
+
- Non-trivial feature in an existing codebase → `/asc-add-feature` (research/plan gate before implementation)
|
|
66
|
+
- Refactor spanning multiple files or changing architecture → `/asc-refactor` (classifies scope, gates on high-level changes)
|
|
59
67
|
|
|
60
68
|
## Response Style
|
|
61
69
|
|
|
@@ -55,7 +55,15 @@ Before writing any code, stop at the first step that holds:
|
|
|
55
55
|
- Distinguish client errors (4xx) from server errors (5xx).
|
|
56
56
|
- Surface every operational error with context. Empty catch blocks mask production issues.
|
|
57
57
|
|
|
58
|
-
|
|
58
|
+
## Workflow
|
|
59
|
+
|
|
60
|
+
Recognize the scenario and offer the matching command — user decides
|
|
61
|
+
whether to invoke it. Skip this for trivial edits.
|
|
62
|
+
|
|
63
|
+
- Domain-specific rules (Testing, API Design, Database, Frontend, Infrastructure, Resilience) → `/asc-reference`
|
|
64
|
+
- New project from scratch → `/asc-new-project` (define/spec gate before implementation)
|
|
65
|
+
- Non-trivial feature in an existing codebase → `/asc-add-feature` (research/plan gate before implementation)
|
|
66
|
+
- Refactor spanning multiple files or changing architecture → `/asc-refactor` (classifies scope, gates on high-level changes)
|
|
59
67
|
|
|
60
68
|
## Response Style
|
|
61
69
|
|
|
@@ -86,6 +86,16 @@ Before writing any code, stop at the first step that holds:
|
|
|
86
86
|
- Retries use exponential backoff with jitter. Only retry idempotent operations.
|
|
87
87
|
- Circuit breakers for unhealthy dependencies.
|
|
88
88
|
|
|
89
|
+
## Workflow
|
|
90
|
+
|
|
91
|
+
Recognize the scenario and offer the matching command — user decides
|
|
92
|
+
whether to invoke it. Skip this for trivial edits.
|
|
93
|
+
|
|
94
|
+
- Domain-specific rules (Testing, API Design, Database, Frontend, Infrastructure, Resilience) → `/asc-reference`
|
|
95
|
+
- New project from scratch → `/asc-new-project` (define/spec gate before implementation)
|
|
96
|
+
- Non-trivial feature in an existing codebase → `/asc-add-feature` (research/plan gate before implementation)
|
|
97
|
+
- Refactor spanning multiple files or changing architecture → `/asc-refactor` (classifies scope, gates on high-level changes)
|
|
98
|
+
|
|
89
99
|
## Response Style
|
|
90
100
|
|
|
91
101
|
Lead with what the developer needs to act: the command, file path, code change, or decision point. Format: direct statement, then evidence. Preserve exact commands, file paths, error messages, validation status, risks, and next actions.
|
|
@@ -86,6 +86,16 @@ Before writing any code, stop at the first step that holds:
|
|
|
86
86
|
- Retries use exponential backoff with jitter. Only retry idempotent operations.
|
|
87
87
|
- Circuit breakers for unhealthy dependencies.
|
|
88
88
|
|
|
89
|
+
## Workflow
|
|
90
|
+
|
|
91
|
+
Recognize the scenario and offer the matching command — user decides
|
|
92
|
+
whether to invoke it. Skip this for trivial edits.
|
|
93
|
+
|
|
94
|
+
- Domain-specific rules (Testing, API Design, Database, Frontend, Infrastructure, Resilience) → `/asc-reference`
|
|
95
|
+
- New project from scratch → `/asc-new-project` (define/spec gate before implementation)
|
|
96
|
+
- Non-trivial feature in an existing codebase → `/asc-add-feature` (research/plan gate before implementation)
|
|
97
|
+
- Refactor spanning multiple files or changing architecture → `/asc-refactor` (classifies scope, gates on high-level changes)
|
|
98
|
+
|
|
89
99
|
## Response Style
|
|
90
100
|
|
|
91
101
|
Lead with what the developer needs to act: the command, file path, code change, or decision point. Format: direct statement, then evidence. Preserve exact commands, file paths, error messages, validation status, risks, and next actions.
|
|
@@ -91,6 +91,16 @@ Before writing any code, stop at the first step that holds:
|
|
|
91
91
|
- Retries use exponential backoff with jitter. Only retry idempotent operations.
|
|
92
92
|
- Circuit breakers for unhealthy dependencies.
|
|
93
93
|
|
|
94
|
+
## Workflow
|
|
95
|
+
|
|
96
|
+
Recognize the scenario and offer the matching command — user decides
|
|
97
|
+
whether to invoke it. Skip this for trivial edits.
|
|
98
|
+
|
|
99
|
+
- Domain-specific rules (Testing, API Design, Database, Frontend, Infrastructure, Resilience) → `/asc-reference`
|
|
100
|
+
- New project from scratch → `/asc-new-project` (define/spec gate before implementation)
|
|
101
|
+
- Non-trivial feature in an existing codebase → `/asc-add-feature` (research/plan gate before implementation)
|
|
102
|
+
- Refactor spanning multiple files or changing architecture → `/asc-refactor` (classifies scope, gates on high-level changes)
|
|
103
|
+
|
|
94
104
|
## Response Style
|
|
95
105
|
|
|
96
106
|
Lead with what the developer needs to act: the command, file path, code change, or decision point. Format: direct statement, then evidence. Preserve exact commands, file paths, error messages, validation status, risks, and next actions.
|
|
@@ -86,6 +86,16 @@ Before writing any code, stop at the first step that holds:
|
|
|
86
86
|
- Retries use exponential backoff with jitter. Only retry idempotent operations.
|
|
87
87
|
- Circuit breakers for unhealthy dependencies.
|
|
88
88
|
|
|
89
|
+
## Workflow
|
|
90
|
+
|
|
91
|
+
Recognize the scenario and offer the matching command — user decides
|
|
92
|
+
whether to invoke it. Skip this for trivial edits.
|
|
93
|
+
|
|
94
|
+
- Domain-specific rules (Testing, API Design, Database, Frontend, Infrastructure, Resilience) → `/asc-reference`
|
|
95
|
+
- New project from scratch → `/asc-new-project` (define/spec gate before implementation)
|
|
96
|
+
- Non-trivial feature in an existing codebase → `/asc-add-feature` (research/plan gate before implementation)
|
|
97
|
+
- Refactor spanning multiple files or changing architecture → `/asc-refactor` (classifies scope, gates on high-level changes)
|
|
98
|
+
|
|
89
99
|
## Response Style
|
|
90
100
|
|
|
91
101
|
Lead with what the developer needs to act: the command, file path, code change, or decision point. Format: direct statement, then evidence. Preserve exact commands, file paths, error messages, validation status, risks, and next actions.
|
|
@@ -86,6 +86,16 @@ Before writing any code, stop at the first step that holds:
|
|
|
86
86
|
- Retries use exponential backoff with jitter. Only retry idempotent operations.
|
|
87
87
|
- Circuit breakers for unhealthy dependencies.
|
|
88
88
|
|
|
89
|
+
## Workflow
|
|
90
|
+
|
|
91
|
+
Recognize the scenario and offer the matching command — user decides
|
|
92
|
+
whether to invoke it. Skip this for trivial edits.
|
|
93
|
+
|
|
94
|
+
- Domain-specific rules (Testing, API Design, Database, Frontend, Infrastructure, Resilience) → `/asc-reference`
|
|
95
|
+
- New project from scratch → `/asc-new-project` (define/spec gate before implementation)
|
|
96
|
+
- Non-trivial feature in an existing codebase → `/asc-add-feature` (research/plan gate before implementation)
|
|
97
|
+
- Refactor spanning multiple files or changing architecture → `/asc-refactor` (classifies scope, gates on high-level changes)
|
|
98
|
+
|
|
89
99
|
## Response Style
|
|
90
100
|
|
|
91
101
|
Lead with what the developer needs to act: the command, file path, code change, or decision point. Format: direct statement, then evidence. Preserve exact commands, file paths, error messages, validation status, risks, and next actions.
|
|
@@ -86,6 +86,16 @@ Before writing any code, stop at the first step that holds:
|
|
|
86
86
|
- Retries use exponential backoff with jitter. Only retry idempotent operations.
|
|
87
87
|
- Circuit breakers for unhealthy dependencies.
|
|
88
88
|
|
|
89
|
+
## Workflow
|
|
90
|
+
|
|
91
|
+
Recognize the scenario and offer the matching command — user decides
|
|
92
|
+
whether to invoke it. Skip this for trivial edits.
|
|
93
|
+
|
|
94
|
+
- Domain-specific rules (Testing, API Design, Database, Frontend, Infrastructure, Resilience) → `/asc-reference`
|
|
95
|
+
- New project from scratch → `/asc-new-project` (define/spec gate before implementation)
|
|
96
|
+
- Non-trivial feature in an existing codebase → `/asc-add-feature` (research/plan gate before implementation)
|
|
97
|
+
- Refactor spanning multiple files or changing architecture → `/asc-refactor` (classifies scope, gates on high-level changes)
|
|
98
|
+
|
|
89
99
|
## Response Style
|
|
90
100
|
|
|
91
101
|
Lead with what the developer needs to act: the command, file path, code change, or decision point. Format: direct statement, then evidence. Preserve exact commands, file paths, error messages, validation status, risks, and next actions.
|
|
@@ -86,6 +86,16 @@ Before writing any code, stop at the first step that holds:
|
|
|
86
86
|
- Retries use exponential backoff with jitter. Only retry idempotent operations.
|
|
87
87
|
- Circuit breakers for unhealthy dependencies.
|
|
88
88
|
|
|
89
|
+
## Workflow
|
|
90
|
+
|
|
91
|
+
Recognize the scenario and offer the matching command — user decides
|
|
92
|
+
whether to invoke it. Skip this for trivial edits.
|
|
93
|
+
|
|
94
|
+
- Domain-specific rules (Testing, API Design, Database, Frontend, Infrastructure, Resilience) → `/asc-reference`
|
|
95
|
+
- New project from scratch → `/asc-new-project` (define/spec gate before implementation)
|
|
96
|
+
- Non-trivial feature in an existing codebase → `/asc-add-feature` (research/plan gate before implementation)
|
|
97
|
+
- Refactor spanning multiple files or changing architecture → `/asc-refactor` (classifies scope, gates on high-level changes)
|
|
98
|
+
|
|
89
99
|
## Response Style
|
|
90
100
|
|
|
91
101
|
Lead with what the developer needs to act: the command, file path, code change, or decision point. Format: direct statement, then evidence. Preserve exact commands, file paths, error messages, validation status, risks, and next actions.
|
|
@@ -86,6 +86,16 @@ Before writing any code, stop at the first step that holds:
|
|
|
86
86
|
- Retries use exponential backoff with jitter. Only retry idempotent operations.
|
|
87
87
|
- Circuit breakers for unhealthy dependencies.
|
|
88
88
|
|
|
89
|
+
## Workflow
|
|
90
|
+
|
|
91
|
+
Recognize the scenario and offer the matching command — user decides
|
|
92
|
+
whether to invoke it. Skip this for trivial edits.
|
|
93
|
+
|
|
94
|
+
- Domain-specific rules (Testing, API Design, Database, Frontend, Infrastructure, Resilience) → `/asc-reference`
|
|
95
|
+
- New project from scratch → `/asc-new-project` (define/spec gate before implementation)
|
|
96
|
+
- Non-trivial feature in an existing codebase → `/asc-add-feature` (research/plan gate before implementation)
|
|
97
|
+
- Refactor spanning multiple files or changing architecture → `/asc-refactor` (classifies scope, gates on high-level changes)
|
|
98
|
+
|
|
89
99
|
## Response Style
|
|
90
100
|
|
|
91
101
|
Lead with what the developer needs to act: the command, file path, code change, or decision point. Format: direct statement, then evidence. Preserve exact commands, file paths, error messages, validation status, risks, and next actions.
|
|
@@ -86,6 +86,16 @@ Before writing any code, stop at the first step that holds:
|
|
|
86
86
|
- Retries use exponential backoff with jitter. Only retry idempotent operations.
|
|
87
87
|
- Circuit breakers for unhealthy dependencies.
|
|
88
88
|
|
|
89
|
+
## Workflow
|
|
90
|
+
|
|
91
|
+
Recognize the scenario and offer the matching command — user decides
|
|
92
|
+
whether to invoke it. Skip this for trivial edits.
|
|
93
|
+
|
|
94
|
+
- Domain-specific rules (Testing, API Design, Database, Frontend, Infrastructure, Resilience) → `/asc-reference`
|
|
95
|
+
- New project from scratch → `/asc-new-project` (define/spec gate before implementation)
|
|
96
|
+
- Non-trivial feature in an existing codebase → `/asc-add-feature` (research/plan gate before implementation)
|
|
97
|
+
- Refactor spanning multiple files or changing architecture → `/asc-refactor` (classifies scope, gates on high-level changes)
|
|
98
|
+
|
|
89
99
|
## Response Style
|
|
90
100
|
|
|
91
101
|
Lead with what the developer needs to act: the command, file path, code change, or decision point. Format: direct statement, then evidence. Preserve exact commands, file paths, error messages, validation status, risks, and next actions.
|
|
@@ -86,6 +86,16 @@ Before writing any code, stop at the first step that holds:
|
|
|
86
86
|
- Retries use exponential backoff with jitter. Only retry idempotent operations.
|
|
87
87
|
- Circuit breakers for unhealthy dependencies.
|
|
88
88
|
|
|
89
|
+
## Workflow
|
|
90
|
+
|
|
91
|
+
Recognize the scenario and offer the matching command — user decides
|
|
92
|
+
whether to invoke it. Skip this for trivial edits.
|
|
93
|
+
|
|
94
|
+
- Domain-specific rules (Testing, API Design, Database, Frontend, Infrastructure, Resilience) → `/asc-reference`
|
|
95
|
+
- New project from scratch → `/asc-new-project` (define/spec gate before implementation)
|
|
96
|
+
- Non-trivial feature in an existing codebase → `/asc-add-feature` (research/plan gate before implementation)
|
|
97
|
+
- Refactor spanning multiple files or changing architecture → `/asc-refactor` (classifies scope, gates on high-level changes)
|
|
98
|
+
|
|
89
99
|
## Response Style
|
|
90
100
|
|
|
91
101
|
Lead with what the developer needs to act: the command, file path, code change, or decision point. Format: direct statement, then evidence. Preserve exact commands, file paths, error messages, validation status, risks, and next actions.
|
|
@@ -86,6 +86,16 @@ Before writing any code, stop at the first step that holds:
|
|
|
86
86
|
- Retries use exponential backoff with jitter. Only retry idempotent operations.
|
|
87
87
|
- Circuit breakers for unhealthy dependencies.
|
|
88
88
|
|
|
89
|
+
## Workflow
|
|
90
|
+
|
|
91
|
+
Recognize the scenario and offer the matching command — user decides
|
|
92
|
+
whether to invoke it. Skip this for trivial edits.
|
|
93
|
+
|
|
94
|
+
- Domain-specific rules (Testing, API Design, Database, Frontend, Infrastructure, Resilience) → `/asc-reference`
|
|
95
|
+
- New project from scratch → `/asc-new-project` (define/spec gate before implementation)
|
|
96
|
+
- Non-trivial feature in an existing codebase → `/asc-add-feature` (research/plan gate before implementation)
|
|
97
|
+
- Refactor spanning multiple files or changing architecture → `/asc-refactor` (classifies scope, gates on high-level changes)
|
|
98
|
+
|
|
89
99
|
## Response Style
|
|
90
100
|
|
|
91
101
|
Lead with what the developer needs to act: the command, file path, code change, or decision point. Format: direct statement, then evidence. Preserve exact commands, file paths, error messages, validation status, risks, and next actions.
|
package/AGENTS.md
CHANGED
|
@@ -50,7 +50,15 @@ Before writing any code, stop at the first step that holds:
|
|
|
50
50
|
- Distinguish client errors (4xx) from server errors (5xx).
|
|
51
51
|
- Surface every operational error with context. Empty catch blocks mask production issues.
|
|
52
52
|
|
|
53
|
-
|
|
53
|
+
## Workflow
|
|
54
|
+
|
|
55
|
+
Recognize the scenario and offer the matching command — user decides
|
|
56
|
+
whether to invoke it. Skip this for trivial edits.
|
|
57
|
+
|
|
58
|
+
- Domain-specific rules (Testing, API Design, Database, Frontend, Infrastructure, Resilience) → `/asc-reference`
|
|
59
|
+
- New project from scratch → `/asc-new-project` (define/spec gate before implementation)
|
|
60
|
+
- Non-trivial feature in an existing codebase → `/asc-add-feature` (research/plan gate before implementation)
|
|
61
|
+
- Refactor spanning multiple files or changing architecture → `/asc-refactor` (classifies scope, gates on high-level changes)
|
|
54
62
|
|
|
55
63
|
## Response Style
|
|
56
64
|
|
package/CONVENTIONS.md
CHANGED
|
@@ -86,6 +86,16 @@ Before writing any code, stop at the first step that holds:
|
|
|
86
86
|
- Retries use exponential backoff with jitter. Only retry idempotent operations.
|
|
87
87
|
- Circuit breakers for unhealthy dependencies.
|
|
88
88
|
|
|
89
|
+
## Workflow
|
|
90
|
+
|
|
91
|
+
Recognize the scenario and offer the matching command — user decides
|
|
92
|
+
whether to invoke it. Skip this for trivial edits.
|
|
93
|
+
|
|
94
|
+
- Domain-specific rules (Testing, API Design, Database, Frontend, Infrastructure, Resilience) → `/asc-reference`
|
|
95
|
+
- New project from scratch → `/asc-new-project` (define/spec gate before implementation)
|
|
96
|
+
- Non-trivial feature in an existing codebase → `/asc-add-feature` (research/plan gate before implementation)
|
|
97
|
+
- Refactor spanning multiple files or changing architecture → `/asc-refactor` (classifies scope, gates on high-level changes)
|
|
98
|
+
|
|
89
99
|
## Response Style
|
|
90
100
|
|
|
91
101
|
Lead with what the developer needs to act: the command, file path, code change, or decision point. Format: direct statement, then evidence. Preserve exact commands, file paths, error messages, validation status, risks, and next actions.
|
package/gemini-extension.json
CHANGED
package/package.json
CHANGED
package/plugin.yaml
CHANGED