@ryuenn3123/agentic-senior-core 2.0.25 → 2.0.27

package/.agent-context/review-checklists/frontend-excellence-rubric.md

@@ -0,0 +1,54 @@
+# Frontend Excellence Rubric (Designer-Grade)
+
+Use this rubric to prevent template-like UI output and enforce intentional product design quality.
+
+## Scoring Model
+
+Score each dimension from 1 to 5.
+- 1: weak or generic quality
+- 3: acceptable production baseline
+- 5: standout quality comparable to top manual design teams
+
+Release recommendation:
+- Minimum average score: 4.0
+- No dimension below: 3
+
+## 1. Visual Direction and Identity
+- [ ] The page has a clear visual direction, not a generic starter layout.
+- [ ] Composition, rhythm, and hierarchy feel intentional across sections.
+- [ ] The output avoids obvious design-template repetition.
+
+## 2. Typography Quality
+- [ ] Font pairing is intentional and role-based (display, body, utility).
+- [ ] Type scale is coherent across mobile and desktop.
+- [ ] Line length, spacing, and emphasis improve readability and scanning.
+
+## 3. Color System Diversity and Contrast
+- [ ] Color palette is purposeful, with semantic roles and contrast-safe pairings.
+- [ ] The result is not a default AI palette or copied trendy scheme without adaptation.
+- [ ] Accent usage supports product intent and interaction priority.
+
+## 4. Interaction Choreography
+- [ ] Motion supports comprehension and hierarchy, not decorative noise.
+- [ ] Entrance and transition timing are consistent and measured.
+- [ ] Reduced-motion fallback preserves usability.
+
+## 5. Responsiveness and Layout Intelligence
+- [ ] Mobile layout is designed, not desktop squeezed into a narrow viewport.
+- [ ] Breakpoint transitions preserve hierarchy, spacing rhythm, and action clarity.
+- [ ] Navigation and key CTA remain explicit across viewport sizes.
+
+## 6. UX Narrative and Conversion Clarity
+- [ ] First viewport communicates value proposition and primary action immediately.
+- [ ] Error, empty, and loading states provide clear next actions.
+- [ ] User journey avoids dead ends and hidden critical actions.
+
+## Benchmark Expectation
+- Treat MiniMax frontend references as baseline, not target ceiling.
+- Target visual and interaction quality aligned with top award-grade manual design workflows (Awwwards-level reference quality).
+- Prefer original composition and branded design systems over template cloning.
+
+## Evidence for Release
+- [ ] Rubric scorecard attached to release artifact.
+- [ ] Screenshot set across key breakpoints attached.
+- [ ] Accessibility and performance evidence attached alongside rubric score.

package/.agent-context/review-checklists/frontend-skill-parity.md

@@ -25,4 +25,5 @@ Use this checklist to enforce mandatory frontend parity aligned with benchmark-d
 ## Release Evidence
 - [ ] Frontend parity checklist artifact is attached to release evidence.
 - [ ] Frontend usability audit report is attached to release evidence.
+- [ ] Frontend excellence rubric scorecard is attached to release evidence.
 - [ ] Any parity waiver includes owner, expiry, and risk statement.

package/.agent-context/review-checklists/frontend-usability.md

@@ -31,3 +31,4 @@ Run this checklist before claiming frontend work is production-ready.
 - [ ] Frontend architecture decision is documented.
 - [ ] Visual baseline update process is documented.
 - [ ] Release note includes usability and responsiveness evidence.
+- [ ] Frontend excellence rubric scorecard is attached with release evidence.

package/.agent-context/rules/docker-runtime.md

@@ -0,0 +1,29 @@
+# Docker Runtime Strategy (Dynamic Generation Required)
+
+Use this rule when Docker is enabled in project context.
+
+## 1. Dynamic Generation Only
+- Do not copy generic Docker templates blindly.
+- Generate Docker assets based on actual stack, package manager, and runtime dependencies in the repository.
+- Re-evaluate Docker instructions when dependencies, build tools, or runtime assumptions change.
+
+## 2. Separate Development and Production Lanes
+- Development lane and production lane are separate concerns.
+- Development lane priorities: fast rebuild, hot reload support, debugger-friendly startup, local volume strategy.
+- Production lane priorities: minimal image size, reproducible build, non-root runtime, strict startup command.
+
+## 3. Security and Supply Chain
+- Use minimal trusted base images with explicit versions.
+- Use multi-stage builds for production images when possible.
+- Avoid baking secrets into image layers.
+- Keep runtime image free from build-only tooling.
+
+## 4. Operational Clarity
+- Docker instructions must document expected entrypoint and exposed ports.
+- Local development command and production deployment command must be explicit.
+- If Docker is not selected for the project, do not force containerization tasks.
+
+## 5. Review Requirements
+- Verify the generated Docker workflow matches selected runtime environment (Linux/WSL, Windows, macOS).
+- Verify development and production instructions are not mixed into one unsafe image path.
+- Ensure API and service health checks are compatible with container startup behavior.

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

@@ -16,6 +16,7 @@ The frontend domain covers component architecture, state management, performance
 - 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
 

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

@@ -4,6 +4,7 @@ Default tier: `advance`
 
 ## Purpose
 Deliver frontend experiences that are visually intentional, accessible, and efficient.
+Target designer-grade quality comparable to high-signal manual design workflows.
 
 ## In Scope
 - UI architecture and component composition
@@ -21,6 +22,8 @@ Deliver frontend experiences that are visually intentional, accessible, and effi
 - Reduced-motion fallback
 - Accessibility baseline pass
 - Responsive behavior verified on mobile and desktop
+- Visual direction is explicit and not a generic AI template pattern
+- Typography and color system choices are intentional and contrast-safe
 - 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
@@ -29,6 +32,7 @@ Deliver frontend experiences that are visually intentional, accessible, and effi
 - Usability audit result
 - Visual regression output
 - Accessibility checklist result
+- Frontend excellence rubric scorecard
 - Release notes for motion and interaction changes
 - Performance trend snapshot and remediation notes when regressions occur