@ryuenn3123/agentic-senior-core 2.0.5 → 2.0.8

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

@@ -1,32 +1,32 @@
-# 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.
+# 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

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

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

@@ -1,29 +1,32 @@
-# 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
-
-## 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
-
-## Evidence
-- Install validation report
-- Rollback verification log
-- Publish dry-run output
-- Integrity and provenance manifest
-
-## Fallback
+# 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

@@ -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

@@ -1,36 +1,49 @@
-# 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
-
-## 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
-
-## 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)
-
-## 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
+# 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
+
+## 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 +1,107 @@
-# 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.
+# 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 +1,8 @@
-{
-  "schemaVersion": "compatibility-manifest-v1",
-  "artifactType": "skill-domain",
-  "domain": "frontend",
-  "ides": ["cursor", "windsurf", "copilot", "gemini", "claude", "codex", "cline"],
-  "nodeMin": "18",
-  "platforms": ["windows", "linux", "macos"]
-}
+{
+  "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

@@ -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.