@ryuenn3123/agentic-senior-core 2.0.4 → 2.0.7

package/.agent-context/blueprints/mobile-app.md

@@ -1,21 +1,91 @@
 # Mobile App Blueprint
 
-This blueprint defines the starter shape for a mobile product that needs a clean separation between UI, device integration, and backend contracts.
+This blueprint defines a production starter for mobile products that need strict separation between UI flow, device integration, offline behavior, and backend contracts.
 
-## Structure
+## Reference Architecture
 
-- Transport: device events, navigation entry points, push notifications, and platform channels.
-- Service: orchestration, screen-level state, validation, and user-facing workflows.
-- Repository: remote API clients, local storage adapters, and persistence abstractions.
+Use a three-layer mobile module boundary:
 
-## Starter Rules
+- Transport layer: navigation routes, deep links, push notification handlers, platform lifecycle hooks.
+- Service layer: screen orchestration, input validation, business workflows, permission policy decisions.
+- Repository layer: API clients, local persistence, cache synchronization, device adapter wrappers.
 
-- Keep screens focused on rendering and user interaction only.
-- Move API access, caching, and serialization into adapter layers.
-- Use consistent error handling for offline, permission, and platform failures.
-- Add release checks for signing, packaging, and crash telemetry before shipping.
+## Suggested Structure
+
+```text
+mobile/
+	app/
+		navigation/
+		screens/
+		feature-flags/
+	features/
+		checkout/
+			ui/
+			service/
+			repository/
+			contracts/
+			tests/
+			index.ts
+		account/
+			ui/
+			service/
+			repository/
+			contracts/
+			tests/
+			index.ts
+	shared/
+		design-tokens/
+		telemetry/
+		error-boundaries/
+		accessibility/
+```
+
+## State and Data Rules
+
+- Keep transient UI state local to the screen component.
+- Keep feature workflow state in service-level orchestrators.
+- Keep remote and local synchronization logic in repository adapters.
+- Enforce idempotent retry semantics for background sync and push-triggered refresh.
+
+## Device and Platform Boundaries
+
+- Wrap native modules behind explicit interfaces.
+- Keep iOS/Android-specific behavior in adapter files, not in feature UI components.
+- Centralize permission checks for camera, location, notifications, and storage.
+- Define fallback behavior for denied permissions before QA sign-off.
+
+## Offline and Failure Handling
+
+- Define offline-first behavior per feature (read-only, queued writes, or blocked operations).
+- Persist pending mutations with retry metadata.
+- Show explicit user-facing recovery actions for network and permission failures.
+- Log mobile crash context with feature name, operation, and user impact summary.
+
+## Testing Baseline
+
+- Unit tests: service decisions, validation, and adapter boundary behavior.
+- Integration tests: repository sync logic with mocked device/network behavior.
+- End-to-end tests: critical journeys (login, primary conversion flow, error recovery path).
+- Accessibility checks: screen reader labels, focus order, and reduced-motion behavior.
+
+## Release Governance
+
+Before shipping each mobile release candidate:
+
+- Verify signing and packaging pipeline integrity.
+- Verify crash-free session and startup stability thresholds.
+- Verify telemetry/analytics payload schema compatibility.
+- Verify rollback strategy for binary release and remote config toggles.
 
 ## Recommended Stack Pairings
 
-- React Native for teams that want JavaScript or TypeScript alignment.
-- Flutter for teams that want a strongly structured UI toolkit.
+- React Native for teams that want JavaScript or TypeScript alignment and shared web hiring pool.
+- Flutter for teams that want consistent rendering across platforms and widget-driven architecture.
+
+## Blueprint Checklist
+
+- [ ] Feature boundaries are modular and explicit.
+- [ ] Device adapters are isolated from UI rendering code.
+- [ ] Offline and permission failure behavior is documented.
+- [ ] Critical mobile journeys are covered by automated tests.
+- [ ] Release package and telemetry gates are enforced before ship.

package/.agent-context/skills/cli/README.md

@@ -8,6 +8,7 @@ This domain covers command design, safe mutation workflows, and machine-readable
 - [Init Flow](init.md) - Deterministic project initialization with explicit write plans
 - [Upgrade Flow](upgrade.md) - Safe upgrades with dry-run, rollback, and compatibility checks
 - [Machine-Readable Output](output.md) - Stable JSON output and deterministic exit semantics
+- [Safety and Telemetry](safety-telemetry.md) - Operational signal capture and release-facing CLI governance summaries
 
 ## Operating Model
 - Use `advance` for normal command work.
@@ -40,6 +41,11 @@ Use presets when you want fewer choices at the start:
 - `mobile-react-native` - React Native + mobile app + balanced profile.
 - `mobile-flutter` - Flutter + mobile app + balanced profile.
 - `observability-platform` - Go + observability + strict profile.
+- `typescript-nestjs-service` - TypeScript + NestJS module blueprint + balanced profile.
+- `java-enterprise-api` - Java + Spring Boot API + strict profile.
+- `dotnet-enterprise-api` - C# + ASP.NET API + strict profile.
+- `php-laravel-api` - PHP + Laravel API + balanced profile.
+- `kubernetes-platform` - Go + Kubernetes manifests + strict profile.
 
 Example:
 

package/.agent-context/skills/cli/safety-telemetry.md

@@ -0,0 +1,39 @@
+# Safety and Telemetry
+
+Tier: ADVANCE
+
+CLI safety telemetry captures operational signals that help maintainers detect drift, reduce onboarding failures, and enforce release quality.
+
+## Signal Categories
+
+Capture and review machine-readable CLI signals:
+
+- Validation and release-gate status.
+- Preflight failure categories.
+- Rollback trigger frequency.
+- Preset usage distribution across onboarding sessions.
+
+## Output Contract
+
+Telemetry reports should remain automation-friendly:
+
+- Stable JSON shape.
+- ISO timestamps.
+- Explicit status fields.
+- Actionable blocker summary.
+
+Human-facing logs can remain concise, but automation payloads should preserve full diagnostic details.
+
+## Governance Use Cases
+
+- Weekly maintainership report generation.
+- Detecting repeated onboarding failures caused by conflicting local files.
+- Tracking whether preset expansion improves adoption.
+- Confirming rollback operations remain low-frequency and controlled.
+
+## Review Checklist
+
+- [ ] Safety signals are emitted in machine-readable format.
+- [ ] Preset and failure telemetry are captured consistently.
+- [ ] Operational reports include blocker summaries.
+- [ ] Telemetry output is suitable for CI artifact upload.

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

@@ -11,6 +11,7 @@ Create smart command-line workflows that guide users efficiently and safely.
 - Machine-readable output for automation
 - Validation and self-healing hooks
 - Cross-platform shell behavior
+- Preset ergonomics and operational telemetry outputs
 
 ## Must-Have Checks
 - Explicit command help and examples
@@ -18,12 +19,14 @@ Create smart command-line workflows that guide users efficiently and safely.
 - Safe destructive-action guards
 - Validation before mutation
 - Exit codes reflect success and failure clearly
+- Preset catalog remains discoverable and tested in smoke tests
 
 ## Evidence
 - CLI smoke tests
 - Machine-readable report output
 - Upgrade dry-run output
 - Cross-platform execution notes
+- Weekly governance report references CLI trust tier and release posture
 
 ## Fallback
 - Standard mode can remain available for compatibility, but advance is the default user experience.

package/.agent-context/skills/distribution/.evidence/compatibility-manifest.json

@@ -0,0 +1,9 @@
+{
+  "schemaVersion": "compatibility-manifest-v1",
+  "artifactType": "skill-domain-evidence",
+  "domain": "distribution",
+  "ides": ["cursor", "windsurf", "copilot", "gemini", "claude", "codex", "cline"],
+  "nodeMin": "18",
+  "platforms": ["windows", "linux", "macos"],
+  "validatedAt": "2026-04-11T12:00:00Z"
+}

package/.agent-context/skills/distribution/.evidence/sbom-excerpt.json

@@ -0,0 +1,6 @@
+{
+  "format": "cyclonedx",
+  "component": "@agentic-skills/distribution",
+  "version": "1.0.0",
+  "dependencies": []
+}

package/.agent-context/skills/distribution/.evidence/test-report.json

@@ -0,0 +1,8 @@
+{
+  "passed": true,
+  "total": 14,
+  "failed": 0,
+  "skipped": 0,
+  "durationMs": 1300,
+  "lastRun": "2026-04-11T12:00:00Z"
+}

package/.agent-context/skills/distribution/CHANGELOG.md

@@ -0,0 +1,7 @@
+---
+tier: production
+---
+# Changelog
+## 1.0.0
+- Expanded distribution skill depth with provenance attestation guidance.
+- Added evidence bundle metadata for trust-tier verification.

package/.agent-context/skills/distribution/README.md

@@ -8,6 +8,7 @@ This domain governs release packaging, compatibility policy, and rollback readin
 - [Publish Hygiene](publish.md) - Package integrity, provenance, and release evidence
 - [Rollback](rollback.md) - Recovery-first release operations
 - [Compatibility](compatibility.md) - Runtime/tooling support policy and guardrails
+- [Provenance Attestation](provenance-attestation.md) - SBOM linkage, artifact identity, and maintainership traceability
 
 ## Operating Model
 - Use `expert` as the default distribution tier.
@@ -16,4 +17,11 @@ This domain governs release packaging, compatibility policy, and rollback readin
 ## Above-Line Additions
 - Release gates tied to benchmark and compatibility checks.
 - Supply-chain artifacts (SBOM/provenance) as first-class outputs.
-- Explicit rollback drills before critical releases.
+- Explicit rollback drills before critical releases.
+
+## Usage Example
+
+```bash
+npm run gate:release
+npm run report:governance-weekly
+```

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

@@ -0,0 +1,5 @@
+{
+  "name": "@agentic-skills/distribution",
+  "version": "1.0.0",
+  "author": "agentic"
+}

package/.agent-context/skills/distribution/provenance-attestation.md

@@ -0,0 +1,47 @@
+# Provenance Attestation
+
+Tier: EXPERT
+
+Provenance attestation links shipped artifacts to source commits, policy gates, and maintainer intent so releases remain auditable.
+
+## Attestation Requirements
+
+Every release artifact should be traceable to:
+
+- Source commit SHA.
+- Versioned changelog entry.
+- Gate evidence (release gate, benchmark, security checks).
+- Maintainer identity and release timestamp.
+
+## Artifact Chain
+
+Maintain a simple provenance chain:
+
+1. Build artifact from tagged commit.
+2. Generate SBOM and integrity digest.
+3. Attach gate output artifacts.
+4. Publish with immutable version metadata.
+
+If any step is missing, release should be blocked until evidence is complete.
+
+## Tamper-Resistance Controls
+
+- Avoid manual artifact replacement outside CI path.
+- Keep checksums in release notes or signed metadata.
+- Enforce immutable package versions after publish.
+- Store audit artifacts with retention policy.
+
+## Operational Review
+
+At weekly cadence, review provenance quality:
+
+- Are all recent releases traceable end to end?
+- Were any gates bypassed or manually overridden?
+- Are SBOM and compatibility manifests synchronized?
+
+## Review Checklist
+
+- [ ] Source commit and version metadata are linked.
+- [ ] SBOM and checksum artifacts are attached.
+- [ ] Gate evidence is complete and timestamped.
+- [ ] No unsigned or out-of-band artifact replacement occurred.

package/.agent-context/skills/distribution/tests/.gitkeep

@@ -0,0 +1 @@
+# Distribution skill test fixtures placeholder

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

@@ -11,6 +11,7 @@ Protect package installation and release distribution with transactional safety.
 - Compatibility checks
 - Forbidden-file detection
 - Publish hygiene and provenance
+- Dependency audit evidence and attestations
 
 ## Must-Have Checks
 - Preflight validation before installation or publish
@@ -18,12 +19,14 @@ Protect package installation and release distribution with transactional safety.
 - Automatic rollback on failure
 - Compatibility manifest present
 - Evidence bundle attached to release
+- Weekly governance report generated and reviewed before maintainers publish
 
 ## Evidence
 - Install validation report
 - Rollback verification log
 - Publish dry-run output
 - Integrity and provenance manifest
+- Governance weekly report with trust-tier and gate posture summary
 
 ## Fallback
 - If automated rollback cannot be guaranteed, the operation must stop before mutation.

package/.agent-context/skills/frontend/.evidence/compatibility-manifest.json

@@ -0,0 +1,9 @@
+{
+  "schemaVersion": "compatibility-manifest-v1",
+  "artifactType": "skill-domain-evidence",
+  "domain": "frontend",
+  "ides": ["cursor", "windsurf", "copilot", "gemini", "claude", "codex", "cline"],
+  "nodeMin": "18",
+  "platforms": ["windows", "linux", "macos"],
+  "validatedAt": "2026-04-11T12:00:00Z"
+}

package/.agent-context/skills/frontend/.evidence/sbom-excerpt.json

@@ -0,0 +1,6 @@
+{
+  "format": "cyclonedx",
+  "component": "@agentic-skills/frontend",
+  "version": "1.0.0",
+  "dependencies": []
+}

package/.agent-context/skills/frontend/.evidence/test-report.json

@@ -0,0 +1,8 @@
+{
+  "passed": true,
+  "total": 24,
+  "failed": 0,
+  "skipped": 0,
+  "durationMs": 1900,
+  "lastRun": "2026-04-11T12:00:00Z"
+}

package/.agent-context/skills/frontend/CHANGELOG.md

@@ -0,0 +1,7 @@
+---
+tier: production
+---
+# Changelog
+## 1.0.0
+- Expanded frontend skill depth with responsive and conversion tracks.
+- Added evidence bundle metadata for trust-tier verification.

package/.agent-context/skills/frontend/README.md

@@ -7,6 +7,8 @@ The frontend domain covers component architecture, state management, performance
 - [Accessibility](accessibility.md) - WCAG compliance, keyboard navigation, semantic HTML, color contrast
 - [Motion](motion.md) - Animation patterns, performance, CSS containment
 - [Performance](performance.md) - Memoization, code splitting, bundle gates, profiling
+- [Responsive Delivery](responsive-delivery.md) - Breakpoint behavior, content hierarchy, and interaction ergonomics
+- [Conversion Clarity](conversion-clarity.md) - First-viewport messaging, CTA placement, and friction removal
 
 ## What Makes Ours Different
 
@@ -21,6 +23,8 @@ The frontend domain covers component architecture, state management, performance
 2. `accessibility.md` - Compliance baseline (EXPERT)
 3. `motion.md` - Design patterns and optimization (EXPERT)
 4. `performance.md` - Profiling and gates (EXPERT)
+5. `responsive-delivery.md` - Mobile and desktop behavior contracts (ADVANCE)
+6. `conversion-clarity.md` - UX narrative and action path quality (ADVANCE)
 
 ## Coverage vs 3 Repos
 
@@ -33,4 +37,13 @@ The frontend domain covers component architecture, state management, performance
 
 ## Default Tier Behavior
 - Use `advance` for typical web apps (1500+ employees)
-- Escalate to `expert` when component library, state complexity, or accessibility/performance tuning is critical
+- Escalate to `expert` when component library, state complexity, or accessibility/performance tuning is critical
+
+## Usage Example
+
+Use frontend guidance in onboarding and release checkpoints:
+
+```bash
+agentic-senior-core init --preset frontend-web
+node ./scripts/frontend-usability-audit.mjs
+```

package/.agent-context/skills/frontend/conversion-clarity.md

@@ -0,0 +1,51 @@
+# Conversion Clarity
+
+Tier: ADVANCE
+
+Conversion clarity ensures users understand value, trust the flow, and can complete primary actions without ambiguity.
+
+## First-Viewport Messaging
+
+Every conversion-oriented screen should answer three questions immediately:
+
+- What is this offering?
+- Why should I continue now?
+- What action should I take first?
+
+Avoid generic hero copy and unclear button labels. CTA text should describe outcome, not only interaction.
+
+## Friction Mapping
+
+Define friction checkpoints per journey:
+
+- Input complexity and cognitive load.
+- Validation and error recovery behavior.
+- Payment or confirmation trust signals.
+- Abandonment points from analytics and session replay.
+
+Each checkpoint needs an explicit mitigation strategy.
+
+## Error and Empty State Quality
+
+- Error states must explain cause and provide next action.
+- Empty states must direct users toward meaningful first action.
+- Do not rely on passive placeholders without guidance.
+- Preserve user input when validation fails to reduce retry friction.
+
+## Instrumentation Expectations
+
+Track conversion quality with consistent events:
+
+- Journey start.
+- Step completion.
+- Validation failure categories.
+- Final success and drop-off points.
+
+Ensure event names and payload schema are versioned.
+
+## Review Checklist
+
+- [ ] First viewport communicates value and next action clearly.
+- [ ] Primary CTA labels are specific and outcome-oriented.
+- [ ] Error and empty states contain actionable guidance.
+- [ ] Conversion analytics events are complete and versioned.

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

@@ -0,0 +1,5 @@
+{
+  "name": "@agentic-skills/frontend",
+  "version": "1.0.0",
+  "author": "agentic"
+}

package/.agent-context/skills/frontend/responsive-delivery.md

@@ -0,0 +1,41 @@
+# Responsive Delivery
+
+Tier: ADVANCE
+
+Responsive delivery is not just resizing components. It defines how information hierarchy, interaction ergonomics, and loading behavior adapt across screen classes.
+
+## Breakpoint Contract
+
+Define a small set of supported breakpoints and explicitly map each critical screen to layout behavior:
+
+- Mobile baseline for primary one-handed flows.
+- Tablet landscape/portrait handling for mixed navigation density.
+- Desktop behavior for dense data views and power-user shortcuts.
+
+## Hierarchy and Readability
+
+- Keep primary value proposition and main action in first viewport.
+- Promote one primary CTA and one secondary CTA at most on conversion screens.
+- Prevent layout shift when optional content loads asynchronously.
+- Keep typography scaling consistent with design tokens.
+
+## Interaction Ergonomics
+
+- Maintain touch target minimum sizes for mobile.
+- Preserve keyboard navigability on desktop and tablet keyboard scenarios.
+- Avoid hover-only critical interactions.
+- Ensure sticky bars and bottom sheets do not hide required form controls.
+
+## Validation Workflow
+
+1. Capture screenshots for each breakpoint from the same scenario.
+2. Execute keyboard and pointer flow checks on critical journeys.
+3. Verify loading, empty, and error states for each breakpoint class.
+4. Attach responsive evidence to release artifact bundle.
+
+## Review Checklist
+
+- [ ] Breakpoint behavior is documented per critical screen.
+- [ ] Primary CTA remains clear on all supported viewports.
+- [ ] Touch and keyboard interactions are both functional.
+- [ ] Loading and error states preserve layout stability.

package/.agent-context/skills/frontend/tests/.gitkeep

@@ -0,0 +1 @@
+# Frontend skill test fixtures placeholder

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

@@ -11,6 +11,8 @@ Deliver frontend experiences that are visually intentional, accessible, and effi
 - Motion, animation, and interaction polish
 - Accessibility and keyboard flows
 - Conversion clarity and onboarding flow
+- Performance budgets and render diagnostics
+- Release evidence for visual and interaction quality
 
 ## Must-Have Checks
 - Feature-driven folder structure
@@ -19,12 +21,16 @@ Deliver frontend experiences that are visually intentional, accessible, and effi
 - Reduced-motion fallback
 - Accessibility baseline pass
 - Responsive behavior verified on mobile and desktop
+- First viewport communicates value proposition and primary action clearly
+- Error and empty states provide explicit next actions
+- Performance budget and regression thresholds are documented per release
 
 ## Evidence
 - Usability audit result
 - Visual regression output
 - Accessibility checklist result
 - Release notes for motion and interaction changes
+- Performance trend snapshot and remediation notes when regressions occur
 
 ## Fallback
 - If a feature cannot meet the advance tier, ship standard mode only as a temporary compatibility path.

package/.agent-context/skills/fullstack/.evidence/compatibility-manifest.json

@@ -0,0 +1,9 @@
+{
+  "schemaVersion": "compatibility-manifest-v1",
+  "artifactType": "skill-domain-evidence",
+  "domain": "fullstack",
+  "ides": ["cursor", "windsurf", "copilot", "gemini", "claude", "codex", "cline"],
+  "nodeMin": "18",
+  "platforms": ["windows", "linux", "macos"],
+  "validatedAt": "2026-04-11T12:00:00Z"
+}

package/.agent-context/skills/fullstack/.evidence/sbom-excerpt.json

@@ -0,0 +1,6 @@
+{
+  "format": "cyclonedx",
+  "component": "@agentic-skills/fullstack",
+  "version": "1.0.0",
+  "dependencies": []
+}

package/.agent-context/skills/fullstack/.evidence/test-report.json

@@ -0,0 +1,8 @@
+{
+  "passed": true,
+  "total": 18,
+  "failed": 0,
+  "skipped": 0,
+  "durationMs": 1600,
+  "lastRun": "2026-04-11T12:00:00Z"
+}

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

@@ -0,0 +1,7 @@
+---
+tier: production
+---
+# Changelog
+## 1.0.0
+- Expanded fullstack skill depth with release coordination guidance.
+- Added evidence bundle metadata for trust-tier verification.

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

@@ -8,6 +8,7 @@ This domain connects frontend and backend implementation into a single feature-d
 - [Feature Slicing](feature-slicing.md) - Organize UI, service, repository, and tests around one business capability
 - [Contracts](contracts.md) - Keep API schemas, DTOs, and frontend types synchronized
 - [End-to-End](end-to-end.md) - Release readiness by verified user journeys and operational gates
+- [Release Coordination](release-coordination.md) - Multi-service rollout ordering, rollback thresholds, and evidence handoff
 
 ## Operating Model
 - Use `advance` for normal feature development.
@@ -16,4 +17,11 @@ This domain connects frontend and backend implementation into a single feature-d
 ## Above-Line Additions
 - Contract drift detection in CI before merge.
 - Backward-compatibility checks for API changes.
-- Release evidence bundle for end-to-end readiness.
+- Release evidence bundle for end-to-end readiness.
+
+## Usage Example
+
+```bash
+agentic-senior-core init --preset fullstack-product
+node ./scripts/quality-trend-report.mjs
+```

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

@@ -0,0 +1,5 @@
+{
+  "name": "@agentic-skills/fullstack",
+  "version": "1.0.0",
+  "author": "agentic"
+}

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

@@ -0,0 +1,51 @@
+# Release Coordination
+
+Tier: EXPERT
+
+Release coordination in fullstack systems aligns UI rollout, API compatibility, data migration timing, and rollback readiness across teams.
+
+## Coordination Matrix
+
+Define a shared release matrix before merge:
+
+- Frontend deployment window and feature-flag activation point.
+- Backend deployment order and compatibility grace period.
+- Data migration execution and rollback scope.
+- Observability checks required for release acceptance.
+
+## Rollout Sequencing
+
+Use an order that preserves backward compatibility:
+
+1. Deploy backend changes in compatibility mode.
+2. Verify contract and benchmark gates.
+3. Deploy frontend consuming new contract.
+4. Enable feature flags progressively.
+5. Remove compatibility shim in a later release.
+
+## Blocker Handling
+
+Track blocker categories with explicit owners:
+
+- Contract mismatch blockers.
+- Performance regression blockers.
+- Accessibility or conversion regression blockers.
+- Migration and rollback uncertainty blockers.
+
+A release can proceed only when blocker list is empty or risk acceptance is approved and documented.
+
+## Evidence Handoff
+
+Release evidence bundle should include:
+
+- End-to-end report for critical journeys.
+- Contract validation and diff summary.
+- Benchmark and quality-trend snapshot.
+- Rollback drill or recovery playbook reference.
+
+## Review Checklist
+
+- [ ] Rollout sequence keeps consumer/provider compatibility.
+- [ ] Blockers have owner and due date before release review.
+- [ ] Feature flags are mapped to rollback strategy.
+- [ ] Evidence bundle is attached to release decision.

package/.agent-context/skills/fullstack/tests/.gitkeep

@@ -0,0 +1 @@
+# Fullstack skill test fixtures placeholder