@ryuenn3123/agentic-senior-core 2.0.4 → 2.0.5

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

@@ -1,28 +1,28 @@
-# Review Quality Skill Pack
-
-Default tier: `expert`
-
-## Purpose
-Turn code review, planning, and benchmark output into explicit quality decisions.
-
-## In Scope
-- Plan-first workflows
-- Reviewer self-critique
-- Benchmark interpretation
-- Security and architecture audits
-- Evidence-driven approval
-
-## Must-Have Checks
-- Every rejection includes a reason and a fix
-- Every approval includes evidence
-- Benchmark deltas are explicit
-- Security findings stop release when critical
-
-## Evidence
-- PR review report
-- Security audit output
-- Benchmark report
-- Approval or rejection rationale
-
-## Fallback
+# Review Quality Skill Pack
+
+Default tier: `expert`
+
+## Purpose
+Turn code review, planning, and benchmark output into explicit quality decisions.
+
+## In Scope
+- Plan-first workflows
+- Reviewer self-critique
+- Benchmark interpretation
+- Security and architecture audits
+- Evidence-driven approval
+
+## Must-Have Checks
+- Every rejection includes a reason and a fix
+- Every approval includes evidence
+- Benchmark deltas are explicit
+- Security findings stop release when critical
+
+## Evidence
+- PR review report
+- Security audit output
+- Benchmark report
+- Approval or rejection rationale
+
+## Fallback
 - Standard mode can be used only for low-risk maintenance and still requires written evidence.

package/.agent-context/stacks/flutter.md

@@ -1,16 +1,16 @@
-# Flutter Stack
-
-Use this stack for cross-platform mobile applications built with Flutter.
-
-## Core Guidance
-
-- Keep presentation widgets small and move state orchestration into dedicated controllers or services.
-- Separate platform channels, navigation, and business rules from widget composition.
-- Validate API payloads at the boundary and avoid spreading transport concerns into UI code.
-- Optimize build and release flows early because mobile packaging regressions are costly.
-
-## Recommended Pairings
-
-- `mobile-app` blueprint for the starter architecture.
-- `frontend` skill domain for interface composition and interaction design.
-- `fullstack` skill domain when the product includes backend coordination.
+# Flutter Stack
+
+Use this stack for cross-platform mobile applications built with Flutter.
+
+## Core Guidance
+
+- Keep presentation widgets small and move state orchestration into dedicated controllers or services.
+- Separate platform channels, navigation, and business rules from widget composition.
+- Validate API payloads at the boundary and avoid spreading transport concerns into UI code.
+- Optimize build and release flows early because mobile packaging regressions are costly.
+
+## Recommended Pairings
+
+- `mobile-app` blueprint for the starter architecture.
+- `frontend` skill domain for interface composition and interaction design.
+- `fullstack` skill domain when the product includes backend coordination.

package/.agent-context/stacks/react-native.md

@@ -1,16 +1,16 @@
-# React Native Stack
-
-Use this stack for cross-platform mobile applications built with React Native.
-
-## Core Guidance
-
-- Keep the app shell thin and delegate data fetching to dedicated service modules.
-- Treat navigation, device integration, and UI composition as separate concerns.
-- Prefer typed API contracts and isolate platform-specific code behind adapters.
-- Keep release gating strict because mobile packaging failures are expensive to recover from.
-
-## Recommended Pairings
-
-- `mobile-app` blueprint for the starter architecture.
-- `frontend` skill domain for UI composition, accessibility, and motion guidance.
-- `fullstack` skill domain when the app depends on backend contract orchestration.
+# React Native Stack
+
+Use this stack for cross-platform mobile applications built with React Native.
+
+## Core Guidance
+
+- Keep the app shell thin and delegate data fetching to dedicated service modules.
+- Treat navigation, device integration, and UI composition as separate concerns.
+- Prefer typed API contracts and isolate platform-specific code behind adapters.
+- Keep release gating strict because mobile packaging failures are expensive to recover from.
+
+## Recommended Pairings
+
+- `mobile-app` blueprint for the starter architecture.
+- `frontend` skill domain for UI composition, accessibility, and motion guidance.
+- `fullstack` skill domain when the app depends on backend contract orchestration.

package/.agent-context/state/architecture-map.md

@@ -1,25 +1,25 @@
-# Architecture Map (State Awareness)
-
-> This file defines protected architectural boundaries for AI-assisted changes.
-
-## Boundary Classification
-
-| Module/Path Pattern | Criticality | Change Policy | Required Checks |
-|---------------------|-------------|---------------|-----------------|
-| `src/modules/payment/**` | critical | Must preserve transactional behavior and idempotency | Unit + integration + rollback test |
-| `src/modules/authentication/**` | critical | Never bypass auth guards or token validation | Security audit + integration tests |
-| `src/modules/**/repository/**` | high | Preserve query contracts and avoid N+1 regressions | Query plan review + performance audit |
-| `src/features/**` | medium | Keep UI contracts stable and avoid API drift | Component tests + contract checks |
-| `src/shared/**` | high | Backward compatibility required for public utilities | Cross-module usage validation |
-
-## Required Agent Behavior
-
-1. Before editing a `critical` area, load `.agent-context/review-checklists/security-audit.md` and `.agent-context/review-checklists/performance-audit.md`.
-2. For boundary-crossing changes, verify no circular dependencies are introduced (see `dependency-map.md`).
-3. Every critical-path change must include explicit risk notes in PR description.
-
-## Project-Specific Notes
-
-- Replace placeholder path patterns with your actual module map.
-- Mark payment, identity, and financial reconciliation flows as `critical`.
-- Keep this file updated whenever module ownership changes.
+# Architecture Map (State Awareness)
+
+> This file defines protected architectural boundaries for AI-assisted changes.
+
+## Boundary Classification
+
+| Module/Path Pattern | Criticality | Change Policy | Required Checks |
+|---------------------|-------------|---------------|-----------------|
+| `src/modules/payment/**` | critical | Must preserve transactional behavior and idempotency | Unit + integration + rollback test |
+| `src/modules/authentication/**` | critical | Never bypass auth guards or token validation | Security audit + integration tests |
+| `src/modules/**/repository/**` | high | Preserve query contracts and avoid N+1 regressions | Query plan review + performance audit |
+| `src/features/**` | medium | Keep UI contracts stable and avoid API drift | Component tests + contract checks |
+| `src/shared/**` | high | Backward compatibility required for public utilities | Cross-module usage validation |
+
+## Required Agent Behavior
+
+1. Before editing a `critical` area, load `.agent-context/review-checklists/security-audit.md` and `.agent-context/review-checklists/performance-audit.md`.
+2. For boundary-crossing changes, verify no circular dependencies are introduced (see `dependency-map.md`).
+3. Every critical-path change must include explicit risk notes in PR description.
+
+## Project-Specific Notes
+
+- Replace placeholder path patterns with your actual module map.
+- Mark payment, identity, and financial reconciliation flows as `critical`.
+- Keep this file updated whenever module ownership changes.