@ryuenn3123/agentic-senior-core 6.16.5 → 6.16.6

package/.agents/plugins/agentic-senior-core/skills/asc-ui/references/modes/operate.md

@@ -4,6 +4,10 @@ Use for: Dashboards, data grids, admin consoles, editors, settings, financial le
 
 > **Core Principle:** The visitor completes a task. Scanability, dense data alignment, low cognitive friction, and native expectations outrank emotional expression. Brand identity lives in the precision of micro-details, not loud decorative containers.
 
+> **Visual Reference Benchmarks:**
+> - CRM & Relational Operations: `references/visuals/real-attio.png` (`real-attio-dom.json`)
+> - Analytics & Telemetry Dashboards: `references/visuals/real-dub.png` (`real-dub-dom.json`)
+
 ---
 
 ## 1. Information Density & Layout Geometry
@@ -18,7 +22,7 @@ Use for: Dashboards, data grids, admin consoles, editors, settings, financial le
   - Hover feedback: `hover:bg-muted/40` across the entire row.
   - Text alignment rule: Left-align text strings, right-align numeric figures and monetary amounts, center status chips and icon actions.
   - Numeric values must use `tabular-nums` for vertical column alignment.
-- **Progressive Disclosure alih-alih Modal Popups:**
+- **Progressive Disclosure over Intrusive Modals:**
   - Avoid popping modals for inline edits or sub-entity creation. Use expandable rows, sliding side sheets (drawers), or inline input switches.
   - Reserve dialogs strictly for destructive confirmations (delete, revoke) or complex isolated workflows (import wizard).
 
@@ -53,26 +57,26 @@ Use for: Dashboards, data grids, admin consoles, editors, settings, financial le
 
 ---
 
-## 4. Audit & Inspection Finding Rows (Action Affordance Invariant)
+## 4. Inspection & Audit Finding Rows
 
 - **Interactive Row Contract:**
   - Finding rows, audit line items, and checklist items must never be rendered as dead, static text blocks.
-  - Every finding row (e.g. `FT-01: Bukti fisik belum dilampirkan`) must provide:
-    1. **Primary Action Affordance:** Explicit inline trigger button (e.g. `Periksa Bukti`, `Minta Rincian`, or expandable chevron).
+  - Every finding row (e.g. `Finding #1: Physical document pending verification`) must provide:
+    1. **Primary Action Affordance:** Explicit inline trigger button (e.g. `Review File`, `Request Details`, or expandable chevron).
     2. **Attachment Badge:** File type badge (`PDF`, `XLSX`), byte size, and upload timestamp.
-    3. **Status Pill:** High-contrast semantic pill (`Perlu Tindak Lanjut`, `Menunggu Konfirmasi`, `Selesai`).
+    3. **Status Pill:** High-contrast semantic pill (`Needs Attention`, `Pending Confirmation`, `Verified`).
     4. **Hover State:** `hover:bg-muted/40 transition-colors` across the entire row bounding box.
 
 ---
 
-## 5. Dual-Navigation De-Confliction (Lenses vs Lifecycle)
+## 5. Dual Navigation Patterns (Filters vs Lifecycles)
 
 - **Separation of Mental Models:**
-  - **Horizontal Tabs**: View-Port Filter Lenses (switching data views, e.g. *Ringkasan*, *Rubrik Domain*, *Temuan*, *Riwayat*). These change what information is rendered on the stage.
-  - **Vertical Rail**: Immutable Lifecycle Progression (e.g. *1. Unggah Dokumen $\to$ 2. Verifikasi $\to$ 3. Penilaian $\to$ 4. Konfirmasi Fisik $\to$ 5. Rangkuman*). This reflects where the entity is in its operational state.
+  - **Horizontal Tabs**: View-Port Filter Lenses (switching data views, e.g. *Overview*, *Domain Criteria*, *Findings*, *History*). These change what information is rendered on the stage.
+  - **Vertical Rail**: Immutable Lifecycle Progression (e.g. *1. Upload Document $\to$ 2. Verify $\to$ 3. Assess $\to$ 4. Confirm $\to$ 5. Summary*). This reflects where the entity is in its operational state.
 - **Accenting Active Lifecycle Step:**
   - Never let the current active step in the lifecycle rail look identical to future unstarted steps.
-  - Active step: highlighted with high-contrast accent ring or filled circle (`bg-primary text-primary-foreground`) with an active descriptor ("Tahap aktif verifikasi").
+  - Active step: highlighted with high-contrast accent ring or filled circle (`bg-primary text-primary-foreground`) with an active descriptor ("Active verification phase").
   - Completed steps: clear muted checks (`text-emerald-600` with subtle strike or timestamp).
   - Pending steps: muted borders (`border-border text-muted-foreground`).
 

package/.agents/plugins/agentic-senior-core/skills/asc-ui/references/modes/persuade.md

@@ -4,6 +4,12 @@ Use for: Landing pages, marketing websites, product launch pages, and pricing sc
 
 > **Core Principle:** The visitor decides and acts; design is the product. Earn attention and conversion with bold, authentic conviction. Ambition is expressed through scale, typographic contrast, and proof of reality—never through fluffy filler or generic card stacks.
 
+> **Visual Reference Benchmarks:**
+> - High-Impact Brand Stage: `references/visuals/real-vercel.png` (`real-vercel-dom.json`)
+> - Financial Infrastructure / Multi-Tier Flow: `references/visuals/real-stripe.png` (`real-stripe-dom.json`)
+> - Editorial Developer Infrastructure: `references/visuals/real-resend.png` (`real-resend-dom.json`)
+> - Storefront / Catalog Filter Stage: `references/visuals/real-marketplace.png` (`real-marketplace-dom.json`)
+
 ---
 
 ## 1. The Viewport Budget & The 80-Word Rule
@@ -18,13 +24,13 @@ Use for: Landing pages, marketing websites, product launch pages, and pricing sc
 
 ---
 
-## 2. In-Memory Direction Dealer (4 Structural Postures)
+## 2. Structural Layout Blueprints (4 Compositions)
 
-When building or redesigning a Persuade surface, never let the LLM default to the statistical average of marketing pages. Choose one of four researched structural postures based on the project's real material:
+When building or redesigning a Persuade surface, select a deliberate structural layout matching the product's real content:
 
 ```
 ┌────────────────────────────────────────────────────────────────────────┐
-│                        THE 4 STRUCTURAL POSTURES                       │
+│                      THE 4 STRUCTURAL BLUEPRINTS                       │
 ├────────────────────────────────────────────────────────────────────────┤
 │ 1. Asymmetric Stage (65/35 Split): Left-anchored heavy typography      │
 │    offset against an interactive preview, ROI calculator, or live UI. │
@@ -37,15 +43,15 @@ When building or redesigning a Persuade surface, never let the LLM default to th
 └────────────────────────────────────────────────────────────────────────┘
 ```
 
-- **Posture Selection Protocol:**
-  - If real software interface exists $\to$ **Posture 3 (Product-Led Canvas)**.
-  - If quantitative savings or enterprise value proposition $\to$ **Posture 1 (Asymmetric Stage)**.
-  - If technical documentation, whitepaper, or architectural manifesto $\to$ **Posture 2 (The Monolith Ledger)**.
-  - If performance benchmarks, protocol comparisons, or telemetry proof $\to$ **Posture 4 (Kinetic Proof Stream)**.
+- **Blueprint Selection:**
+  - If real software interface exists $\to$ **Blueprint 3 (Product-Led Canvas)**.
+  - If quantitative savings or enterprise value proposition $\to$ **Blueprint 1 (Asymmetric Stage)**.
+  - If technical documentation, whitepaper, or architectural manifesto $\to$ **Blueprint 2 (The Monolith Ledger)**.
+  - If performance benchmarks, protocol comparisons, or telemetry proof $\to$ **Blueprint 4 (Kinetic Proof Stream)**.
 
 ### Structural Blueprints (Enforced DOM Geometries)
 
-#### Posture 1: Asymmetric Stage (65/35 Split)
+#### Blueprint 1: Asymmetric Stage (65/35 Split)
 - **Container:** `grid grid-cols-1 lg:grid-cols-12 gap-12 items-center`
 - **Left Lead (7 cols):** `lg:col-span-7 space-y-6 text-left`
   - Display headline: `text-5xl lg:text-7xl font-bold tracking-tight leading-[1.05]`
@@ -55,14 +61,14 @@ When building or redesigning a Persuade surface, never let the LLM default to th
   - Authentic artifact, interactive widget, or live score/ROI card: `rounded-2xl border border-border/80 bg-card p-6 shadow-sm`
   - Zero equal-weight card grids below.
 
-#### Posture 2: The Monolith Ledger
+#### Blueprint 2: The Monolith Ledger
 - **Container:** `max-w-4xl mx-auto px-6 py-16 divide-y divide-border/60`
 - **Tabular Rows:** Each entity or program is a horizontal row: `py-8 grid grid-cols-1 md:grid-cols-12 gap-6 items-baseline`
   - Category / Date: `md:col-span-3 text-xs font-semibold tracking-wider uppercase text-muted-foreground`
   - Heading & Data: `md:col-span-5 text-xl font-bold text-foreground`
   - Detail & Action: `md:col-span-4 text-sm text-muted-foreground`
 
-#### Posture 3: Product-Led Canvas
+#### Blueprint 3: Product-Led Canvas
 - **Container:** `flex flex-col items-center text-center max-w-6xl mx-auto px-6 pt-16 pb-20`
 - **Compact Hero Frame:** `max-w-2xl space-y-4 mb-10`
   - Headline: `text-4xl sm:text-6xl font-extrabold tracking-tight`
@@ -72,19 +78,22 @@ When building or redesigning a Persuade surface, never let the LLM default to th
 
 ---
 
-## 3. Anti-Cardocalypse & Visual Pacing
+## 3. Composition Variety & Content Rhythm
 
-- **Banned 3-Card Symmetrical Grid:**
-  - Never default to a 3-column grid where every card has identical dimensions, a Lucide icon in a pastel square, a bold title, and two lines of gray text.
+- **Banned Symmetrical 3-Card Rows:**
+  - Never default to a 3-column row where every item has identical dimensions, a generic icon box, a bold title, and two lines of gray text.
   - Instead, vary composition according to content weight:
     - *Flagship Feature:* Full-width container or asymmetric 8/4 split showing the primary capability in action.
     - *Supporting Capabilities:* Compact 2-column checklist or a structured comparison table.
-- **The Signature Element:**
-  - Every Persuade surface may feature at most **one memorable signature element** on the first screen that directly reflects the product domain:
+- **Anti-Spreadsheet Wireframe on Public Landing Pages:**
+  - Do NOT convert a public home or landing page into a 100+ row raw data dump. Provide structured category overviews with focused preview panels (see `references/craft/composition-patterns.md`).
+  - Do NOT wrap human directories or committees into spreadsheet border matrices (`border-t border-b border-l border-r`); use clean spacing, authentic badges, and natural typographic flow.
+- **The Focal Signature Element:**
+  - Every Persuade surface may feature at most **one memorable focal element** on the first screen that directly reflects the product domain:
     - An interactive calculator or estimator that recalculates results in real time.
     - An unedited, high-resolution product screenshot showing real user data.
     - A live interactive UI fragment (e.g., an assessment scorecard preview for educational tools, a filterable ledger row for accounting tools).
-  - **Hard Ban on Faux-Terminal Cosplay:** Never inject terminal prompts, ASCII art, or pseudo-telemetry consoles into non-developer products.
+  - **No Artificial Terminals:** Never inject terminal prompts, ASCII art, or pseudo-telemetry consoles into non-developer products.
   - A giant counter of marks or animated numbers is a decorative reflex, not a signature.
 
 ---

package/.agents/plugins/agentic-senior-core/skills/asc-ui/references/modes/read.md

@@ -4,6 +4,10 @@ Use for: Documentation, API references, technical blogs, guides, knowledge bases
 
 > **Core Principle:** The visitor understands something. Structure for sustained comprehension, visual calm, and rapid scanning. The reading experience must minimize eye fatigue while providing effortless navigation through dense hierarchies.
 
+> **Visual Reference Benchmarks:**
+> - Documentation & API Reference: `references/visuals/real-mintlify.png` (`real-mintlify-dom.json`)
+> - Product Manifesto & Long-Form Craft: `references/visuals/real-linear.png` (`real-linear-dom.json`)
+
 ---
 
 ## 1. Ergonomic Reading Measure & Spacing

package/.agents/plugins/agentic-senior-core/skills/asc-ui/references/redesign-audit.md

@@ -75,7 +75,7 @@ Audit screens systematically against four engineering vectors:
 - [ ] Cycle through entire screen using `Tab` and `Shift+Tab` with mouse disconnected.
 - [ ] Press `Escape` while dialog/modal is open; verify closure and focus restoration.
 
-### 4.3 State Quad Coverage
+### 4.3 State Coverage
 - [ ] Inspect loading state: does it use proportional skeletons matching final dimensions?
 - [ ] Inspect empty state: is it actionable with a 1-sentence explanation?
 - [ ] Inspect error state: does it diagnose the issue and provide an inline retry button?

package/.agents/plugins/agentic-senior-core/skills/asc-ui/references/states-feedback.md

@@ -1,10 +1,10 @@
-# The Data State Quad & Action Feedback Engine
+# Data States & Action Feedback
 
 Any view that consumes asynchronous data or triggers mutations must handle every possible state in the component lifecycle. Never design only for the populated happy path.
 
 ---
 
-## 1. The State Quad
+## 1. The Four Essential UI States
 
 Every data-driven interface exists in one of four states: