@ryuenn3123/agentic-senior-core 2.5.22 → 3.0.0

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

@@ -1,32 +0,0 @@
-# Compatibility
-
-Tier: ADVANCE
-
-Compatibility policy prevents shipping builds that break on supported runtimes or tooling ecosystems.
-
-## Compatibility Matrix
-
-Define supported combinations explicitly:
-- Runtime versions (Node, Python, Java, etc.)
-- OS/platform scope
-- IDE/editor integration versions
-- Dependency constraints
-
-## Gate Strategy
-
-- Validate package against supported runtime matrix in CI.
-- Block release on unsupported runtime regressions.
-- Mark deprecated support windows and removal timeline.
-
-## Breaking Change Protocol
-
-- Major version for incompatible behavior.
-- Migration notes for changed defaults.
-- Transitional compatibility period when feasible.
-
-## Review Checklist
-
-- [ ] Supported runtime matrix is current and tested.
-- [ ] Incompatible changes are versioned correctly.
-- [ ] Migration notes exist for user-impacting changes.
-- [ ] CI verifies compatibility before publish.

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

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

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

@@ -1,47 +0,0 @@
-# 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/publish.md

@@ -1,37 +0,0 @@
-# Publish Hygiene
-
-Tier: EXPERT
-
-Publishing should be repeatable, auditable, and minimal in surface area.
-
-## Pre-Publish Gates
-
-- Validate package contents and metadata.
-- Run tests and policy validators.
-- Confirm version/changelog consistency.
-- Generate SBOM and provenance artifacts.
-
-## Package Surface Control
-
-- Use explicit allow-list for publish files.
-- Exclude internal scripts, test fixtures, and local configs.
-- Verify CLI entry points and executable permissions.
-
-## Ownership and Provenance
-
-- Ensure publisher identity is controlled.
-- Record commit SHA and release timestamp.
-- Attach generated reports (gate, benchmark, SBOM) to release artifacts.
-
-## Failure Policy
-
-- Abort publish on failing quality gate.
-- Abort publish on unresolved high-severity security findings.
-- Abort publish on missing changelog entry.
-
-## Review Checklist
-
-- [ ] Package contents match expected release manifest.
-- [ ] Quality and security gates passed.
-- [ ] Version and changelog are aligned.
-- [ ] Provenance artifacts are generated and stored.

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

@@ -1,32 +0,0 @@
-# Rollback
-
-Tier: EXPERT
-
-Rollback is a mandatory release capability, not an afterthought.
-
-## Rollback Readiness
-
-- Define rollback trigger conditions before release.
-- Keep previous stable artifact available for immediate redeploy.
-- Preserve migration rollback scripts for data-affecting changes.
-
-## Rollback Flow
-
-1. Detect failure signal (error spike, failed SLO, functional regression).
-2. Freeze new rollout.
-3. Re-deploy previous known-good version.
-4. Verify health checks and key journeys.
-5. Publish incident summary with root-cause owner.
-
-## Data Change Safety
-
-- Use backward-compatible migrations for forward and rollback paths.
-- Avoid destructive schema operations in same release as code cutover.
-- Validate rollback on staging with production-like data shape.
-
-## Review Checklist
-
-- [ ] Rollback plan documented and tested.
-- [ ] Previous release artifact retained.
-- [ ] Data migration rollback path verified.
-- [ ] Health checks confirm rollback success.

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

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

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

@@ -1,32 +0,0 @@
-# Distribution Skill Pack
-
-Default tier: `expert`
-
-## Purpose
-Protect package installation and release distribution with transactional safety.
-
-## In Scope
-- Package validation
-- Backup and rollback
-- Compatibility checks
-- Forbidden-file detection
-- Publish hygiene and provenance
-- Dependency audit evidence and attestations
-
-## Must-Have Checks
-- Preflight validation before installation or publish
-- Backup point before mutating user state
-- 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

@@ -1,9 +0,0 @@
-{
-  "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

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

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

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

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

@@ -1,7 +0,0 @@
----
-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

@@ -1,50 +0,0 @@
-# Frontend Engineering Skills
-
-The frontend domain covers component architecture, state management, performance optimization, accessibility, motion design, and visual polish. Content consolidated from **minimax-ai/skills** (design focus), **awesome-copilot** (architectural patterns), and **antigravity-awesome-skills** (React patterns), with production-grade automation and enforcement.
-
-## Topics
-- [UI Architecture](ui-architecture.md) - Smart/Dumb components, state management, composition patterns
-- [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
-
-- Smart/Dumb Architecture (awesome-copilot) + animation system patterns (minimax) + React patterns (antigravity)
-- Anti-Slop Enforcer (ABOVE LINE) - Detect forbidden visual patterns and style drift
-- Accessibility Auditor (ABOVE LINE) - Detect contrast failures, ARIA issues, and keyboard navigation gaps
-- Performance Budget Enforcer (ABOVE LINE) - Bundle size gates and LCP/FID/CLS thresholds
-- Frontend Excellence Rubric (ABOVE LINE) - Designer-grade scoring for visual direction, typography, color diversity, and interaction choreography
-
-## Recommended Reading Order
-
-1. `ui-architecture.md` - Mental models first (EXPERT)
-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
-
-| Aspect | antigravity | awesome-copilot | MiniMax | Ours |
-|--------|-------------|-----------------|---------|------|
-| Component Patterns | Medium | High | Medium | High + quality gates |
-| Animation Patterns | Low | Low | High | High + performance rules |
-| Accessibility | Medium | High | Medium | High + automated audits |
-| Automation | None | None | None | Anti-slop, accessibility, and performance tooling |
-
-## 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
-
-## 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/accessibility.md

@@ -1,107 +0,0 @@
-# Accessibility and Inclusive Interaction
-
-**Tier:** EXPERT | **Source:** awesome-copilot (WCAG) + minimax (motion and dark mode) + antigravity (UX patterns)
-
-## Purpose
-
-Accessibility is a production requirement. Inclusive interaction reduces support burden, improves usability, and prevents last-minute retrofit work.
-
-## Part 1: Semantic Structure
-
-Use native HTML elements first. They provide keyboard support, roles, and state semantics without extra work.
-
-```javascript
-<nav>
-  <button aria-expanded={isOpen} aria-controls="menu-panel">Menu</button>
-  <ul id="menu-panel" hidden={!isOpen}>
-    <li><a href="/">Home</a></li>
-    <li><a href="/about">About</a></li>
-  </ul>
-</nav>
-```
-
-Avoid replacing native controls with generic containers unless there is a specific reason.
-
-## Part 2: Keyboard Support
-
-Every interactive control must be reachable and operable by keyboard.
-
-- Tab order should follow the visual order.
-- Enter and Space should activate buttons and custom controls.
-- Focus should never get trapped unless a modal or dialog deliberately manages it.
-- Skip links should exist on content-heavy pages.
-
-```javascript
-<div
-  role="button"
-  tabIndex={0}
-  onClick={handleDelete}
-  onKeyDown={(event) => {
-    if (event.key === 'Enter' || event.key === ' ') {
-      handleDelete();
-    }
-  }}
->
-  Delete
-</div>
-```
-
-## Part 3: Contrast and Text Scaling
-
-- Normal text contrast should meet WCAG AA minimums.
-- Large text may use the relaxed large-text ratio, but still needs clear contrast.
-- Layouts should survive zoom and text scaling without truncation.
-- Avoid fixed-height containers that clip longer translated content.
-
-## Part 4: Screen Reader Support
-
-Use accessible names and state descriptions.
-
-```javascript
-<button aria-label="Close menu" onClick={handleClose}>
-  X
-</button>
-```
-
-If content updates dynamically, use live regions only when needed and keep them concise.
-
-## Part 5: Motion and Reduced Motion
-
-Animations should respect reduced-motion settings. Motion must support understanding, not create distraction.
-
-```javascript
-const prefersReducedMotion = window.matchMedia('(prefers-reduced-motion: reduce)').matches;
-
-const menuVariants = {
-  open: {
-    opacity: 1,
-    transition: prefersReducedMotion ? { duration: 0 } : { duration: 0.2 }
-  }
-};
-```
-
-## Part 6: Forms and Error Messaging
-
-- Every input needs a visible label.
-- Error messages should describe the problem and how to fix it.
-- Validation should be announced in a way screen readers can reach.
-- Do not rely on color alone to communicate state.
-
-## Part 7: Testing Approach
-
-Test accessibility with a mix of manual and automated checks.
-
-- Automated scans for contrast, labels, and roles.
-- Keyboard-only navigation passes for critical flows.
-- Screen-reader spot checks for key screens.
-- Motion tests for reduced-motion behavior.
-
-## Review Checklist
-
-- [ ] Semantic elements are used first.
-- [ ] Keyboard operation is complete.
-- [ ] Contrast and zoom behavior are acceptable.
-- [ ] Accessible names exist for icon-only controls.
-- [ ] Reduced-motion behavior is implemented.
-- [ ] Form labels and errors are clear.
-- [ ] Critical flows are tested with keyboard and screen readers.

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

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

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

@@ -1,51 +0,0 @@
-# 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/motion.md

@@ -1,67 +0,0 @@
-# Motion Design and Implementation
-
-Tier: EXPERT
-
-Motion is part of product behavior. It should clarify state changes, guide focus, and provide feedback without reducing accessibility or performance.
-
-## Motion Intent Model
-
-Use motion only for one of these intents:
-- Transition intent: communicate screen or state transition.
-- Feedback intent: confirm user action success/failure.
-- Focus intent: direct attention to newly relevant content.
-
-If a transition has no intent, remove it.
-
-## Timing and Consistency
-
-Adopt a small timing scale and reuse it across the product:
-- Fast: 120ms for micro-feedback.
-- Standard: 200ms to 260ms for component transitions.
-- Slow: 320ms to 420ms for route transitions.
-
-Avoid mixing unrelated easing curves in one flow.
-
-## Performance-Safe Animation Rules
-
-Prefer animating properties that do not trigger expensive layout and paint work:
-- Preferred: transform, opacity.
-- Avoid for frequent animation: top, left, width, height, box-shadow blur radius.
-
-Use CSS containment and selective `will-change` only for elements that actually animate.
-
-## Reduced Motion Compliance
-
-Always implement reduced-motion fallback:
-
-```css
-.panel {
-	transition: transform 220ms ease, opacity 220ms ease;
-}
-
-@media (prefers-reduced-motion: reduce) {
-	.panel {
-		transition: none;
-	}
-}
-```
-
-## Interaction Patterns
-
-Recommended patterns:
-- Enter/exit fade + translate for dialogs.
-- Staggered list reveal for scannability on load.
-- Subtle press/hover feedback for actionable controls.
-
-Avoid these patterns:
-- Continuous decorative motion on primary content.
-- Multiple competing animations in one viewport.
-- Looping movement that can distract reading flow.
-
-## Review Checklist
-
-- [ ] Every animation has explicit product intent.
-- [ ] Timing scale is consistent across components.
-- [ ] Heavy layout-triggering properties are avoided.
-- [ ] Reduced-motion mode is implemented and tested.
-- [ ] Motion does not block keyboard or screen-reader flow.

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

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

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

@@ -1,63 +0,0 @@
-# Frontend Performance Engineering
-
-Tier: EXPERT
-
-Performance work should be evidence-driven. Start with baseline metrics, optimize where bottlenecks are proven, then verify that user-facing indicators improved.
-
-## Core Metrics
-
-Track Core Web Vitals in CI and release checks:
-- LCP target: less than 2.5s on reference environments.
-- INP target: less than 200ms.
-- CLS target: less than 0.1.
-
-Also track bundle size and script execution time for key routes.
-
-## Render Efficiency
-
-Common controls:
-- Keep expensive computation outside render path with memoization.
-- Use stable callbacks for memoized child components.
-- Split large component trees by feature boundary.
-
-```javascript
-const visibleRows = useMemo(() => {
-	return allRows.filter((row) => row.isVisible);
-}, [allRows]);
-
-const handleRowOpen = useCallback((rowId) => {
-	openRowDetails(rowId);
-}, [openRowDetails]);
-```
-
-## Network and Caching Strategy
-
-- Treat server state separately from UI state.
-- Use query caching with explicit stale policies.
-- Avoid duplicate API calls by keying requests consistently.
-
-For route transitions, prefetch data for likely next navigation paths.
-
-## Bundle Governance
-
-Use route and component-level code splitting:
-- Lazy-load non-critical routes.
-- Defer optional heavy modules until needed.
-- Audit bundle growth at each release.
-
-Set a budget and fail CI on unapproved bundle-size regressions.
-
-## Diagnostics Workflow
-
-1. Capture baseline profile and web-vitals report.
-2. Apply one optimization change.
-3. Re-profile and compare deltas.
-4. Keep only changes with measurable improvement.
-
-## Review Checklist
-
-- [ ] Core metrics targets are monitored and reported.
-- [ ] Render-heavy paths are profiled with tooling evidence.
-- [ ] Data fetching uses cache and deduplication strategy.
-- [ ] Bundle-size budget is defined and enforced.
-- [ ] Performance regressions are blocked until reviewed.

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

@@ -1,41 +0,0 @@
-# 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

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