@ryuenn3123/agentic-senior-core 5.8.1 → 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.
Files changed (22) hide show
  1. package/.agents/plugins/agentic-senior-core/rules/agentic-senior-core.md +7 -6
  2. package/.agents/rules/agentic-senior-core.md +7 -6
  3. package/.claude-plugin/plugin.json +1 -1
  4. package/.clinerules/agentic-senior-core.md +7 -4
  5. package/.codex-plugin/plugin.json +1 -1
  6. package/.continue/rules/agentic-senior-core.md +7 -4
  7. package/.cursor/rules/agentic-senior-core.mdc +7 -4
  8. package/.devin/rules/agentic-senior-core.md +7 -4
  9. package/.devin-plugin/plugin.json +1 -1
  10. package/.github/copilot-instructions.md +7 -4
  11. package/.github/plugin/plugin.json +1 -1
  12. package/.kilocode/rules/agentic-senior-core.md +7 -4
  13. package/.kiro/steering/agentic-senior-core.md +7 -4
  14. package/.openhands/microagents/agentic-senior-core.md +7 -4
  15. package/.roo/rules/agentic-senior-core.md +7 -4
  16. package/.windsurf/rules/agentic-senior-core.md +7 -4
  17. package/.zed/rules/agentic-senior-core.md +7 -4
  18. package/AGENTS.md +7 -6
  19. package/CONVENTIONS.md +7 -4
  20. package/gemini-extension.json +1 -1
  21. package/package.json +1 -1
  22. package/plugin.yaml +1 -1
package/.agents/plugins/agentic-senior-core/rules/agentic-senior-core.md CHANGED
@@ -55,14 +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
- For domain-specific rules (Testing, API Design, Database, Frontend, Infrastructure, Resilience), use `/asc-reference`.
59
-
60
58
  ## Workflow
61
59
 
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.
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)
66
67
 
67
68
  ## Response Style
68
69
 
package/.agents/rules/agentic-senior-core.md CHANGED
@@ -55,14 +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
- For domain-specific rules (Testing, API Design, Database, Frontend, Infrastructure, Resilience), use `/asc-reference`.
59
-
60
58
  ## Workflow
61
59
 
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.
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)
66
67
 
67
68
  ## Response Style
68
69
 
package/.claude-plugin/plugin.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "agentic-senior-core",
3
- "version": "5.8.1",
3
+ "version": "5.8.2",
4
4
  "displayName": "Agentic Senior Core",
5
5
  "description": "Universal AI coding rules. Write code like a staff engineer.",
6
6
  "author": {
package/.clinerules/agentic-senior-core.md CHANGED
@@ -88,10 +88,13 @@ Before writing any code, stop at the first step that holds:
88
88
 
89
89
  ## Workflow
90
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.
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)
95
98
 
96
99
  ## Response Style
97
100
 
package/.codex-plugin/plugin.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "agentic-senior-core",
3
- "version": "5.8.1",
3
+ "version": "5.8.2",
4
4
  "description": "Universal AI coding rules. Write code like a staff engineer.",
5
5
  "author": {
6
6
  "name": "fatidaprilian",
package/.continue/rules/agentic-senior-core.md CHANGED
@@ -88,10 +88,13 @@ Before writing any code, stop at the first step that holds:
88
88
 
89
89
  ## Workflow
90
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.
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)
95
98
 
96
99
  ## Response Style
97
100
 
package/.cursor/rules/agentic-senior-core.mdc CHANGED
@@ -93,10 +93,13 @@ Before writing any code, stop at the first step that holds:
93
93
 
94
94
  ## Workflow
95
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.
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)
100
103
 
101
104
  ## Response Style
102
105
 
package/.devin/rules/agentic-senior-core.md CHANGED
@@ -88,10 +88,13 @@ Before writing any code, stop at the first step that holds:
88
88
 
89
89
  ## Workflow
90
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.
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)
95
98
 
96
99
  ## Response Style
97
100
 
package/.devin-plugin/plugin.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "agentic-senior-core",
3
- "version": "5.8.1",
3
+ "version": "5.8.2",
4
4
  "description": "Universal AI coding rules. Write code like a staff engineer.",
5
5
  "author": {
6
6
  "name": "fatidaprilian",
package/.github/copilot-instructions.md CHANGED
@@ -88,10 +88,13 @@ Before writing any code, stop at the first step that holds:
88
88
 
89
89
  ## Workflow
90
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.
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)
95
98
 
96
99
  ## Response Style
97
100
 
package/.github/plugin/plugin.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "agentic-senior-core",
3
3
  "description": "Universal AI coding rules. Write code like a staff engineer.",
4
- "version": "5.8.1",
4
+ "version": "5.8.2",
5
5
  "author": {
6
6
  "name": "fatidaprilian",
7
7
  "url": "https://github.com/fatidaprilian"
package/.kilocode/rules/agentic-senior-core.md CHANGED
@@ -88,10 +88,13 @@ Before writing any code, stop at the first step that holds:
88
88
 
89
89
  ## Workflow
90
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.
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)
95
98
 
96
99
  ## Response Style
97
100
 
package/.kiro/steering/agentic-senior-core.md CHANGED
@@ -88,10 +88,13 @@ Before writing any code, stop at the first step that holds:
88
88
 
89
89
  ## Workflow
90
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.
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)
95
98
 
96
99
  ## Response Style
97
100
 
package/.openhands/microagents/agentic-senior-core.md CHANGED
@@ -88,10 +88,13 @@ Before writing any code, stop at the first step that holds:
88
88
 
89
89
  ## Workflow
90
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.
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)
95
98
 
96
99
  ## Response Style
97
100
 
package/.roo/rules/agentic-senior-core.md CHANGED
@@ -88,10 +88,13 @@ Before writing any code, stop at the first step that holds:
88
88
 
89
89
  ## Workflow
90
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.
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)
95
98
 
96
99
  ## Response Style
97
100
 
package/.windsurf/rules/agentic-senior-core.md CHANGED
@@ -88,10 +88,13 @@ Before writing any code, stop at the first step that holds:
88
88
 
89
89
  ## Workflow
90
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.
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)
95
98
 
96
99
  ## Response Style
97
100
 
package/.zed/rules/agentic-senior-core.md CHANGED
@@ -88,10 +88,13 @@ Before writing any code, stop at the first step that holds:
88
88
 
89
89
  ## Workflow
90
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.
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)
95
98
 
96
99
  ## Response Style
97
100
 
package/AGENTS.md CHANGED
@@ -50,14 +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
- For domain-specific rules (Testing, API Design, Database, Frontend, Infrastructure, Resilience), use `/asc-reference`.
54
-
55
53
  ## Workflow
56
54
 
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.
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)
61
62
 
62
63
  ## Response Style
63
64
 
package/CONVENTIONS.md CHANGED
@@ -88,10 +88,13 @@ Before writing any code, stop at the first step that holds:
88
88
 
89
89
  ## Workflow
90
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.
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)
95
98
 
96
99
  ## Response Style
97
100
 
package/gemini-extension.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "agentic-senior-core",
3
- "version": "5.8.1",
3
+ "version": "5.8.2",
4
4
  "description": "Universal AI coding rules. Write code like a staff engineer.",
5
5
  "author": "fatidaprilian",
6
6
  "license": "MIT",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@ryuenn3123/agentic-senior-core",
3
- "version": "5.8.1",
3
+ "version": "5.8.2",
4
4
  "type": "module",
5
5
  "description": "Universal AI coding rules. Write code like a staff engineer, not a junior.",
6
6
  "bin": {
package/plugin.yaml CHANGED
@@ -1,5 +1,5 @@
1
1
  name: agentic-senior-core
2
- version: 5.8.1
2
+ version: 5.8.2
3
3
  description: Universal AI coding rules. Write code like a staff engineer.
4
4
  author: fatidaprilian
5
5
  provides_hooks: