@ryuenn3123/agentic-senior-core 2.0.3 → 2.0.5

package/.agent-context/skills/fullstack/feature-slicing.md

@@ -1,65 +1,65 @@
-# Feature Slicing
-
-Tier: ADVANCE
-
-Feature slicing organizes implementation around business capabilities instead of technical file types. A single feature owns its UI, service orchestration, persistence adapters, and tests.
-
-## Why It Matters
-
-- Improves ownership: one team can ship and maintain a feature end to end.
-- Reduces coupling: changes stay local to one capability.
-- Speeds delivery: less coordination across unrelated folders.
-
-## Recommended Layout
-
-```text
-src/
-	features/
-		checkout/
-			ui/
-			service/
-			repository/
-			contracts/
-			tests/
-			index.ts
-		orders/
-			ui/
-			service/
-			repository/
-			contracts/
-			tests/
-			index.ts
-```
-
-## Module Boundary Rules
-
-- Expose only through `index.ts` as the feature public API.
-- Do not import private files across feature folders.
-- Keep shared utilities in a neutral shared module; avoid feature-to-feature deep imports.
-
-## Anti-Patterns
-
-Bad:
-- `src/components`, `src/services`, `src/repositories` global buckets for all features.
-- Shared folder becoming a dumping ground for feature-specific code.
-- One feature mutating another feature's database entities directly.
-
-Good:
-- Feature package exposes explicit use-cases and UI entrypoints.
-- Cross-feature communication uses contracts and events.
-- Shared module limited to stateless primitives and infrastructure adapters.
-
-## Integration Workflow
-
-1. Define capability and boundary (example: checkout).
-2. Define public API for the feature module.
-3. Implement UI and service logic inside the feature.
-4. Add repository and contract definitions.
-5. Add unit/integration/end-to-end tests within the feature.
-
-## Review Checklist
-
-- [ ] Feature can be understood without reading unrelated modules.
-- [ ] No deep import across feature boundaries.
-- [ ] Public API is explicit and stable.
+# Feature Slicing
+
+Tier: ADVANCE
+
+Feature slicing organizes implementation around business capabilities instead of technical file types. A single feature owns its UI, service orchestration, persistence adapters, and tests.
+
+## Why It Matters
+
+- Improves ownership: one team can ship and maintain a feature end to end.
+- Reduces coupling: changes stay local to one capability.
+- Speeds delivery: less coordination across unrelated folders.
+
+## Recommended Layout
+
+```text
+src/
+	features/
+		checkout/
+			ui/
+			service/
+			repository/
+			contracts/
+			tests/
+			index.ts
+		orders/
+			ui/
+			service/
+			repository/
+			contracts/
+			tests/
+			index.ts
+```
+
+## Module Boundary Rules
+
+- Expose only through `index.ts` as the feature public API.
+- Do not import private files across feature folders.
+- Keep shared utilities in a neutral shared module; avoid feature-to-feature deep imports.
+
+## Anti-Patterns
+
+Bad:
+- `src/components`, `src/services`, `src/repositories` global buckets for all features.
+- Shared folder becoming a dumping ground for feature-specific code.
+- One feature mutating another feature's database entities directly.
+
+Good:
+- Feature package exposes explicit use-cases and UI entrypoints.
+- Cross-feature communication uses contracts and events.
+- Shared module limited to stateless primitives and infrastructure adapters.
+
+## Integration Workflow
+
+1. Define capability and boundary (example: checkout).
+2. Define public API for the feature module.
+3. Implement UI and service logic inside the feature.
+4. Add repository and contract definitions.
+5. Add unit/integration/end-to-end tests within the feature.
+
+## Review Checklist
+
+- [ ] Feature can be understood without reading unrelated modules.
+- [ ] No deep import across feature boundaries.
+- [ ] Public API is explicit and stable.
 - [ ] Tests live with the feature and cover core behavior.

package/.agent-context/skills/fullstack.md

@@ -1,27 +1,27 @@
-# Fullstack Skill Pack
-
-Default tier: `advance`
-
-## Purpose
-Coordinate frontend and backend delivery as a single product system.
-
-## In Scope
-- Feature slicing across UI and API boundaries
-- Shared validation contracts
-- End-to-end flows and release readiness
-- Performance, accessibility, and observability together
-
-## Must-Have Checks
-- Single feature directory with clear public API
-- Frontend and backend contracts aligned
-- End-to-end test coverage for critical paths
-- Release notes explain UX and API impact together
-
-## Evidence
-- Feature parity checklist
-- End-to-end test report
-- Contract validation output
-- Release artifact bundle
-
-## Fallback
+# Fullstack Skill Pack
+
+Default tier: `advance`
+
+## Purpose
+Coordinate frontend and backend delivery as a single product system.
+
+## In Scope
+- Feature slicing across UI and API boundaries
+- Shared validation contracts
+- End-to-end flows and release readiness
+- Performance, accessibility, and observability together
+
+## Must-Have Checks
+- Single feature directory with clear public API
+- Frontend and backend contracts aligned
+- End-to-end test coverage for critical paths
+- Release notes explain UX and API impact together
+
+## Evidence
+- Feature parity checklist
+- End-to-end test report
+- Contract validation output
+- Release artifact bundle
+
+## Fallback
 - Split delivery only when the feature boundary is explicit and the evidence bundle is still complete.

package/.agent-context/skills/index.json

@@ -1,107 +1,107 @@
-{
-  "defaultTier": "advance",
-  "tiers": [
-    {
-      "name": "standard",
-      "description": "Compatibility fallback only"
-    },
-    {
-      "name": "advance",
-      "description": "Default operating tier"
-    },
-    {
-      "name": "expert",
-      "description": "Complex architecture and integration"
-    },
-    {
-      "name": "above",
-      "description": "Release-critical enterprise governance"
-    }
-  ],
-  "domains": {
-    "frontend": {
-      "name": "frontend",
-      "displayName": "Frontend",
-      "description": "Unified frontend delivery covering UI architecture, motion, accessibility, and conversion clarity.",
-      "defaultTier": "advance",
-      "defaultPackFileName": "frontend.md",
-      "evidence": "Frontend usability audit, accessibility checks, and visual regression output.",
-      "tierToPackFileNames": {
-        "standard": "frontend.md",
-        "advance": "frontend.md",
-        "expert": "frontend.md",
-        "above": "frontend.md"
-      }
-    },
-    "backend": {
-      "name": "backend",
-      "displayName": "Backend",
-      "description": "Backend delivery with strict layer separation, validation, and safe data access.",
-      "defaultTier": "advance",
-      "defaultPackFileName": "backend.md",
-      "evidence": "Unit tests, API contracts, and release gate output.",
-      "tierToPackFileNames": {
-        "standard": "backend.md",
-        "advance": "backend.md",
-        "expert": "backend.md",
-        "above": "backend.md"
-      }
-    },
-    "fullstack": {
-      "name": "fullstack",
-      "displayName": "Fullstack",
-      "description": "Single-path product delivery across frontend and backend boundaries.",
-      "defaultTier": "advance",
-      "defaultPackFileName": "fullstack.md",
-      "evidence": "End-to-end tests, contract validation, and feature parity review.",
-      "tierToPackFileNames": {
-        "standard": "fullstack.md",
-        "advance": "fullstack.md",
-        "expert": "fullstack.md",
-        "above": "fullstack.md"
-      }
-    },
-    "cli": {
-      "name": "cli",
-      "displayName": "CLI",
-      "description": "Smart command-line delivery with safe defaults, machine-readable output, and upgrade flows.",
-      "defaultTier": "advance",
-      "defaultPackFileName": "cli.md",
-      "evidence": "CLI smoke tests, dry-run output, and automation-friendly reports.",
-      "tierToPackFileNames": {
-        "standard": "cli.md",
-        "advance": "cli.md",
-        "expert": "cli.md",
-        "above": "cli.md"
-      }
-    },
-    "distribution": {
-      "name": "distribution",
-      "displayName": "Distribution",
-      "description": "Package safety, rollback, compatibility, and release hygiene.",
-      "defaultTier": "expert",
-      "defaultPackFileName": "distribution.md",
-      "evidence": "Install validation, rollback verification, and publish dry-run logs.",
-      "tierToPackFileNames": {
-        "standard": "distribution.md",
-        "advance": "distribution.md",
-        "expert": "distribution.md",
-        "above": "distribution.md"
-      }
-    },
-    "review-quality": {
-      "name": "review-quality",
-      "displayName": "Review Quality",
-      "description": "Planning, review, benchmark, and security discipline for every change.",
-      "defaultTier": "expert",
-      "defaultPackFileName": "review-quality.md",
-      "evidence": "PR review output, benchmark report, and security audit results.",
-      "tierToPackFileNames": {
-        "standard": "review-quality.md",
-        "advance": "review-quality.md",
-        "expert": "review-quality.md",
-        "above": "review-quality.md"
-      }
-    }
-  }
-}
+{
+  "defaultTier": "advance",
+  "tiers": [
+    {
+      "name": "standard",
+      "description": "Compatibility fallback only"
+    },
+    {
+      "name": "advance",
+      "description": "Default operating tier"
+    },
+    {
+      "name": "expert",
+      "description": "Complex architecture and integration"
+    },
+    {
+      "name": "above",
+      "description": "Release-critical enterprise governance"
+    }
+  ],
+  "domains": {
+    "frontend": {
+      "name": "frontend",
+      "displayName": "Frontend",
+      "description": "Unified frontend delivery covering UI architecture, motion, accessibility, and conversion clarity.",
+      "defaultTier": "advance",
+      "defaultPackFileName": "frontend.md",
+      "evidence": "Frontend usability audit, accessibility checks, and visual regression output.",
+      "tierToPackFileNames": {
+        "standard": "frontend.md",
+        "advance": "frontend.md",
+        "expert": "frontend.md",
+        "above": "frontend.md"
+      }
+    },
+    "backend": {
+      "name": "backend",
+      "displayName": "Backend",
+      "description": "Backend delivery with strict layer separation, validation, and safe data access.",
+      "defaultTier": "advance",
+      "defaultPackFileName": "backend.md",
+      "evidence": "Unit tests, API contracts, and release gate output.",
+      "tierToPackFileNames": {
+        "standard": "backend.md",
+        "advance": "backend.md",
+        "expert": "backend.md",
+        "above": "backend.md"
+      }
+    },
+    "fullstack": {
+      "name": "fullstack",
+      "displayName": "Fullstack",
+      "description": "Single-path product delivery across frontend and backend boundaries.",
+      "defaultTier": "advance",
+      "defaultPackFileName": "fullstack.md",
+      "evidence": "End-to-end tests, contract validation, and feature parity review.",
+      "tierToPackFileNames": {
+        "standard": "fullstack.md",
+        "advance": "fullstack.md",
+        "expert": "fullstack.md",
+        "above": "fullstack.md"
+      }
+    },
+    "cli": {
+      "name": "cli",
+      "displayName": "CLI",
+      "description": "Smart command-line delivery with safe defaults, machine-readable output, and upgrade flows.",
+      "defaultTier": "advance",
+      "defaultPackFileName": "cli.md",
+      "evidence": "CLI smoke tests, dry-run output, and automation-friendly reports.",
+      "tierToPackFileNames": {
+        "standard": "cli.md",
+        "advance": "cli.md",
+        "expert": "cli.md",
+        "above": "cli.md"
+      }
+    },
+    "distribution": {
+      "name": "distribution",
+      "displayName": "Distribution",
+      "description": "Package safety, rollback, compatibility, and release hygiene.",
+      "defaultTier": "expert",
+      "defaultPackFileName": "distribution.md",
+      "evidence": "Install validation, rollback verification, and publish dry-run logs.",
+      "tierToPackFileNames": {
+        "standard": "distribution.md",
+        "advance": "distribution.md",
+        "expert": "distribution.md",
+        "above": "distribution.md"
+      }
+    },
+    "review-quality": {
+      "name": "review-quality",
+      "displayName": "Review Quality",
+      "description": "Planning, review, benchmark, and security discipline for every change.",
+      "defaultTier": "expert",
+      "defaultPackFileName": "review-quality.md",
+      "evidence": "PR review output, benchmark report, and security audit results.",
+      "tierToPackFileNames": {
+        "standard": "review-quality.md",
+        "advance": "review-quality.md",
+        "expert": "review-quality.md",
+        "above": "review-quality.md"
+      }
+    }
+  }
+}

package/.agent-context/skills/review-quality/README.md

@@ -1,19 +1,19 @@
-# Review Quality Skills
-
-Default tier: `expert`
-
-This domain formalizes review quality across planning discipline, security enforcement, and benchmark-driven decision making.
-
-## Topics
-- [Planning](planning.md) - Plan quality, scope control, and change strategy
-- [Security](security.md) - Critical vulnerability policy and boundary safeguards
-- [Benchmarking](benchmark.md) - Regression detection and evidence-based comparison
-
-## Operating Model
-- Use `expert` for standard review workflows.
-- Escalate to `above` for release-critical or governance-sensitive changes.
-
-## Above-Line Additions
-- Security halt protocol for critical findings.
-- Benchmark gate thresholds integrated in CI.
+# Review Quality Skills
+
+Default tier: `expert`
+
+This domain formalizes review quality across planning discipline, security enforcement, and benchmark-driven decision making.
+
+## Topics
+- [Planning](planning.md) - Plan quality, scope control, and change strategy
+- [Security](security.md) - Critical vulnerability policy and boundary safeguards
+- [Benchmarking](benchmark.md) - Regression detection and evidence-based comparison
+
+## Operating Model
+- Use `expert` for standard review workflows.
+- Escalate to `above` for release-critical or governance-sensitive changes.
+
+## Above-Line Additions
+- Security halt protocol for critical findings.
+- Benchmark gate thresholds integrated in CI.
 - Review evidence bundle for auditability.

package/.agent-context/skills/review-quality/benchmark.md

@@ -1,30 +1,30 @@
-# Benchmarking
-
-Tier: ADVANCE
-
-Benchmarking should guide release decisions with measurable evidence rather than anecdotal impressions.
-
-## Benchmark Inputs
-
-- Baseline benchmark snapshot.
-- Current candidate benchmark output.
-- Threshold policy for acceptable deltas.
-
-## Evaluation Rules
-
-- Treat regressions above threshold as release blockers.
-- Require owner assignment for all negative deltas.
-- Re-run benchmark after remediation to verify recovery.
-
-## Reporting Standard
-
-- Include benchmark summary in release bundle.
-- Keep machine-readable JSON output for automation.
-- Track trend over time, not only single-run status.
-
-## Review Checklist
-
-- [ ] Baseline and current benchmark are comparable.
-- [ ] Threshold policy is applied consistently.
-- [ ] Regressions have owner and due date.
+# Benchmarking
+
+Tier: ADVANCE
+
+Benchmarking should guide release decisions with measurable evidence rather than anecdotal impressions.
+
+## Benchmark Inputs
+
+- Baseline benchmark snapshot.
+- Current candidate benchmark output.
+- Threshold policy for acceptable deltas.
+
+## Evaluation Rules
+
+- Treat regressions above threshold as release blockers.
+- Require owner assignment for all negative deltas.
+- Re-run benchmark after remediation to verify recovery.
+
+## Reporting Standard
+
+- Include benchmark summary in release bundle.
+- Keep machine-readable JSON output for automation.
+- Track trend over time, not only single-run status.
+
+## Review Checklist
+
+- [ ] Baseline and current benchmark are comparable.
+- [ ] Threshold policy is applied consistently.
+- [ ] Regressions have owner and due date.
 - [ ] Reports are archived for audit trail.

package/.agent-context/skills/review-quality/compatibility-manifest.json

@@ -1,8 +1,8 @@
-{
-  "schemaVersion": "compatibility-manifest-v1",
-  "artifactType": "skill-domain",
-  "domain": "review-quality",
-  "ides": ["cursor", "windsurf", "copilot", "gemini", "claude", "codex", "cline"],
-  "nodeMin": "18",
-  "platforms": ["windows", "linux", "macos"]
-}
+{
+  "schemaVersion": "compatibility-manifest-v1",
+  "artifactType": "skill-domain",
+  "domain": "review-quality",
+  "ides": ["cursor", "windsurf", "copilot", "gemini", "claude", "codex", "cline"],
+  "nodeMin": "18",
+  "platforms": ["windows", "linux", "macos"]
+}

package/.agent-context/skills/review-quality/planning.md

@@ -1,38 +1,38 @@
-# Planning
-
-Tier: EXPERT
-
-Planning quality determines implementation quality. Non-trivial work should start with a scoped, testable plan.
-
-## Planning Standard
-
-- Define objective, scope, and non-goals.
-- Identify architecture boundaries affected.
-- Document risk, rollback, and validation strategy.
-- Break work into reviewable increments.
-
-## Required Plan Artifacts
-
-- Implementation steps with expected output.
-- File impact map.
-- Test strategy and acceptance criteria.
-- Migration notes if behavior changes.
-
-## Scope Control
-
-- Avoid unrelated refactors in feature commits.
-- Split high-risk work into isolated checkpoints.
-- Preserve public API compatibility unless explicitly versioned.
-
-## Evidence Discipline
-
-- Attach command output for validation and test evidence.
-- Keep assumption logs explicit so reviewers can challenge unknowns early.
-- Ensure rollback path is documented before implementation starts.
-
-## Review Checklist
-
-- [ ] Plan includes explicit success criteria.
-- [ ] Risks and mitigations are documented.
-- [ ] Validation commands are defined.
+# Planning
+
+Tier: EXPERT
+
+Planning quality determines implementation quality. Non-trivial work should start with a scoped, testable plan.
+
+## Planning Standard
+
+- Define objective, scope, and non-goals.
+- Identify architecture boundaries affected.
+- Document risk, rollback, and validation strategy.
+- Break work into reviewable increments.
+
+## Required Plan Artifacts
+
+- Implementation steps with expected output.
+- File impact map.
+- Test strategy and acceptance criteria.
+- Migration notes if behavior changes.
+
+## Scope Control
+
+- Avoid unrelated refactors in feature commits.
+- Split high-risk work into isolated checkpoints.
+- Preserve public API compatibility unless explicitly versioned.
+
+## Evidence Discipline
+
+- Attach command output for validation and test evidence.
+- Keep assumption logs explicit so reviewers can challenge unknowns early.
+- Ensure rollback path is documented before implementation starts.
+
+## Review Checklist
+
+- [ ] Plan includes explicit success criteria.
+- [ ] Risks and mitigations are documented.
+- [ ] Validation commands are defined.
 - [ ] Scope remains aligned with original objective.

package/.agent-context/skills/review-quality/security.md

@@ -1,34 +1,34 @@
-# Security
-
-Tier: EXPERT
-
-Security review is a release gate. Critical vulnerabilities must halt feature rollout until resolved.
-
-## Security Halt Policy
-
-Immediately block release when any of the following are present:
-- Hardcoded credentials or tokens.
-- Injection vulnerabilities (SQL/command/template).
-- Authentication or authorization bypass.
-- Unvalidated external input entering privileged paths.
-
-## Boundary Safeguards
-
-- Validate external input at transport boundary.
-- Enforce parameterized queries.
-- Limit privilege scope for runtime credentials.
-- Keep secrets in approved secret stores.
-
-## Review Expectations
-
-- Threat model relevant attack surfaces.
-- Verify dependency vulnerability posture.
-- Confirm error messages do not leak sensitive internals.
-- Confirm audit logs exist for security-sensitive actions.
-
-## Review Checklist
-
-- [ ] No critical vulnerability remains open.
-- [ ] Input and output boundaries are validated.
-- [ ] Secret handling follows policy.
+# Security
+
+Tier: EXPERT
+
+Security review is a release gate. Critical vulnerabilities must halt feature rollout until resolved.
+
+## Security Halt Policy
+
+Immediately block release when any of the following are present:
+- Hardcoded credentials or tokens.
+- Injection vulnerabilities (SQL/command/template).
+- Authentication or authorization bypass.
+- Unvalidated external input entering privileged paths.
+
+## Boundary Safeguards
+
+- Validate external input at transport boundary.
+- Enforce parameterized queries.
+- Limit privilege scope for runtime credentials.
+- Keep secrets in approved secret stores.
+
+## Review Expectations
+
+- Threat model relevant attack surfaces.
+- Verify dependency vulnerability posture.
+- Confirm error messages do not leak sensitive internals.
+- Confirm audit logs exist for security-sensitive actions.
+
+## Review Checklist
+
+- [ ] No critical vulnerability remains open.
+- [ ] Input and output boundaries are validated.
+- [ ] Secret handling follows policy.
 - [ ] Least-privilege access is enforced.