@ryuenn3123/agentic-senior-core 5.8.0 → 5.8.1
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 +7 -0
- package/.agents/rules/agentic-senior-core.md +7 -0
- package/.claude-plugin/plugin.json +1 -1
- package/.clinerules/agentic-senior-core.md +7 -0
- package/.codex-plugin/plugin.json +1 -1
- package/.continue/rules/agentic-senior-core.md +7 -0
- package/.cursor/rules/agentic-senior-core.mdc +7 -0
- package/.devin/rules/agentic-senior-core.md +7 -0
- package/.devin-plugin/plugin.json +1 -1
- package/.github/copilot-instructions.md +7 -0
- package/.github/plugin/plugin.json +1 -1
- package/.kilocode/rules/agentic-senior-core.md +7 -0
- package/.kiro/steering/agentic-senior-core.md +7 -0
- package/.openhands/microagents/agentic-senior-core.md +7 -0
- package/.roo/rules/agentic-senior-core.md +7 -0
- package/.windsurf/rules/agentic-senior-core.md +7 -0
- package/.zed/rules/agentic-senior-core.md +7 -0
- package/AGENTS.md +7 -0
- package/CONVENTIONS.md +7 -0
- package/gemini-extension.json +1 -1
- package/package.json +1 -1
- package/plugin.yaml +1 -1
|
@@ -57,6 +57,13 @@ Before writing any code, stop at the first step that holds:
|
|
|
57
57
|
|
|
58
58
|
For domain-specific rules (Testing, API Design, Database, Frontend, Infrastructure, Resilience), use `/asc-reference`.
|
|
59
59
|
|
|
60
|
+
## Workflow
|
|
61
|
+
|
|
62
|
+
Starting a project from scratch, or adding a non-trivial feature to an
|
|
63
|
+
existing codebase? Mention `/asc-new-project` or `/asc-add-feature` —
|
|
64
|
+
they set up a research/plan gate before implementation. Let the user
|
|
65
|
+
decide whether to invoke it. Skip this for trivial edits.
|
|
66
|
+
|
|
60
67
|
## Response Style
|
|
61
68
|
|
|
62
69
|
Lead with what the developer needs to act: the command, file path, code change, or decision point. Follow with context only when the action depends on it.
|
|
@@ -57,6 +57,13 @@ Before writing any code, stop at the first step that holds:
|
|
|
57
57
|
|
|
58
58
|
For domain-specific rules (Testing, API Design, Database, Frontend, Infrastructure, Resilience), use `/asc-reference`.
|
|
59
59
|
|
|
60
|
+
## Workflow
|
|
61
|
+
|
|
62
|
+
Starting a project from scratch, or adding a non-trivial feature to an
|
|
63
|
+
existing codebase? Mention `/asc-new-project` or `/asc-add-feature` —
|
|
64
|
+
they set up a research/plan gate before implementation. Let the user
|
|
65
|
+
decide whether to invoke it. Skip this for trivial edits.
|
|
66
|
+
|
|
60
67
|
## Response Style
|
|
61
68
|
|
|
62
69
|
Lead with what the developer needs to act: the command, file path, code change, or decision point. Follow with context only when the action depends on it.
|
|
@@ -86,6 +86,13 @@ 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
|
+
Starting a project from scratch, or adding a non-trivial feature to an
|
|
92
|
+
existing codebase? Mention `/asc-new-project` or `/asc-add-feature` —
|
|
93
|
+
they set up a research/plan gate before implementation. Let the user
|
|
94
|
+
decide whether to invoke it. Skip this for trivial edits.
|
|
95
|
+
|
|
89
96
|
## Response Style
|
|
90
97
|
|
|
91
98
|
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,13 @@ 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
|
+
Starting a project from scratch, or adding a non-trivial feature to an
|
|
92
|
+
existing codebase? Mention `/asc-new-project` or `/asc-add-feature` —
|
|
93
|
+
they set up a research/plan gate before implementation. Let the user
|
|
94
|
+
decide whether to invoke it. Skip this for trivial edits.
|
|
95
|
+
|
|
89
96
|
## Response Style
|
|
90
97
|
|
|
91
98
|
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,13 @@ 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
|
+
Starting a project from scratch, or adding a non-trivial feature to an
|
|
97
|
+
existing codebase? Mention `/asc-new-project` or `/asc-add-feature` —
|
|
98
|
+
they set up a research/plan gate before implementation. Let the user
|
|
99
|
+
decide whether to invoke it. Skip this for trivial edits.
|
|
100
|
+
|
|
94
101
|
## Response Style
|
|
95
102
|
|
|
96
103
|
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,13 @@ 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
|
+
Starting a project from scratch, or adding a non-trivial feature to an
|
|
92
|
+
existing codebase? Mention `/asc-new-project` or `/asc-add-feature` —
|
|
93
|
+
they set up a research/plan gate before implementation. Let the user
|
|
94
|
+
decide whether to invoke it. Skip this for trivial edits.
|
|
95
|
+
|
|
89
96
|
## Response Style
|
|
90
97
|
|
|
91
98
|
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,13 @@ 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
|
+
Starting a project from scratch, or adding a non-trivial feature to an
|
|
92
|
+
existing codebase? Mention `/asc-new-project` or `/asc-add-feature` —
|
|
93
|
+
they set up a research/plan gate before implementation. Let the user
|
|
94
|
+
decide whether to invoke it. Skip this for trivial edits.
|
|
95
|
+
|
|
89
96
|
## Response Style
|
|
90
97
|
|
|
91
98
|
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,13 @@ 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
|
+
Starting a project from scratch, or adding a non-trivial feature to an
|
|
92
|
+
existing codebase? Mention `/asc-new-project` or `/asc-add-feature` —
|
|
93
|
+
they set up a research/plan gate before implementation. Let the user
|
|
94
|
+
decide whether to invoke it. Skip this for trivial edits.
|
|
95
|
+
|
|
89
96
|
## Response Style
|
|
90
97
|
|
|
91
98
|
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,13 @@ 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
|
+
Starting a project from scratch, or adding a non-trivial feature to an
|
|
92
|
+
existing codebase? Mention `/asc-new-project` or `/asc-add-feature` —
|
|
93
|
+
they set up a research/plan gate before implementation. Let the user
|
|
94
|
+
decide whether to invoke it. Skip this for trivial edits.
|
|
95
|
+
|
|
89
96
|
## Response Style
|
|
90
97
|
|
|
91
98
|
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,13 @@ 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
|
+
Starting a project from scratch, or adding a non-trivial feature to an
|
|
92
|
+
existing codebase? Mention `/asc-new-project` or `/asc-add-feature` —
|
|
93
|
+
they set up a research/plan gate before implementation. Let the user
|
|
94
|
+
decide whether to invoke it. Skip this for trivial edits.
|
|
95
|
+
|
|
89
96
|
## Response Style
|
|
90
97
|
|
|
91
98
|
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,13 @@ 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
|
+
Starting a project from scratch, or adding a non-trivial feature to an
|
|
92
|
+
existing codebase? Mention `/asc-new-project` or `/asc-add-feature` —
|
|
93
|
+
they set up a research/plan gate before implementation. Let the user
|
|
94
|
+
decide whether to invoke it. Skip this for trivial edits.
|
|
95
|
+
|
|
89
96
|
## Response Style
|
|
90
97
|
|
|
91
98
|
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,13 @@ 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
|
+
Starting a project from scratch, or adding a non-trivial feature to an
|
|
92
|
+
existing codebase? Mention `/asc-new-project` or `/asc-add-feature` —
|
|
93
|
+
they set up a research/plan gate before implementation. Let the user
|
|
94
|
+
decide whether to invoke it. Skip this for trivial edits.
|
|
95
|
+
|
|
89
96
|
## Response Style
|
|
90
97
|
|
|
91
98
|
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,13 @@ 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
|
+
Starting a project from scratch, or adding a non-trivial feature to an
|
|
92
|
+
existing codebase? Mention `/asc-new-project` or `/asc-add-feature` —
|
|
93
|
+
they set up a research/plan gate before implementation. Let the user
|
|
94
|
+
decide whether to invoke it. Skip this for trivial edits.
|
|
95
|
+
|
|
89
96
|
## Response Style
|
|
90
97
|
|
|
91
98
|
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
|
@@ -52,6 +52,13 @@ Before writing any code, stop at the first step that holds:
|
|
|
52
52
|
|
|
53
53
|
For domain-specific rules (Testing, API Design, Database, Frontend, Infrastructure, Resilience), use `/asc-reference`.
|
|
54
54
|
|
|
55
|
+
## Workflow
|
|
56
|
+
|
|
57
|
+
Starting a project from scratch, or adding a non-trivial feature to an
|
|
58
|
+
existing codebase? Mention `/asc-new-project` or `/asc-add-feature` —
|
|
59
|
+
they set up a research/plan gate before implementation. Let the user
|
|
60
|
+
decide whether to invoke it. Skip this for trivial edits.
|
|
61
|
+
|
|
55
62
|
## Response Style
|
|
56
63
|
|
|
57
64
|
Lead with what the developer needs to act: the command, file path, code change, or decision point. Follow with context only when the action depends on it.
|
package/CONVENTIONS.md
CHANGED
|
@@ -86,6 +86,13 @@ 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
|
+
Starting a project from scratch, or adding a non-trivial feature to an
|
|
92
|
+
existing codebase? Mention `/asc-new-project` or `/asc-add-feature` —
|
|
93
|
+
they set up a research/plan gate before implementation. Let the user
|
|
94
|
+
decide whether to invoke it. Skip this for trivial edits.
|
|
95
|
+
|
|
89
96
|
## Response Style
|
|
90
97
|
|
|
91
98
|
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