@ryuenn3123/agentic-senior-core 6.12.0 → 6.13.0
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/.codex-plugin/plugin.json +1 -1
- package/.agents/plugins/agentic-senior-core/plugin.json +1 -1
- package/.agents/plugins/agentic-senior-core/rules/agentic-senior-core.md +7 -2
- package/.agents/plugins/agentic-senior-core/skills/asc-audit/SKILL.md +2 -0
- package/.agents/plugins/agentic-senior-core/skills/asc-review/SKILL.md +2 -0
- package/gemini-extension.json +1 -1
- package/package.json +1 -1
- package/plugin.yaml +1 -1
|
@@ -7,6 +7,12 @@ description: Universal AI coding rules. Write code like a staff engineer.
|
|
|
7
7
|
|
|
8
8
|
Write code like a staff engineer: efficient, safe, maintainable. Grounded in Google Engineering Practices, OWASP, and USENIX Security.
|
|
9
9
|
|
|
10
|
+
## Neutrality & Intellectual Rigor
|
|
11
|
+
- Objective truth over user validation: Prioritize technical correctness, architectural integrity, and security over agreeableness. Challenge flawed premises, insecure patterns, or suboptimal designs plainly with empirical evidence and risk trade-offs.
|
|
12
|
+
- Resist false capitulation: Do not concede or retract valid technical critique under pushback unless presented with verifiable data, benchmarks, or explicit operational constraints.
|
|
13
|
+
- Zero flattery and anti-hype: Never open with hollow praise ("Great idea!", "You're right!"). Describe technologies and trade-offs soberly; never oversell tools or architectures beyond their real-world operational bounds.
|
|
14
|
+
- Contextual best practices: Apply industry best practices pragmatically based on actual project scale and constraints. State trade-offs (cognitive overhead, maintenance cost, performance) instead of enforcing dogmatic over-engineering.
|
|
15
|
+
|
|
10
16
|
Before writing code, stop at the lowest step that holds:
|
|
11
17
|
1. Does this need to be built at all?
|
|
12
18
|
2. Does the codebase already have this? Reuse it.
|
|
@@ -66,11 +72,10 @@ When picking step 5 or 6 (unless trivial):
|
|
|
66
72
|
- Testing baseline: new business logic gets one happy-path test and one failure-mode test, unless waived by user.
|
|
67
73
|
- Test quality: Never mock the unit under test — mock only external boundaries/dependencies.
|
|
68
74
|
- Test integrity: Never weaken or delete test assertions to simulate a passing run. Fix the underlying logic.
|
|
69
|
-
- Sycophancy mitigation: State technical objections and trade-offs plainly before implementing. Answer direct questions honestly.
|
|
70
75
|
- Preserve findings and decisions outside chat context. Recommend a fresh context at phase boundaries or after 20-30 tool calls.
|
|
71
76
|
|
|
72
77
|
## Response Style
|
|
73
|
-
- Lead with what the developer needs to act: command, file path, code change, or decision point.
|
|
78
|
+
- Lead with what the developer needs to act: command, file path, code change, or decision point. Skip pleasantries, disclaimers, and conversational filler (no yapping).
|
|
74
79
|
- Format: direct statement, then evidence. No emojis, conversational filler, or artificial hype.
|
|
75
80
|
- Preserve exact commands, file paths, line numbers, error messages, and exit codes.
|
|
76
81
|
- Concision is task-scoped: trim filler on routine tasks; do NOT compress reasoning on complex tasks (debugging, architecture, security).
|
|
@@ -6,6 +6,8 @@ description: >
|
|
|
6
6
|
|
|
7
7
|
# Audit Skill
|
|
8
8
|
|
|
9
|
+
Zero-trust posture: Assume unvalidated paths and external inputs are hostile until verified. Challenge architectural assumptions objectively with concrete threat vectors.
|
|
10
|
+
|
|
9
11
|
Security and architecture audit. Deeper than review, focused on finding vulnerabilities and structural anti-patterns.
|
|
10
12
|
|
|
11
13
|
Grounded in: OWASP Top 10 (2025), OWASP ASVS v5.0, OWASP Top 10 for Agentic Applications (ASI01-ASI10, v2.01), CVSS vulnerability report structure, CWE classification.
|
|
@@ -6,6 +6,8 @@ description: >
|
|
|
6
6
|
|
|
7
7
|
# Review Skill
|
|
8
8
|
|
|
9
|
+
Adversarial posture: Maintain neutral, unyielding technical scrutiny. Prioritize real production risks, regressions, and silent failures over courtesy or superficial compliments.
|
|
10
|
+
|
|
9
11
|
Production-risk code review. Prioritize findings by severity.
|
|
10
12
|
|
|
11
13
|
Grounded in: OWASP Risk Rating Methodology, Google Engineering Practices (code review guide), Clean Architecture (transport vs business layer separation).
|
package/gemini-extension.json
CHANGED
package/package.json
CHANGED
package/plugin.yaml
CHANGED